

You can see what this looks like in the screenshot below. Be careful to spell PolicyDefinitions correctly or the administrative templates will not work.įinally, copy all of the administrative template and localization files you downloaded and extracted earlier into the PolicyDefinitions folder. Once you arrive in the Policies folder, you will need to create a subfolder called PolicyDefinitions, as shown in the screenshot below. You will need to type this location into the window’s address bar to access it. To create the Central Store, open File Explorer and navigate to %SystemRoot%\sysvol \domain\policies. Normally, the Central Store is located at %SystemRoot%\sysvol \domain\policies\PolicyDefinitions. Assuming that you are installing the administrative template files on a domain controller, you will need to place the files in the Central Store. Once you have downloaded and extracted administrative template files, as shown in the screenshot above, you will need to move them to a location where they can be used. You can see what the template files look like in the following screenshot. There will also be a series of language-specific folders containing ADML files that supply the language used within the templates. The download consists of a series of ADMX files, each corresponding to a particular Office application. Otherwise, if you are only planning on using the templates in conjunction with the Active Directory (as is the case with what I am about to show you), then either version will work.

If, for example, you are going to be customizing the 64-bit version of Office, you will need to download the 64-bit templates.

If you will be using the Office Customization Tool, you will need to download the version of the template that matches the version of Office that you are customizing. When you get ready to download the template, you will be asked to install the 32-bit version or the 64-bit version. You can download the Microsoft Office administrative templates here. Before you can do that, you will need to install the Microsoft Office administrative templates if you have not already done so. The easiest way to keep users from seeing messages like the one shown above is to create a Group Policy setting that disables Microsoft 365 update messages.

Fortunately, Microsoft 365 update messages like the one shown in the screenshot below are relatively easy to disable. Few things are more annoying to anyone hard at work trying to complete a project than receiving messages nagging the user to install Microsoft Office 365 updates.
