Overview
This article outlines the process of deploying the ExSign Outlook Edition client using a Group Policy Object (GPO) logon script in a Windows domain environment. This approach ensures that the ExSign client is automatically copied to each user’s profile and executed at every login, enabling centralized and consistent signature management.
Step 1: Prepare Script and Files
Place the required files in the SYSVOL scripts directory on your domain controller:
\\dc01\SYSVOL\hc.corp\scripts\
Required files:
- ExSignClient.exe
- ExSignClient.exe.config
- Signature.cmd
Step 2: Create and Link the GPO
- Open Group Policy Management.
- Navigate to your domain.
- Create a new GPO (e.g., Run_Signature_Agent).
- Link the GPO to the appropriate Organizational Unit (OU) containing the target users.
Step 3: Configure the Logon Script
- Right-click the newly created GPO and select Edit.
- Navigate to:
User Configuration → Policies → Windows Settings → Scripts (Logon/Logoff) - Open Logon, then click Add.
- Specify the script path:
Step 4: Configure the Signature Script
Edit the Signature.cmd file and include the following commands:
copy \\dc01\SYSVOL\hc.corp\scripts\ExSignClient.exe %appdata%\ExSignclient.exe /Y
copy \\dc01\SYSVOL\hc.corp\scripts\ExSignClient.exe.config %appdata%\ExSignclient.exe.config /Y
start %appdata%\ExSignclient.exe
These commands will:
- Copy the ExSign client files to the user’s roaming profile directory.
- Ensure the client runs automatically at login.
Step 5: Verification
After a user logs in:
C:\Users\<Username>\AppData\Roaming\
- Confirm the presence of:
- ExSignclient.exe
- ExSignclient.exe.config
- Verify that the ExSign client launches automatically without errors.
Conclusion
Following the above steps ensures a seamless deployment of ExSign Outlook Edition via GPO. This method provides a centralized, automated, and reliable way to manage email signatures across all users in the domain environment.