FAQs - Outlook / Office 365 Deployment Desktop Software


    1. How do I remove the Outlook / Office 365 Deployment Software from my computer?

    1. Open your computer’s CONTROL PANEL.
    2. Click open “Programs and Features”.
    3. Locate the “Outlook Signature Deployment Tool” published by “DynaSend” in your list of installed programs.
    4. Click on it and then click UNINSTALL (and then follow the prompts).

    uninstall the outlook deployment tool


    2. What are the technical requirements to install and run the software?

    The Outlook / Office 365 Deployment Software is Windows-based and requires Microsoft’s .NET Framework version 4.5 (or higher). Microsoft’s .NET Framework version 4.5 was released in 2012 and should already reside on your computer if it was purchased after 2012 or if you have done the routine updates to Windows that Microsoft encourages.


    3. How will the AdminSetupxxxxx.msi setup file work on a Remote Desktop Server ([RDS server] formerly call Terminal server)?

    The Administrator mode is not going to work out of the box for a terminal server setup. However, it can be made to work, or you may find it easier to have individual users run the user mode setup (or automatically deploy the user mode setup to individual users).

    If you would like to use the Administrator mode setup, you will need to make some changes post install, and arrange to provision a Configuration file for every user who has a signature setup. The file is %appdata%\DynaSend\Signature Deployment Tool\DeploymentToolConfiguration.xml and is installed in C:\ProgramData\DynaSend\Signature Deployment Tool by default. The values which will need to be set for every user are the email address and signature folder. The “UserSid” referenced in that file is not actually currently used.

    For admin mode, the other thing you would need to do post-install for the Administrator mode setup is manually edit the SignatureDeploymentTool.exe.config file in the C:\Program Files\DynaSend\Signature Deployment Tool folder, and set the isUserMode setting to true, even though you have installed it in admin mode. This is very important because it will not pick up the right DeploymentToolConfiguration.xml file for multiple users otherwise.


    4. How has administrative version of the Outlook / Office 365 Deployment Software been pushed out to a large number of users?

    The administrative version of the Outlook / Office 365 Deployment Software was pushed out by one of our clients, Tektronix, to 3000+ users worldwide using the following approach:

    Email Signature Tool Deployment Scope (PDF)

    How Tektronix Deployed the Tool (PDF)


    5. How do I use Group Policy to remotely install the Outlook / Office 365 Deployment Software?

    Here’s a link to Microsoft’s instructions for remotely installing an MSI package using group policy: https://support.microsoft.com/en-us/kb/816102.


    6. We don’t use Active Directory, so how can I automatically populate the email address field during the deployment process?

    If you’re not using Active Directory the Outlook / Office 365 Deployment Software will be unable to automatically populate the email address field. Therefore the EMAILADDRESS variable in the installer must be set to the user’s email address during the deployment process. While there are multiple ways of doing this, one approach is at the command line level via the following (rex@digitechbranding.com being the email address in this example):

    msiexec.exe /passive /i DynaSendSignatureDeploymentToolAdminSetup1-0-8-x86.msi EMAILADDRESS=rex@digitechbranding.com
    

    7. Do I need to do anything special when remotely deploying the software to PC’s shared by multiple users or to the Citrix shared environment?

    The trick here is to remotely install the “admin” version of the software, but to then to make it behave like the “user” version - resulting in the software isolating the multiple users on the machine and prompting each of them for their email address the first time the app is opened.

    Begin by remotely installing the Outlook / Office 365 Deployment Software without specifying the email address switch during the install.

    Following the installation, it is necessary to make a small change to a configuration file as follows:

    In the C:\Program Files (x86)\DynaSend\Signature Deployment Tool, open SignatureDeploymentTool.exe.config in Notepad and change the “isUserMode” setting to true - highlighted below. (Note: The installation script can probably just overwrite this file post-install for shared PC’s.)


    8. What do you recommend as to the most efficient way to deploy this to multiple users in the Citrix environment?

    If the administrative version is installed (by an admin), it will use the per-machine registry key which is:

    HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Windows\CurrentVersion\Run
    

    For the Citrix environment, rather than installing for every user, we recommend installing the admin version once into your base Citrix environment (part of the image that gets reset) but manually editing the config file at \Program Files\DynaSend\Signature Deployment Tool\SignatureDeploymentTool.exe.config to set “isUserMode” to “true”.

    So, even though it is installed in administrative mode, it will run individually for each user. We realize this may seem a little counter-intuitive but this way you could avoid installing it 100 times (or whatever) for 100 users.


    9. Can the deployment software be configured to just run once per logon, rather than running continuously in the background?

    With the default installation, the software will always be running in the background and will check for signature updates periodically.

    If you’d prefer to have it only run once, at the time of logon, it can be set-up to operate this way. In this case the behavior is for the Outlook / Office 365 Deployment Software to be launched when the user logs-on. It will immediately check for any signature updates (and apply them if found). Once done, it will close and exit. The switch to use to create this behavior is /runonce switch.

    The final command line would look like: “C:\Program Files (x86)\DynaSend\Signature Deployment Tool\signaturedeploymenttool.exe” /runonce


    10. Can I run the install silently using some switches, without specifying any email address?

    Yes, you can run the install silently using some switches, without specifying an email address:

    msiexec /i DynaSendSignatureDeploymentToolUserSetup1-1-0-x86 /passive
    

    The wizard won’t appear, just a progress bar, and there will be no prompt for an email address. When the product is first run, it will pick up the address from Active Directory. By the way running from Group Policy is the same as the above except that “passive” is replaced with “quiet” which means that not even a progress bar is displayed.

    If it is still not getting picked up, please see the screenshots below which show the place it looks at in Active Directory to match to an email address, and let us know if you are using something else or otherwise what results you are seeing.

    From Administrative Tools -> Active Directory Users & Computers

    Active Directoriy Properties - General

    This one is normally set via the Exchange Management tools, which would depend on the version of Exchange you have (if any). However if you don’t have any on-premises Exchange the above is the easiest one to use. You can probably edit the proxyAddresses attribute manually even if you don’t have Exchange, although if the attribute doesn’t exist at all you would need to use ADSIEdit.

    Active Directory Properties - Attribute Editor

    About Digitech Branding

    Founded in 1999, Digitech Branding is a proprietary technology developer and service provider with the singular focus of producing standardized, high-quality, professional email signatures for companies and organizations worldwide.

    Contact Us

    Digitech Branding
    611 Fremont Street
    Lake Mills, WI 53551
    +1 (920) 648-5408
    sales@digitechbranding.com

    All Materials Copyright Digitech Branding - 2017