Visual Studio 2017 administrator guide
In enterprise environments, it's common for system administrators to deploy installations to end-users from a network share or by using systems management software. We've designed the Visual Studio setup engine to support enterprise deployment, allowing system administrators the ability to create a network install location, to pre-configure installation defaults, to deploy product keys during the installation process, and to manage product updates after a successful rollout. This administrator guide provides scenario-based guidance for enterprise deployment in networked environments.
Deploy Visual Studio 2017 in an enterprise environment
You can deploy Visual Studio 2017 to client workstations as long as each target computer meets the minimum installation requirements. Whether you're deploying through software like System Center or through a batch file, you'll typically want to go through the following steps:
Create a network share that contains the Visual Studio product files to a network location.
Select the workloads and components you want to install.
Optionally, apply a volume license product key as part of the installation script so that users don't need to activate the software separately.
Update the network layout to control when product updates are delivered to your end-users.
Optionally, set registry keys to control what is cached on client workstations.
Use your deployment technology of choice to execute the script generated in the previous steps on your target developer workstations.
Refresh your network location with the latest updates to Visual Studio by running the command you used in step 1 on a regular basis to add updated components.
Note that installations from a network share will "remember" the source location they came from. This means that a repair of a client machine might need to return to the network share that the client originally installed from. Choose your network location carefully so that it aligns to the lifetime that you expect to have Visual Studio 2017 clients running in your organization.
Use Visual Studio tools
We have several tools available to help you detect and manage installed Visual Studio instances on client machines.
In addition to the documentation in the administrator guide, a good source of information on Visual Studio 2017 setup is Heath Stewart's blog.
Specify customer feedback settings
By default, the Visual Studio installation enables customer feedback. When you enable Group Policy, you can configure Visual Studio to disable customer feedback on individual computers. To do so, set a registry-based policy on the following key:
Entry = OptIn
Value = (DWORD)
- 0 is opted out
- 1 is opted in
For more information about customer feedback settings, see the Visual Studio Customer Experience Improvement Program page.
Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshooting Visual Studio 2017 installation and upgrade issues for step-by-step guidance.
We also offer a live chat (English only) support option for installation-related issues.
Here are a few more support options:
- 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.
- Share a product suggestion with us on UserVoice.
- Track product issues and find answers in the Visual Studio Developer Community.
- Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.
- Install Visual Studio 2017
- Use command-line parameters to install Visual Studio 2017
- Create a networked-based installation of Visual Studio
- Automate Visual Studio with a response file
- Automatically apply product keys when deploying Visual Studio
- Set defaults for enterprise deployments of Visual Studio
- Disable or move the package cache
- Update a networked-based installation of Visual Studio
- Control updates to Visual Studio deployments
- Tools for detecting and managing Visual Studio instances