Creating a GPO for Office and Outlook Add-in
Introduction
This guide provides step-by-step instructions for installing the add-in on multiple machines via GPO. This is a different method as opposed to going to each machine and installing the add-in manually.
Before Beginning
- Prior to beginning this process, the add-in installers should be saved in a folder along the following path: \\<domain>\netlogon\
Note: If you do not already have the installation files for the add-in, please contact your TeamConnect administrator.
- In order to have the add-in deploy through GPO, you need to first access your domain controller. From there, you will create a new Group Policy, or GPO. This new GPO can be named anything, as long as it is clear for you.
Creating the Deployable Package
Step 1:
Access your domain policies. Right click on your Domain Policy to create a group policy object and click Edit. From here, you will need to expand out the Computer Configuration, Policies, and Software Settings arrows as seen below.
Note: A best practice is to make a new named policy for any software installation.
Next, right click in the blank space to the right of Software installation and hover over New and select Package.
Navigate to the folder you created before starting this process with the installation files and select the Setup file.
Deploy to assigned users.
Note: This will be available across the domain and it's accessible by domain users and computers since the folder resides in the
\\<domain>\netlogon\ path.
Linking the GPO
Step 2:
Return to your domain controller and right click on it, then choose Link an Existing GPO.
You will then select the Group Policy that was created for the Add-in.
Note: The GPO may take up to 2 hours to update and may require a restart. You can check to see if the GPO is there via group policy results by using the CMD prompt and typing: gpresult /r /scope:computer
Although it is not recommended, the GPO can be forced to update if needed using the CMD prompt and typing: gpupdate /force
Please refer to your IT Team prior to any forced changes.