Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Administrators can use Office policy templates with the Group Policy settings of Windows
Article ID: 826170 - View products that this article applies to.
This article discusses how administrators can use Microsoft Office policy templates with the Group Policy settings of Microsoft Windows. The Microsoft Office 2003 Resource Kit contains policy templates (.adm files) that administrators can use with Office 2003 programs. In a Microsoft Windows-based network, Group Policy settings can help administrators control how users work with Office 2003.
This article describes the resources that are available for creating policies to be used in Microsoft Windows Server 2000-based environments and in Microsoft Windows Server 2003-based environments. This article contains the following sections:
OverviewsBy setting policies, you can define and maintain a particular Office 2003 configuration on users' computers. Unlike other customizations (such as default settings that are distributed in a transform [MST file]), policies are reapplied every time that a user logs on to the network (or at some other interval set by the administrator). Users cannot edit the registry to change the policies.
You can set policies that apply to the local computer (and to every user of that computer), or you can set policies that apply only to individual users. You set per-computer policies under Computer Configuration in the Group Policy snap-in. Per-computer policies are applied the first time that any user logs on to the network from that computer. You set per-user policies under User Configuration in the Group Policy snap-in. Per-user policies are applied when the specified user logs on to the network from any computer.
To use an Office 2003 policy template, you must load it in the Group Policy Microsoft Management Console snap-in.
Available Office 2003 policy templatesWith the policy template files in the Microsoft Office 2003 Resource Kit , you can set policies globally for users of Office on a network. By using policies, you can quickly enforce a user configuration on users' computers when users, groups, or computers log on to the network.
The Office policy template files (.adm files) describe all the policy settings that you can set for Office. You use these .adm files with the Group Policy snap-in that is included with Microsoft Windows operating systems to apply policies to users' computers.
The Setup program of the Microsoft Office 2003 Resource Kit installs the following policy templates in the Windows\Inf folder on your computer.
Collapse this tableExpand this table
Policy Template FilesOn the Policy Template Files Web page of the Microsoft Office 2003 Resource Kit Web site, you can install the Office 2003 policy templates, or the Visio 2003 policy templates, or both.
How to load an Office 2003 policy template in the Local Computer policyYou use the Group Policy snap-in to set Office 2003 policies from the Office policy templates (.adm files). After you set policies for a particular Group Policy object, Windows automatically implements the policies on the users' computers.
To load an Office 2003 policy in the Local Computer Policy, follow these steps:
ReferencesFor information about how to manage users' configurations by policy, visit the following Microsoft Web site:
Managing Users' Configurations by PolicyFor information about how to use group policies in Microsoft Windows Server 2003, visit the following Microsoft Web site:
http://www.microsoft.com/windowsserver2003/techinfo/overview/gpintro.mspxFor information about to how to use group policies in Microsoft Windows 2000, visit the following Microsoft Web site:
http://technet.microsoft.com/library/Bb742376.aspxFor information about how to install and maintain software applications based on Group Policy, visit the following Microsoft Web site:
Using Group Policy to Deploy OfficeFor information about enterprise management with the Group Policy Management Console, visit the following Microsoft Web site:
Article ID: 826170 - Last Review: May 24, 2012 - Revision: 4.0