You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/install/create-a-network-installation-of-visual-studio.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,16 +19,16 @@ ms.subservice: installation
19
19
20
20
Sometimes an enterprise administrator wants to create a private installation cache (also known as a "layout") that contains Visual Studio files that can be [deployed to client machines within an organization](deploy-a-layout-onto-a-client-machine.md).
21
21
22
-
Creating a layout is useful in following situations:
23
-
-A user has limited permissions
24
-
-The client machines have limited access to the internet
25
-
-An organization wants to standardize on a particular version of the developer toolset
22
+
Creating a layout is useful in following scenarios:
23
+
-The user has limited system permissions
24
+
-Client machines have restricted internet access
25
+
-The organization wants to standardize on a specific version of the developer toolset
26
26
27
27
We designed Visual Studio so that an administrator can both create and maintain a layout and store it on an internal network share and optionally make it available on an organization's intranet. The layout serves as the source location for all Visual Studio files needed for both initial client installation and subsequent updates.
28
28
29
29
The information on this page is grouped up into three main sections:
30
30
31
-
*[**Create the layout**](#create-the-layout): describes how to create the layout with the correct product content, configure the default settings, store it on a network file share, and make it available on your intranet.
31
+
*[**Create the layout**](#create-the-layout): describes how to create a layout with the correct product content, configure the default settings, store the layout on a network file share, and make it available on your intranet.
32
32
*[**Maintain the layout**](#maintaining-your-layout): information on how to best update the layout's product version, or modify the layout's product content, channel settings, installer version, and folder size.
33
33
*[**Help and Support**](#get-support-for-your-network-layout): where to ask for help
34
34
@@ -46,7 +46,7 @@ Download the correct bootstrapper for the edition of Visual Studio you want and
46
46
47
47
::: moniker range="vs-2019"
48
48
49
-
The following bootstrappers always install the latest most secure version of Visual Studio 2019, no matter when you run them. Alternatively, if you want to create or update a layout to a specific version of Visual Studio 2019, go to the [Visual Studio 2019 Releases](/visualstudio/releases/2019/history#installing-an-earlier-release) page that has links to the fixedversion bootstrappers for each servicing release, and download the one you want. Copy it into the directory that you want to serve as the source location of the layout.
49
+
The following bootstrappers always install the latest most secure version of Visual Studio 2019, no matter when you run them. If you want to create or update a layout to a specific version of Visual Studio 2019, go to the [Visual Studio 2019 Releases](/visualstudio/releases/2019/history#installing-an-earlier-release) page. It contains links to fixed-version bootstrappers for each servicing release. Download the one you want, and copy it into the directory that you want to use as the source location for the layout.
@@ -60,7 +60,7 @@ Other supported bootstrappers include [vs_teamexplorer.exe](https://aka.ms/vs/16
60
60
61
61
::: moniker range="=vs-2022"
62
62
63
-
The following bootstrappers always install the latest most secure version of Visual Studio 2022 on the Current channel, no matter when you run them. Alternatively, if you want to create or update a layout to a specific version or a specific channel of Visual Studio 2022, download the evergreen and fixedversion bootstrapper for the servicing release for the channel that you want from[Visual Studio 2022 Release History](/visualstudio/releases/2022/release-history#release-dates-and-build-numbers). Copy it into the directory that you want to serve as the source location of the layout.
63
+
The following bootstrappers always install the latest most secure version of Visual Studio 2022 on the Current channel, no matter when you run them. If you want to create or update a layout to a specific version or a specific channel of Visual Studio 2022, download the appropriate bootstrapper. Both the evergreen and fixed-version bootstrappers for each servicing release and channel are available on the[Visual Studio 2022 Release History](/visualstudio/releases/2022/release-history#release-dates-and-build-numbers) page. Download the one you want, and copy it into the directory that you want to use as the source location for the layout.
@@ -81,7 +81,7 @@ The following bootstrappers always install the latest most secure version of Vis
81
81
::: moniker range=">=vs-2022"
82
82
83
83
>[!TIP]
84
-
>If you previously downloaded a bootstrapper file and want to verify what version it will install, here's how. In Windows, open File Explorer, right-click the bootstrapper file, choose **Properties** and then choose the **Details** tab. The **Product version** field describes the [channel and version](/visualstudio/releases/2022/vs2022-release-rhythm) that the bootstrapper will install. The version number should always be read as "latest servicing version of what is specified", and the channel is assumed to be Current unless explicitly specified. So, a bootstrapper with a Product version of LTSC 17.0 installs the latest 17.0.x servicing release that's available on the 17.0 LTSC channel. A bootstrapper with a Product version that says Visual Studio 2022 installs the latest servicing version of Visual Studio 2022 on the Current channel.
84
+
>If you previously downloaded a bootstrapper file and want to verify the version it installs, here's how. In Windows, open File Explorer, right-click the bootstrapper file, choose **Properties** and then choose the **Details** tab. The **Product version** field describes the [channel and version](/visualstudio/releases/2022/vs2022-release-rhythm) that the bootstrapper installs. The version number should always be read as "latest servicing version of what is specified", and the channel is assumed to be Current unless explicitly specified. So, a bootstrapper with a Product version of LTSC 17.0 installs the latest 17.0.x servicing release that's available on the 17.0 LTSC channel. A bootstrapper with a Product version that says Visual Studio 2022 installs the latest servicing version of Visual Studio 2022 on the Current channel.
0 commit comments