Adolsign

Every signature, pulled straight from the directory.

Adolsign reads Active Directory, LDAP or Microsoft Entra ID and turns one template into a correct, on-brand Outlook signature for every user — deployed by login script, to a thousand mailboxes at once, without anyone hand-editing a template.

Request a free trial

Windows 2000 through 11 · Outlook 2000 through Microsoft 365 · Active Directory or Microsoft Entra ID · in production since 2005 · current release v3.0.0

How it works

1. Write a template. Drop scan codes into an .htm, .rtf or .txt file — the same ones your designer already ships, e.g. field_fullname, field_title, or with options: field_telephone(--prefix "Tel: ")field_telephone.
2. Define the rules. In adolsign.config, map templates to AD groups or field values, mark defaults, attach extra files — one file, every signature policy.

3. Run it. From a login script, your software distribution tool, or by hand:

   adolsign --configfile adolsign.config --default

4. It's already on every desktop. Outlook's signature files and default-signature registry keys are updated silently — nothing for the user to click.

Features

• Directory-driven fields — looks users up over ADSI/ADODB, plain LDAP, or Microsoft Graph, your choice per rollout. Title, department, phone, office — whatever your schema holds, mapped once.
• Conditional templating — scan codes take real options: --prefix, --postfix, --default, --case, --anchor, --format, --lookup. Blank fields can drop their whole line automatically.
• Rules, not rosters — assign signatures by AD group membership or by any directory field value. Add a rule once; every future hire picks it up automatically.
• Every format Outlook expects — HTML, RTF and plain text generated together, plus an auto-built vCard attached to the signature.
• Local or cloud rollout — write straight to Outlook's signature folder and registry defaults, or emit a deployment manifest for Exchange Online / Outlook on the web.
• Offline installer packages — bundle a signature set into a one-click installer for remote workers or machines outside the login-script path.

Modes

Local Outlook — writes signature files to Outlook's local signature folder, sets new-mail and reply/forward defaults in the registry, works across Office 2000 through Microsoft 365 desktop, deployed by login script with no user interaction.

Cloud / Exchange Online (new in 3.0) — renders the same templates against Microsoft Entra ID, emits a deployment manifest for Exchange Online / Outlook on the web, no local registry writes so it's safe for shared or virtual desktops.

Requirements

Deployment

FAQs