Visual Studio administrator guide

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

In enterprise environments, system administrators typically deploy and update software on end users machines. The Visual Studio product integrates well in these types of environments by giving system administrators the ability to manage and control when and how the Visual Studio software is deployed and updated. Visual Studio can be acquired from the internet, from a network share, or from a product cache, and it can be deployed and updated manually, programatically or by using systems management software. Visual Studio provides the ability to create and maintain acquisition locations, pre-configure installation defaults, deploy product keys during the installation process, and manage product updates after a successful rollout. This administrator guide provides quick links to scenario-based guidance for enterprise deployment.

Research and plan before you begin

You will need to make a plan for how you deploy Visual Studio across your organization. Below lists some of the key things to think about, and it's best if your plan and decisions are made before the original installation happens on the client machine.

  • Make sure that each target computer meets the minimum installation requirements. Note that Visual Studio does not support application virtualization solutions such as Microsoft App-V or MSIX for Windows or third-party app virtualization technologies.
  • Make sure that each target computer meets the minimum installation requirements. Note that Visual Studio does not support application virtualization solutions such as Microsoft App-V or MSIX for Windows or third-party app virtualization technologies.
  • Clarify your security and compatibility needs. Do you need to ensure that your organization is always running the latest and most secure software?

If your company needs to stay on a feature set longer but still wants to get regular servicing security updates, you should plan to use a servicing baseline. For more information about security baselines, see the Support options for Enterprise and Professional customers section of the Visual Studio product lifecycle and servicing page.

If your company needs to stay on a feature set longer but still wants to get regular servicing security updates, you should plan to use a servicing baseline. For more information, see the Support options for Enterprise and Professional customers section of the Visual Studio product lifecycle and servicing page.

  • Decide on the update model.

    • Where should your client machines acquire the product updates from? In other words, should they get their updates from an IT managed company-wide network layout, or should they acquire the updates from the internet? This often depends on if clients have access to the internet or not.
    • Who is allowed to update the client machines? Remember that whoever initiates the update must have administrative privileges on the machine. Are users allowed to update their machines, or does an admin need to invoke it centrally or programatically?
    • When should the updates happen? Should it be left to the user's discretion to decide when to update, or do you want central IT control that enforces when updates happen?
  • Decide if you want to configure group policy settings on your client machines.

  • Decide which workloads and components your company needs.

  • Follow Windows security baselines. Microsoft is dedicated to providing its customers with secure operating systems, such as Windows 10 and Windows Server, and secure apps, such as Microsoft Edge. In addition to the security assurance of its products, Microsoft also enables you to have fine control over your environments by providing various configuration capabilities.

Install Visual Studio

The following resources will help you do the initial install of Visual Studio in common enterprise scenarios.

Update Visual Studio

The following resources will help you keep your Visual Studio updated, current, and secure.

Configure Visual Studio

  • Set registry policies that affect the deployment and behavior of Visual Studio such as where some packages shared with other versions or instances are installed, where and whether packages are cached, if administrator update should be enabled or how they should be applied, which update channels are available and how they're presented to the client, and how notifications appear or don't appear.
  • Create custom bootstrapper packages. Learn advanced techniques for how to create custom bootstrapper packages to further control your installation configuration by creating product and package manifests.

Manage, Modify or Repair Visual Studio

  • Detect, verify, and manage installed Visual Studio instances on client machines.

  • Get troubleshooting tips. Get help when you’re installing or updating Visual Studio, and learn how to report a problem if you’re blocked. These tips include step-by-step instructions that should resolve most online or offline installation issues.

  • Repair Visual Studio to fix update issues. Sometimes your Visual Studio installation becomes damaged or corrupted. A repair is useful for fixing install-time issues across all install operations, including updates.

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 also 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