{"id":232203,"date":"2021-04-08T12:59:10","date_gmt":"2021-04-08T19:59:10","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=232203"},"modified":"2021-04-08T17:27:25","modified_gmt":"2021-04-09T00:27:25","slug":"introducing-visual-studio-administrator-updates","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/introducing-visual-studio-administrator-updates\/","title":{"rendered":"Introducing Visual Studio Administrator Updates"},"content":{"rendered":"

During the month of April 2021, Visual Studio will start publishing administrator updates to Visual Studio 2017 and Visual Studio 2019 via Windows Server Update Services<\/a> (WSUS) and the Microsoft Update Catalog<\/a>.\u00a0Enterprises will be able to then use standard deployment tools like Microsoft Endpoint Configuration Manager to easily roll out these updates throughout their organization. In order to take advantage of administrator updates, you\u2019ll need to understand both what they are and how they\u2019re intended to be used.\u00a0You will also need to configure your client machines properly to recognize and accept them.<\/p>\n

This blog post provides a high level summary of Visual Studio administrator updates.\u00a0For further details, refer to the online documentation for how to enable administrator updates<\/a> and then apply administrator updates<\/a>.<\/p>\n

\"Visual<\/a><\/p>\n

Figure 1 – Example Microsoft Endpoint Configuration Manager UI displaying Visual Studio administrator updates<\/em><\/p>\n

 <\/p>\n

Administrator Update Characteristics<\/strong><\/span><\/p>\n

Visual Studio administrator updates will now be available whenever an update is released for any and all Visual Studio servicing versions that are under support<\/a>.\u00a0These updates contain information and instructions that a client machine can use to update itself to a particular version. Note that administrator updates for Visual Studio 2017 and 2019 do not actually contain the updated product bits themselves \u2013 rather the product bits are sourced from either the internet or from a network or private install cache. Also, the administrator updates can only be used to update an instance of Visual Studio already present on the client computer; applying these updates cannot be used to install a new instance of Visual Studio.<\/p>\n

The title of each administrator update describes both the applicable version range of the update as well as the final version that will be applied. In the example above, the \u201cVisual Studio 2019 version 16.9.0 to 16.9.4 update\u201d will be applicable to any clients from versions 16.9.0 through 16.9.3, and it will update them to 16.9.4.<\/p>\n

There are three types of Visual Studio administrator updates.\u00a0Security updates deliver fixes to security vulnerabilities, feature updates contain significant new features and are denoted by an increase in the minor version number, and quality updates contain targeted servicing bug fixes to a particular minor version. The table below lists the key characteristics of administrator updates.<\/p>\n

Table 1 – Characteristics of Visual Studio administrator updates<\/em><\/p>\n\n\n\n\n\n\n\n\n
\u00a0<\/caption>\n
Characteristic<\/span><\/strong><\/td>\nSecurity updates<\/span><\/strong><\/td>\nFeature updates<\/span><\/strong><\/td>\nQuality updates<\/span><\/strong><\/td>\n<\/tr>\n
Available in the Microsoft Update Catalog<\/strong><\/td>\nYes<\/span><\/td>\nYes<\/span><\/td>\nYes<\/span><\/td>\n<\/tr>\n
Available in WSUS<\/strong><\/td>\nYes (automatically)<\/span><\/td>\nOptional manual import<\/a><\/span><\/td>\nOptional manual import<\/a><\/span><\/td>\n<\/tr>\n
Update Category<\/strong><\/td>\nSecurity Updates<\/span><\/td>\nFeature Packs<\/span><\/td>\nUpdates<\/span><\/td>\n<\/tr>\n
SKU Applicability<\/strong><\/td>\nAll Visual Studio editions<\/span><\/td>\nVisual Studio Professional\nVisual Studio Enterprise\n(and the other SKUs used in enterprise environments)<\/span><\/td>\nVisual Studio Professional\nVisual Studio Enterprise\n(and the other SKUs used in enterprise environments)<\/span><\/td>\n<\/tr>\n
Types of changes included as compared to the previous release on that baseline.<\/strong><\/td>\nSecurity fixes<\/span>\nQuality fixes<\/span><\/span><\/td>\nFeature changes\nSecurity fixes\nQuality fixes<\/span><\/td>\nQuality fixes<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Configuring client computers to receive administrator updates<\/strong><\/span><\/p>\n

A few things must be in place in order for the client machines to properly recognize and receive administrator updates.<\/p>\n

First of all, the Visual Studio Client Detector Utility must be installed on the client machines. This utility has been included with all Visual Studio 2017 and Visual Studio 2019 updates since May 2020, and it is included in all administrator updates as a pre-requisite. This utility is also available to independently deploy<\/a> from both WSUS and the Microsoft Update Catalog.<\/p>\n

Secondly, the client computers must have a Visual Studio-specific \u201cadministrator update opt-in\u201d registry key set.\u00a0When the AdministratorUpdatesEnabled <\/strong>REG_DWORD key is set to 1<\/strong>, the client machine can accept the administrator updates. This step is necessary to make sure that the new administrator updates are not unintentionally or accidentally pushed out to unsuspecting client machines.<\/p>\n

In order to minimize disruption to ongoing development activity, there are some configuration options available to Visual Studio users so they can assert some control or preference as to which administrator updates get applied to their machine. They can set the AdministratorUpdatesOptOut,<\/strong> key which will block any administrator updates from applying to the machine. They can also set the BaselineStickinessVersions2019<\/strong> key which expresses a preference for remaining on a particular servicing baseline and prevents a higher administrator feature update from applying. Setting any of these keys requires admin access to the machine.<\/p>\n

Lastly, keep in mind that the Visual Studio application must be closed in order for the administrator update to be successfully deployed to the client machine. If Visual Studio is open or if any files are being used, then the update will be cancelled.<\/p>\n

For an exhaustive list of what the different client configuration options are and how to set them correctly, refer to the Understanding configuration options<\/a> and Methods for configuring an administrator update<\/a> sections in the Applying Administrator Updates online documentation<\/a>.<\/p>\n

 <\/p>\n

Managing where the client machines get the updated product bits from<\/strong><\/span><\/p>\n

For many customers, client machines can download the updated product bits from the internet. Many enterprises however, choose to restrict internet access, allowing instead for client machines to install and update bits from an internal network layout location<\/a>. To ensure that centrally deployed administrator updates can be applied using updated bits that are on an internal network location, the following conditions must be true before the administrator update can be successfully deployed:<\/p>\n