Up to Visual Studio 2010 the unattended installation was made up of many steps, making a journey into a .ini file…
With Visual Studio 2012, the new experience is pretty faster, cleaner and easier.
The first thing to do is to create a Network Image, to be used into the company to deploy Visual Studio 2012. You have to create a X:/IDEinstall folder.
Then the only needed step is to customize the AdminDeployment.xml file! I won’t go deep dive on the schema as the MSDN documentation is self-explanative, but it can be summarized as it: you can choose which component to install in a Yes|No binary choice.
Once the AdminDeployment.xml file is customized as you want, you just have to grant the share all the required permissions and the users are automatically going to install Visual Studio with the defined settings.
Otherwise a silent installation is possible using the following command line statement:
\\ServerName\IDEinstall\vs_Product.exe /adminfile AdminDeployment.xml /quiet /norestart
This statement is also the way of managing Visual Studio installations, both quiet and interactive. Again, everything relies on the AdminDeployment.xml file.