Create a network installation of Visual Studio 2017
Typically, an enterprise administrator creates a network install point for deployment to client workstations. We've designed Visual Studio 2017 to enable you to cache the files for the initial installation along with all product updates to a single folder. (This process is also referred to as creating a layout.) We've done this so that client workstations can use the same network location to manage their installation even if they haven't yet updated to the latest servicing update.
If you have multiple editions of Visual Studio in use within your enterprise (for example, both Visual Studio Professional and Visual Studio Enterprise), you must create a separate network install share for each edition.
Download the Visual Studio bootstrapper
Download the edition of Visual Studio you want. Make sure to click Save, and then click Open folder.
Your setup executable—or to be more specific, a bootstrapper file—should match one of the following.
|Visual Studio Enterprise||vs_enterprise.exe|
|Visual Studio Professional||vs_professional.exe|
|Visual Studio Community||vs_community.exe|
Create an offline installation folder
You must have an internet connection to complete this step. To create an offline installation with all languages and all features, use one of the commands from the following examples.
A complete Visual Studio 2017 layout requires at least 35 GB of disk space and can take some time to download. See the Customizing the network layout section for details on how to create a layout with only the components you want to install.
Make sure that you run the command from your Download directory. Typically, that's
C:\Users\<username>\Downloads on a computer running Windows 10.
For Visual Studio Enterprise, run:
vs_enterprise.exe --layout c:\vs2017offline
For Visual Studio Professional, run:
vs_professional.exe --layout c:\vs2017offline
For Visual Studio Community, run:
vs_community.exe --layout c:\vs2017offline
Modify the response.json file
You can modify the response.json to set default values that are used when setup is run. For example, you can configure the
response.json file to select a specific set of workloads selected automatically.
See Automate Visual Studio installation with a response file for details.
Copy the layout to a network share
Host the layout on a network share so it can be run from other machines.
xcopy /e c:\vs2017offline \\server\products\VS2017
Customizing the network layout
There are several options you can use to customize your network layout. You can create a partial layout that only contains a specific set of language locales, workloads, components, and their recommended or optional dependencies. This might be useful if you know that you are going to deploy only a subset of workloads to client workstations. Typical command-line parameters for customizing the layout include:
--addto specify workload or component IDs. If
--addis used, only those workloads and components specified with
--addare downloaded. If
--addis not used, all workload and components are downloaded.
--includeRecommendedto include all the recommended components for the specified workload IDs
--includeOptionalto include all the recommended and optional components for the specified workload IDs.
--langto specify language locales.
Here are a few examples of how to create a custom partial layout.
- To download all workloads and components for only one language, run:
vs_enterprise.exe --layout C:\vs2017offline --lang en-US
- To download all workloads and components for multiple languages, run:
vs_enterprise.exe --layout C:\vs2017offline --lang en-US de-DE ja-JP
- To download one workload for all languages, run
vs_enterprise.exe --layout C:\vs2017offline --add Microsoft.VisualStudio.Workload.Azure --includeRecommended
- To download two workloads and one optional component for three languages, run:
vs_enterprise.exe --layout C:\vs2017offline --add Microsoft.VisualStudio.Workload.Azure --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Component.GitHub.VisualStudio --includeRecommended --lang en-US de-DE ja-JP
- To download two workloads and all of their recommended components, run:
vs_enterprise.exe --layout C:\vs2017offline --add Microsoft.VisualStudio.Workload.Azure --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Component.GitHub.VisualStudio --includeRecommended
- To download two workloads and all of their recommended and optional components, run:
vs_enterprise.exe --layout C:\vs2017offline --add Microsoft.VisualStudio.Workload.Azure --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Component.GitHub.VisualStudio --includeOptional
New in 15.3
When you run a layout command, the options that you specify are saved (such as the workloads and languages). Subsequent layout commands will include all of the previous options. Here is an example of a layout with one workload for English only:
vs_enterprise.exe --layout c:\VS2017Layout --add Microsoft.VisualStudio.Workload.ManagedDesktop --lang en-US
When you want to update that layout to a newer version, you don't have to specify any additional command-line parameters. The previous settings are saved and used by any subsequent layout commands in this layout folder. The following command will update the existing partial layout.
vs_enterprise.exe --layout c:\VS2017Layout
When you want to add an additional workload, here's an example of how to do so. In this case, we'll add the Azure workload and a localized language. Now, both Managed Desktop and Azure are included in this layout. The language resources for English and German are include for all these workloads. The layout is updated to the latest available version.
vs_enterprise.exe --layout c:\VS2017Layout --add Microsoft.VisualStudio.Workload.Azure --lang de-DE
If you want to update an existing layout to a full layout, use the --all option, as shown in the following example.
vs_enterprise.exe --layout c:\VS2017Layout --all
Deploying from a network installation
Administrators can deploy Visual Studio onto client workstations as part of an installation script. Or, users who have administrator rights can run setup directly from the share to install Visual Studio on their machine.
- Users can install by running:
- Administrators can install in an unattended mode by running:
\\server\products\VS2017\vs_enterprise.exe --quiet --wait --norestart
When executed as part of a batch file, the
--wait option ensures that the
vs_enterprise.exe process waits until the installation is complete before it returns an exit code. This is useful if an enterprise administrator wants to perform further actions on a completed installation (for example, to apply a product key to a successful installation) but must wait for the installation to finish to handle the return code from that installation. If you do not use
vs_enterprise.exe process exits before the installation is complete and returns an inaccurate exit code that doesn't represent the state of the install operation.
When you install from a layout, the content that is installed is acquired from the layout. However, if you select a component that is not in the layout, it will be acquired from the internet. If you want to prevent Visual Studio setup from downloading any content that is missing in your layout, use the
--noWeb option. If
--noWeb is used and the layout is missing any content that is selected to be installed, setup fails.
If you used the
--wait parameter, then depending on the result of the operation, the
%ERRORLEVEL% environment variable is set to one of the following values:
|0||Operation completed successfully|
|3010||Operation completed successfully, but install requires reboot before it can be used|
|Other||Failure condition occurred - check the logs for more information|
Updating a network install layout
As product updates become available, you might want to update the network install layout to incorporate updated packages.
How to create a layout for a previous Visual Studio 2017 release
The Visual Studio 2017 bootstrappers that are available on visualstudio.microsoft.com download and install the latest Visual Studio 2017 release available whenever they are run. If you download a Visual Studio bootstrapper today and run it six months from now, it installs the Visual Studio 2017 release that is available at that later time. If you create a layout, installing Visual Studio from that layout installs the specific version of Visual Studio that exists in the layout. Even though a newer version might exist online, you get the version of Visual Studio that is in the layout.
If you need to create a layout for an older version of Visual Studio 2017, you can go to https://my.visualstudio.com to download "fixed" versions of the Visual Studio 2017 bootstrappers.
How to get support for your offline installer
If you experience a problem with your offline installation, we want to know about it. The best way to tell us is by using the Report a Problem tool. When you use this tool, you can send us the telemetry and logs we need to help us diagnose and fix the problem.
We have other support options available, too. For a list, see our Talk to us page.
Sometimes, things can go wrong. If your Visual Studio installation fails, see the Troubleshooting Visual Studio 2017 installation and upgrade issues page. If none of the troubleshooting steps help, you can contact us by live chat for installation assistance (English only). For details, see the Visual Studio support page.
Here are a few more support options:
- You can 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.
- You can share a product suggestion with us on UserVoice.
- You can track product issues and find answers in the Visual Studio Developer Community.
- You can also engage with us and other Visual Studio developers through the Visual Studio conversation in the Gitter community. (This option requires a GitHub account.)