Administrative Templates (ADMX)

Applies to: yesVisual Studio noVisual Studio for Mac noVisual Studio Code

IT Administrators in organizations may want to control certain aspects of Visual Studio behavior to achieve consistency, compliance, or compatibility across their client machines. An easy way to accomplish this control is to configure group policies using Visual Studio Administrative Templates (ADMX).

The Visual Studio Administrative Templates (ADMX) consolidate the various Visual Studio policies into different categories, making them easily discoverable. IT Administrators can learn what policies are available and then configure and deploy the appropriate settings to the client machines. The ADMX templates can be integrated with standard management and deployment tools such as Group Policy Editor or Microsoft Endpoint Manager.

The Visual Studio group policy settings contained in the ADMX file are machine-wide for all users, meaning they intend to cover all applicable installed instances, versions, and SKUs of Visual Studio. Sometimes a policy is particular to a specific version of Visual Studio, and the template clearly calls this out.

Visual Studio policy categories

There are four main categories of Visual Studio policies that are included in the Visual Studio Administrative Templates (ADMX):

Acquiring the Visual Studio Administrative Templates (ADMX)

The Visual Studio Administrative Templates (ADMX) can be downloaded from the Microsoft Download Center. The default installation path is C:\Windows\PolicyDefinitions, a location that makes them instantly visible to the Group Policy Editor (gpedit.exe) tool, but you can install them anywhere. The templates are updated periodically, so if you use them we recommend that you check back periodically to get the latest updates.

Using Microsoft Endpoint Manager to deploy the policies

You can use the Visual Studio Administrative Templates (ADMX) within enterprise management tools such as Microsoft Endpoint Manager to configure and control client machines.

For cloud connected environments that are managed by Intune, you can import the Visual Studio Administrative Templates (ADMX) into your Devices > Configuration profiles, and then create a customized Configuration profile based on the imported ADMX files. Eventually, Visual Studio Administrative Templates will be built natively into the Microsoft Endpoint Manager environment, so this manual import step will be unnecessary.

Note

Visual Studio Administrative Templates (ADMX) depend on the Windows administrative template (Windows.admx), so make sure you manually import that one in too.]

Support or troubleshooting

Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.

Here are a few more support options:

  • We offer an installation chat (English only) support option for installation-related issues.
  • Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE. If you're an IT Administrator and don't have Visual Studio installed, you can submit IT Admin feedback here.
  • Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.

See also