How to Use Group Policy to Deploy Custom Word Templates

You want every user in your domain to have the same set of custom Word templates — letterheads, memos, or reports — without manually copying files to each workstation. Group Policy can push these templates to the correct folder and configure Word to use them as the default document location. This article explains how to prepare the templates, create a Group Policy Object, and map the network path so Word loads the templates on startup.

What Group Policy Deployment of Word Templates Does

Group Policy lets you centrally manage settings across all computers joined to a domain. When you deploy custom Word templates through Group Policy, you avoid visiting each machine. The policy copies the template files from a network share to the user’s local Templates folder. It also sets the Workgroup templates location in Word so the templates appear under File > New. No user action is required after the next Group Policy refresh or computer restart.

Before you start, you need a domain controller running Windows Server 2016 or later. You also need a network share that all users can read. The Word templates must be in .dotx or .dotm format and stored in a single folder on that share. You need domain administrator rights to create and link Group Policy Objects.

Steps to Deploy Custom Word Templates Using Group Policy

Step 1: Prepare the Template Files and Network Share

1. Create a folder for the templates
   On your file server, create a folder named WordTemplates. Place all custom .dotx or .dotm files in this folder.
2. Set share permissions
   Right-click the folder, select Properties > Sharing > Advanced Sharing. Check Share this folder. Click Permissions and add the Domain Users group with Read access. Remove the Everyone group if present.
3. Set NTFS permissions
   On the Security tab, add Domain Users with Read & Execute and List folder contents permissions. Apply the changes.
4. Test the share path
   On a client computer, open File Explorer and type \FileServer\WordTemplates. Verify that all template files are visible and readable.

Step 2: Create a Group Policy Object to Copy Templates

1. Open Group Policy Management Console
   On your domain controller, run gpmc.msc from the Run dialog. Expand the forest and domain.
2. Create a new GPO
   Right-click the domain or an OU containing the target users, select Create a GPO in this domain, and Link it here. Name it Word Template Deployment. Click OK.
3. Edit the GPO
   Right-click the new GPO and select Edit. In the Group Policy Management Editor, navigate to User Configuration > Preferences > Windows Settings > Files.
4. Add a file copy action
   Right-click Files, select New > File. In the Properties dialog, configure the following:
   – Action: Update
   – Source file(s): \\FileServer\WordTemplates\
   – Destination File: %USERPROFILE%\AppData\Roaming\Microsoft\Word\Startup\ (or \Templates if you prefer the user Templates folder)
   Check Replace the file if it exists if you want to update templates on each refresh. Click OK.
5. Set the common options
   In the Common tab, check Run in logged-on user’s security context. This ensures the copy uses the user’s permissions. Click OK.

Step 3: Configure Word to Use the Workgroup Templates Location

1. Navigate to Word administrative templates
   In the same GPO, go to User Configuration > Policies > Administrative Templates > Microsoft Word 2016 > File Locations. If you do not see Microsoft Word 2016, download the Office Administrative Template files from Microsoft and add them to the Central Store.
2. Enable Workgroup templates setting
   Double-click Workgroup templates. Select Enabled. In the Path box, enter the UNC path to the folder where the templates were copied on the client, for example %USERPROFILE%\AppData\Roaming\Microsoft\Word\Startup. Click OK.
3. Optional: Hide the Personal templates tab
   Navigate to User Configuration > Policies > Administrative Templates > Microsoft Word 2016 > Miscellaneous. Enable Disable the ‘Personal’ tab in the New Document dialog. This forces users to see only the workgroup templates. Click OK.

Step 4: Link the GPO and Test

1. Link the GPO to the correct OU
   Ensure the GPO is linked to the organizational unit containing the target users. If you created it at the domain level, it applies to all users unless filtered.
2. Force a Group Policy update
   On a test client computer, open Command Prompt as administrator and run gpupdate /force. Wait for the update to complete.
3. Verify the templates
   Open Word and go to File > New. Look for the Workgroup templates or the Personal tab. The custom templates should appear there. Also check that the files exist in the destination folder on the client.

Common Issues When Deploying Word Templates via Group Policy

Word Does Not Show the Deployed Templates Under File > New

This usually happens when the Workgroup templates path is set incorrectly. Verify the path in the GPO matches the exact destination folder used in the File preference. If you copied the templates to %USERPROFILE%\AppData\Roaming\Microsoft\Word\Startup, the Workgroup templates path must be identical. Also confirm that the templates are .dotx or .dotm files, not .docx.

Templates Are Not Copied to the Client Computer

Check the share and NTFS permissions on the source folder. The user must have Read access to the network share. Also verify that the File preference action is set to Update and the source path uses the correct server name. Run gpresult /h gpresult.html on the client to see if the GPO is applied.

Group Policy Administrative Templates for Word Are Missing

The default Group Policy console does not include Word settings. Download the Microsoft 365 Apps for enterprise administrative templates from the Microsoft Download Center. Extract the files and copy the .admx and .adml files to the Central Store folder at \\Domain\SYSVOL\Domain\Policies\PolicyDefinitions.

Manual Copy vs Group Policy Deployment: Key Differences

Item	Manual Copy	Group Policy Deployment
Setup time	High — must visit each computer	Low — configure once per domain
Update frequency	Requires manual re-copy	Automatic on policy refresh
User permissions needed	Local admin rights often required	Standard user rights sufficient
Central management	No	Yes
Supports multiple template sets per OU	No	Yes — use separate GPOs

You can now centrally deploy custom Word templates to all domain users without visiting each workstation. Start by testing the GPO on a small OU before rolling it out domain-wide. For more granular control, use security filtering to apply the GPO only to specific user groups. As a next step, consider deploying a custom Normal.dotm template to enforce default font and margin settings across the organization.