In this post I will demonstrate how I deployed Visual Studio Professional 2013 using Configuration Manager 2012 R2. In part two, I will show how I deployed Cumulative Update 3.
1 – The first step is to mount the Visual Studio iso and copy the contents to wherever you store your application files on your Configuration Manager server.
2 – In order to prevent going to the web during setup, I then modified the ‘AdminDeployment.xml’ file as per the instructions found here: http://msdn.microsoft.com/en-us/library/ee225237.aspx
As you can see there are various other customisation options you can make to this file.
Here’s my AdminDeployment.xml file before the modification:
And here it is after I edited it:
3 – Next, In the Configuration Manager Console I created a new Application and chose to ‘Manually specify the application information’
4 – Complete the General Information fields as you see fit:
5 – If you are going to make this application available to the Catalog, then complete the fields that you feel are appropriate:
6 – To create a new deployment type, click the ‘Add’ button:
7 – Change the type to ‘Script Installer’ :
8 – Give the deployment type a meaningful name:
9 – Browse to your content location. For the installation program I typed the following:
“vs_professional.exe” /Admin File AdminDeployment.xml /q /norestart
If you wish to see other parameters that you can add, in a command prompt, browse to the directory that contains vs_professional.exe and type: vs_professional.exe /?
Note that I chose to supress reboots. Once installed, a balloon-tip will appear notifying the user that a restart is required.
Don’t forget to add the uninstall details:
10 – We then need to add a detection clause:
11 – I decided to use the file version for devenv.exe for the detection clause:
12 – So mine looks like this:
13 – Click next when you are at this point:
14 – For the user experience, I configured my settings like this, though feel free to season to taste:
15 – Click the Add’ button if you wish to add any Installation requirements for this deployment:
16 – Add any requirements as you see fit, I’ve just added some basic ones in this example:
17 – Here’s the finished result of your requirements:
18 – If you have any dependent applications that you wish to add then here is where you do it. I did not so, click next:
19 – You are presented with a summary screen:
20 – …and another:
21 – If you had another deployment type, you could click ‘Add’ and create another. I did not so click the next button:
22 – Confirm your settings:
23 – …and we’re done:
24 – Don’t forget to distribute this to your distribution points and now would be a good time to test this deployment to a user \ computer before we go ahead and look at deploying Update 3.