How to Deploy Word Templates via Microsoft Endpoint Configuration Manager

If you manage multiple Windows computers in your organization, deploying standardized Word templates to every user can be time-consuming. Manually copying template files to each workstation leads to version inconsistencies and wasted IT hours. Microsoft Endpoint Configuration Manager (MECM) lets you push Word template files automatically to all managed devices. This article explains how to package a Word template, create a Configuration Manager application, deploy it to a device collection, and verify successful installation.

How Word Templates Are Stored and Why MECM Helps

Word templates are files with .dotx or .dotm extensions. When a user opens Word, the application looks for templates in specific folders. The default user template folder is %AppData%\Microsoft\Templates. Global templates for all users on a machine go in %ProgramFiles%\Microsoft Office\Templates\1033 or a custom network path defined in the Trust Center settings.

Without a deployment tool, an IT admin must copy template files to every computer manually. This method fails when template versions change or when new machines join the domain. MECM solves this by treating the template as an application. You package the file into an MSI, define a detection rule (for example, check for the file in a specific folder), and deploy the application to a collection of devices. MECM handles distribution, installation, and compliance reporting.

Prepare the Template File and Create the MSI Package

Before you use MECM, you need a deployable package. MECM can distribute .msi files natively. You can wrap your Word template in a lightweight MSI using a free tool like WiX Toolset or Advanced Installer. The MSI should copy the .dotx or .dotm file to the target folder and include a detection method such as a registry key or file version.

What You Need

You need the following items before starting:

• A finalized Word template file (.dotx or .dotm) stored on a network share.
• WiX Toolset or another MSI authoring tool installed on a staging computer.
• Administrator access to the MECM console.
• A device collection that contains the target computers.

Steps to Deploy the Word Template Using MECM

Follow these steps to create and deploy the application in Configuration Manager.

1. Create the MSI package for the template
   On a staging computer, open WiX Toolset and create a new Setup project. Add your template file to the project. Set the destination folder to [ProgramFiles64Folder]\Microsoft Office\Templates\1033 for global templates or [AppDataFolder]\Microsoft\Templates for per-user templates. Build the project to generate an .msi file. Copy the .msi and any supporting files to a network share accessible to the MECM site server.
2. Open the MECM console and start the Create Application wizard
   In the MECM console, go to Software Library > Application Management > Applications. Right-click Applications and select Create Application. Choose Manually specify the application information and click Next.
3. Enter general application information
   On the General Information page, type a name for the application, for example Word Corporate Template. Add a brief description and the version number of the template. Click Next.
4. Add a deployment type
   On the Deployment Types page, click Add. In the Create Deployment Type wizard, choose Windows Installer (.msi file) as the type. Browse to the network share that contains your .msi file. The wizard will parse the MSI and populate the product code and version automatically. Click Next.
5. Configure the detection method
   On the Detection Method page, the wizard will add a rule based on the MSI product code. This tells MECM whether the application is already installed. You can add a secondary rule to check for the template file in the target folder. Click Next through the remaining pages and close the deployment type wizard.
6. Finish the application wizard
   Back in the Create Application wizard, review the settings and click Next, then Close. The application now appears in the Applications list.
7. Distribute the application content
   Right-click the application and select Distribute Content. Choose a distribution point group that serves the target computers. Complete the wizard to copy the MSI files to the distribution points.
8. Deploy the application to a device collection
   Right-click the application and select Deploy. In the Deploy Software wizard, browse to the device collection that contains the target computers. Set the action to Install and the purpose to Required. Define a schedule, for example, As soon as possible. Set the deadline to a specific date and time. Complete the wizard.
9. Monitor the deployment
   In the MECM console, go to Monitoring > Deployments. Select your deployment to see the compliance status. Wait for the client computers to run the policy and install the MSI. You can also check the AppEnforce.log file on a client computer for detailed installation results.

Common Deployment Issues and How to Fix Them

The Template Does Not Appear in Word After Deployment

Word may not recognize the template if the MSI copied the file to the wrong folder. Verify the destination path in the MSI. Open Word and go to File > Options > Add-ins. Under Manage, select Templates and click Go. The template should appear in the Global templates and add-ins list. If it does not, check that the file is in the correct folder. For per-user templates, confirm that the user profile path is correct.

MECM Reports Application as Not Compliant

The detection method may be failing. Open the application properties in MECM and review the detection rule. If you used the MSI product code rule only, the application becomes non-compliant if the MSI is uninstalled. Add a file-based detection rule that checks for the template file in the target folder. This rule will mark the application as installed even if the MSI registry data is missing.

Deployment Takes Too Long or Fails on Some Computers

Large template files can cause slow downloads over low-bandwidth networks. Compress the template file before packaging it in the MSI. Also verify that the distribution point is within the same boundary group as the client computers. If the client cannot reach the distribution point, the deployment will fail.

MECM Application vs Package: Template Deployment Differences

Item	Application (Recommended)	Package / Program
Description	Uses MSI with detection rules for compliance reporting	Uses a script or command line with no built-in detection
Detection method	File, registry, or product code rule	No automatic detection; requires custom exit code logic
Compliance reporting	Yes, shows installed vs not installed status	No, only shows whether the program ran
Reinstallation behavior	Reinstalls only if detection rule fails	Runs the program every time based on schedule
Best use case	Word template deployment to many devices	One-time script execution or legacy deployments

Always use the Application model for template deployment. It gives you accurate compliance data and avoids reinstalling the template on every policy refresh.

After you deploy the Word template through MECM, every target computer will have the template in the correct folder. Users can open Word and select the template from File > New > Personal. To keep templates current, update the MSI with the new file version and deploy a revision of the application. For advanced control, add a supersedence rule that replaces the old application with the new one automatically.