How to deploy Visual Studio 2013 and Update 3 using Configuration Manager 2012 (Part 1)

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.

3 - Edit AdminDeployment

Here’s my AdminDeployment.xml file before the modification:

4 - Admin Before Edit

And here it is after I edited it:

5 - Admin after Edit

3 – Next, In the Configuration Manager Console I created a new Application and chose to ‘Manually specify the application information’

1 - Manually Specify the application

4 – Complete the General Information fields as you see fit:

2 - Specify General info

 

5 – If you are going to make this application available to the Catalog, then complete the fields that you feel are appropriate:

3 - App user info

6 – To create a new deployment type, click the ‘Add’ button:

4 - Click the Add button

7 – Change the type to ‘Script Installer’ :

5 - Change to Script Installer

8 – Give the deployment type a meaningful name:

6 - Name the deployment type

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:

7 - Deployment type content locations

10 – We then need to add a detection clause:

8 - Add Clause

11 – I decided to use the file version for devenv.exe for the detection clause:

9 - File Version

12 – So mine looks like this:

10 - Finished detection rule

13 – Click next when you are at this point:

11 - Detection rule summary

14 – For the user experience, I configured my settings like this, though feel free to season to taste:

12 - User experience

15 – Click the Add’ button if you wish to add any Installation requirements for this deployment:

13 - Specify reqs

16 – Add any requirements as you see fit, I’ve just added some basic ones in this example:

14 - Configured reqs

17 – Here’s the finished result of your requirements:

14 - Configured reqs

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:

15 - Dependencies

19 – You are presented with a summary screen:

16 - Summary

20 – …and another:

17 - Summary2

21 – If you had another deployment type, you could click ‘Add’ and create another.  I did not so click the next button:

18 - No more deployment types to add

22 – Confirm your settings:

19 - Confirm Settings

23 – …and we’re done:

20 - Application creation success

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.

 

1 Comment

Leave a Reply

Your email address will not be published.


*