How to install Visual Studio 2012 Update 2 using Configuration Manager 2012

** UPDATE ** How to install CU3 – Click here.

Installing Visual Studio 2012 Update 2 using Configuration Manager 2012 is a fairly straightforward process.  The longest part will be downloading the  update itself.

In my research it appears that this cannot be slipstreamed into the existing Visual Studio product  but it is, however, cumulative.  This means that if you have not already installed Update 1, then you do not need to worry as it’s all included in update 2.

With that in mind, lets crack on.

a.  First, you’ll need to download the web installer from Microsoft’s website.  I got mine from here. (Update: 29 Jan 2015 – This link no longer exists as there is a newer CU available now)

b.  Once the download is complete, open a command prompt, navigate to the download location, and run the command: VS2012.2.exe /layout (as per the screenshot below)



c.  You will then be prompted to select a location to download all of the components to.  So do that and then press the Download button:


This process may take a while depending on your Internet speed.  When it’s finished, browse to the download location you chose in step c (above) and you should have something like this:




d.  Now copy the whole of the packages directory and the VS2012.2.exe to a location on your Configuration Manager server where you would normally place your application deployment source files.  (Ensure that the vs2012.2.exe remains outside of the packages folder exactly as shown in the screenshot in step c)

Creating the application:

Now we’ve done all of that, it’s time to create the actual application.  So fire up the Configuration Manager console, and create a new application…

1.  Create Application Wizard \ General screen:  Ensure that type is set to ‘Windows Installer (Native)’ and that you have selected ‘Manually specify the application information’



2.  Specify information about this application screen: Give the application a meaningful name and fill in the rest of the fields as you desire.



3.  Application Catalog screen:  Fill in as much detail as you like here.  If you are going to be making this application available to users in the Application Catalog then you may wish to add a lot more detail than I have in my screenshot.



4.  Deployment Types screen:  Click the Add button



5.  General screen:  Ensure that type is set to ‘Script installer (Native) and that you have selected ‘Manually specify the deployment type information’



6.  General Information screen: Enter a meaningful name and complete the rest of the fields as you wish.



7.  Content screen:  Browse to the directory where you placed the package directory and vs2012.2.exe on your Configuration Manager 2012 server.  Enter the information shown in the screenshot for the ‘Installation Program’ and ‘Uninstall program’ fields:



8.  Detection Method screen:  Click on the ‘Add Clause’ button



9.  Detection rule dialog:  I chose to use the executable that launches Visual Studio, as the vanilla installation gives the version number of:  11.0.50727.1  and the Update 2 version changes it to: version:11.0.60315.1

With that in mind, ensure your detection rule looks like the one in my screenshot:



10.  Detection Method screen:  Now we have a detection method, click the next button.



11.  User Experience screen:  Change the installation behaviour to ‘Install for system’ and the logon requirement to: Whether or not a user is logged on’  The max allowed run time and estimated install time I’ll leave to you…



12.  Requirements screen:  Click on the Add button so that we can add some system requirements for this application.



13.  Create Requirement dialog:  I chose to limit this application to WIndows 7SP1 x86 and x64 computers.  Feel free to add RAM, free disk space or whatever suits your environment here.



14.  Now we have some requirements set, click on the Next button.



15.  Dependencies screen:  If you already have an application that deployed Visual Studio 2012, it’s a good idea to add it as a dependency as an additional fail-safe to ensure that this update will not install unless the Visual Studio 2012 has been installed and is present.  (If you need step-by-step instructions on how to deploy Visual Studio 2012 using Configuration Manager 2012 then please refer to my post here.)

So click on the ‘Add’ button…



16.  Dependency Dialog:  Create a new dependency, give it a dependency group name and browse to your existing application that deploys Visual Studio 2012.  Ensure that the ‘Auto Install’ check-box is empty.  This is important as if you select auto-install then this update application will fail.  I tried ticking the auto-install check box then deployed my Update 2 application thinking that I could then deploy on application to new computers \ users that required VS2012 (As auto install was checked it would first install .net4.5 followed by vs2012 followed by this application) and I also thought I could deploy this very same application to computers that already have VS2012 installed but not update 2 (as they would have passed the dependency check)  However, when I tried this on a computer that did not have VS2012 installed, I found that the application stayed in a failed state due to the computer requiring a reboot from the .net4.5 installation.  Depending on how you set up your VS2012 application you may find you can get away with it – in my VS2012 application I chose to suppress reboots, hence the error.

Phew..that was a long that’s all been said, here’s a screenshot of what I did:



17.  Dependencies screen:  Now we have set up our dependencies, click next…



18.  Summary screen:  Take a gander at the summary screen before committing your actions by clicking the next button:



19.  Completion screen:  Success!



20.  Deployment Types screen:  Now we have a deployment type, click next.



21.  Summary screen:  If you are happy with the summary, click next:



22.  Completion screen:  Success!




Now all you have to do is distribute the application to your distribution point and deploy to either a computer collection or user groups if you wish to make it visible in the Application Catalog.

Here’s a screenshot I took in Visual Studio in Help \ about before the update:




And here’s what it looked like after the update rolled out:




That’s it!




  1. Thanks for the easy-to-follow, helpful articles! I used your directions to deploy Visual Studio 2012 Update 3 through MDT 2012 (into an image).

  2. ozthe2 is da man!

    Seriously, oz, thanks so much for this clear, well illustrated post. I never would imagine that I could successfully deploy VS2013 AND CU3 on the first try, and without having to pull additional info from other sites.

    If you’d like to update this post to reflect the now-released CU3, the version number after installing is now 11.0.60610.01. Use this in place of the CU2 version and your deployment won’t “fail” because “The application was not detected after installation completed.”

    Again, thanks a ton for the help.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.