Now that Visual Studio 2010 SP1 has been released, administrators and developers may wish to install both RTM and SP1 together for a seamless experien ...
Now that Visual Studio 2010 SP1 has been released, administrators and developers may wish to install both RTM and SP1 together for a seamless experience. With the release of VS2010 RTM we already published the Visual Studio Administrator Guide that documents a lot of the instructions I’ll utilize below. I encourage you to review that before proceeding with the following instructions, particularly how to avoid restarts during setup by pre-installing certain packages like Windows Installer 4.5 and .NET Framework 4.0.
How to: Create and run an unattended Visual Studio with SP1 setup
You’ll create a distribution point that will contain both Visual Studio 2010 RTM and SP1. This will work for existing installations of VS 2010 since setup will simply repair the product if it’s already installed. This has the added benefit that if any files are missing from the target machine, they should be reinstalled without a prompt for source during the SP1 install.
Creating a network or local image
First you’ll be creating copies of the Visual Studio 2010 RTM and SP1 installations that you can share out or install locally.
- Create a network or local image of Visual Studio setup as documented in How to: Create and Run an Unattended Visual Studio Setup.
- You do not need to pre-populate the product key, but the developer will be prompted for it when first starting Visual Studio. Pre-populating the product key is recommended for administrators deploying to multiple machines through volume licensing.
- You do not need to create an unattend.ini file if you want to install all features. Running setup.exe /q /norestart will install all features.
- If you do want to create an unattend.ini file, run setup\setup.exe /createunattend <drive>:\VS2010\unattend.ini and not setup.exe in the root. You should run this on the same operating system platform and architecture that you want to target.
- Creating the network or local image for Visual Studio 2010 documentation is also optional. SP1 will upgrade the Help Viewerregardless.
- Create a subdirectory under <drive>:\VS2010 or wherever you created the image from step 1 named “SP1”.
- Download Visual Studio 2010 Service Pack 1 and save to %TEMP% or any other location you like except in the directory you just created in step 2.
- Open a command prompt (you can open it elevated now, or confirm the elevation prompt when requested later) and change directories to where you saved the SP1 web installer in step 3.
- Run VS10sp1-KB983509.exe /createlayout <drive>:\VS2010\SP1 to download all packages to the directory you created in step 2.
Creating the unattend.bat file
Next you’ll be creating a batch install that will first install Visual Studio 2010 RTM followed by SP1. You can use any batch or scripting language you like so long as it is already supported on target machines. The example below uses the Windows batch language to make use of tokens like %~dp0 which provides the parent path to the batch script. This is handy in case you change the network or local image location in the future.
- Create a batch file named unattend.bat in the directory you created in step 1 and open it in notepad.exe or your favorite vanilla text editor.
- (Recommended) Add a simple check to determine if the batch script is processed in an elevated process. See the attached batch script for an example.
- Add the path to setup.exe in VS2010 with the following options.
- Full install with no unattend.ini file:
"%~dp0setup\setup.exe" /q /norestart - Custom install with unattend.ini file:
"%~dp0setup\setup.exe" /q /norestart /unattendfile "%~dp0unattend.ini"
- Full install with no unattend.ini file:
- (Optional) If you want to install Visual Studio 2010 documentation locally as documented in the Administrator Guide, add the command to HelpLibManager.exe next, ex:
"%ProgramFiles%\Microsoft Help Viewer\v1.0\HelpLibManager.exe" /silent /product VS /version 100 /locale en-US /content "%ProgramData%\Microsoft\HelpLibrary" /sourceMedia "%~dp0ProductDocumentation\HelpContentSetup.msha" - Add the path to setup.exe in VS2010\SP1 with the following option.
- Restart after install (recommended):
"%~dp0SP1\setup.exe" /q - Do not restart after install (Visual Studio or .NET Framework may not work until you do, but subsequent installs may work before rebooting):
"%~dp0SP1\setup.exe" /q /norestart
- Restart after install (recommended):
You might consider adding some error processing for reboot return codes after each command. See the attached batch script for an example.
Running unattended setup
If you plan on deploying Visual Studio 2010 with SP1 over the network, you can share out the location you created above, ex: <drive>:\VS2010. As noted in the Administrator Guide, spaces in the share path may cause setup to fail so its best you avoid using spaces.
Since the batch file already passes the right options to the installers, the deployment scripts or developers can execute unattend.bat in an elevated command prompt directly.
How to: Deploy Visual Studio with SP1 using Microsoft System Configuration Manager (SCCM)
You’ll use the distribution point you created above to create or modify a package for SCCM to install Visual Studio 2010 RTM and SP1. You’ll follow the process documented in How to: Deploy Visual Studio Using Microsoft System Configuration Manager (SCCM) and add a program to the package after Visual Studio.
- Create the network image as documented above in the section “Creating a network or local image”.
- Follow the instructions in How to: Deploy Visual Studio Using Microsoft System Configuration Manager (SCCM) up till and including “Create a Program That has Setup and Installation Parameters for Visual Studio”.
- Create a program for the Visual Studio 2010 SP1 package.
- Right-click on Programs, point to New, and then click Program.
- On the General page, type a name for the package in the Name box, which in this example is “Visual Studio 2010 SP1 silent installation” (without quotes).
- In the Command line box, type: SP1\setup.exe /q /norestart
- In the Run list, select Hidden.
- In the After running list, verify that No action required is selected. Click Next, and then on the Requirements page click Nextagain.
- On the Environment page, in the Program can run list, select whether a user must be logged on. This will enable Run with administrative rights for the Run mode. Leave Drive mode set to Runs with UNC name, and then click Next.
- On the Advanced page, select Suppress program notifications. Also select Run another program first and then select the “Visual Studio 2010 Package” and the “Visual Studio 2010 silent installation” Program. Click Next.
- On the Windows Installer page, click Next.
- Click Next and then on the MOM Maintenance Mode page click Next again.
- To view the Summary page, click Next.
- To finish creating the new program, click Next, and then on the Wizard Completed page click Close.
- Continue the instructions in How to: Deploy Visual Studio Using Microsoft System Configuration Manager (SCCM) with “Select a Distribution Point”.
The documentation cited above from the Administrators Guide has a number of help links to more information about Active Directory and SCCM.
PS：
不得不說現在 Visual Studio 2010 已經相當老舊，今年的 Visual Studio 2017 發佈已久，早已迭代了好幾個版本。
但有些情況下，還是需要用到 Visual Studio 2010 做開發，這是不得已的事情。
所以每次在新系統上安裝 Visual Studio 2010 完畢後，還要再裝載 SP1 ISO 鏡像並且安裝。
這很麻煩，網上又沒有集成版的安裝包，那到底能不能兩次安裝合併為一次，並且做到無人值守安裝呢，答案是可以的。
事實上，我更 傾向/喜歡 用 Visual Studio 2017 做開發，而且是越新越好。
嗯，我有強迫症...
Now that Visual Studio 2010 SP1 has been released, administrators and developers may wish to install both RTM and SP1 together for a seamless experience. With the release of VS2010 RTM we already published the Visual Studio Administrator Guide that documents a lot of the instructions I’ll utilize below. I encourage you to review that before proceeding with the following instructions, particularly how to avoid restarts during setup by pre-installing certain packages like Windows Installer 4.5 and .NET Framework 4.0.
How to: Create and run an unattended Visual Studio with SP1 setup
You’ll create a distribution point that will contain both Visual Studio 2010 RTM and SP1. This will work for existing installations of VS 2010 since setup will simply repair the product if it’s already installed. This has the added benefit that if any files are missing from the target machine, they should be reinstalled without a prompt for source during the SP1 install.
Creating a network or local image
First you’ll be creating copies of the Visual Studio 2010 RTM and SP1 installations that you can share out or install locally.
- Create a network or local image of Visual Studio setup as documented in How to: Create and Run an Unattended Visual Studio Setup.
- You do not need to pre-populate the product key, but the developer will be prompted for it when first starting Visual Studio. Pre-populating the product key is recommended for administrators deploying to multiple machines through volume licensing.
- You do not need to create an unattend.ini file if you want to install all features. Running setup.exe /q /norestart will install all features.
- If you do want to create an unattend.ini file, run setup\setup.exe /createunattend <drive>:\VS2010\unattend.ini and not setup.exe in the root. You should run this on the same operating system platform and architecture that you want to target.
- Creating the network or local image for Visual Studio 2010 documentation is also optional. SP1 will upgrade the Help Viewerregardless.
- Create a subdirectory under <drive>:\VS2010 or wherever you created the image from step 1 named “SP1”.
- Download Visual Studio 2010 Service Pack 1 and save to %TEMP% or any other location you like except in the directory you just created in step 2.
- Open a command prompt (you can open it elevated now, or confirm the elevation prompt when requested later) and change directories to where you saved the SP1 web installer in step 3.
- Run VS10sp1-KB983509.exe /createlayout <drive>:\VS2010\SP1 to download all packages to the directory you created in step 2.
Creating the unattend.bat file
Next you’ll be creating a batch install that will first install Visual Studio 2010 RTM followed by SP1. You can use any batch or scripting language you like so long as it is already supported on target machines. The example below uses the Windows batch language to make use of tokens like %~dp0 which provides the parent path to the batch script. This is handy in case you change the network or local image location in the future.
- Create a batch file named unattend.bat in the directory you created in step 1 and open it in notepad.exe or your favorite vanilla text editor.
- (Recommended) Add a simple check to determine if the batch script is processed in an elevated process. See the attached batch script for an example.
- Add the path to setup.exe in VS2010 with the following options.
- Full install with no unattend.ini file:
"%~dp0setup\setup.exe" /q /norestart - Custom install with unattend.ini file:
"%~dp0setup\setup.exe" /q /norestart /unattendfile "%~dp0unattend.ini"
- Full install with no unattend.ini file:
- (Optional) If you want to install Visual Studio 2010 documentation locally as documented in the Administrator Guide, add the command to HelpLibManager.exe next, ex:
"%ProgramFiles%\Microsoft Help Viewer\v1.0\HelpLibManager.exe" /silent /product VS /version 100 /locale en-US /content "%ProgramData%\Microsoft\HelpLibrary" /sourceMedia "%~dp0ProductDocumentation\HelpContentSetup.msha" - Add the path to setup.exe in VS2010\SP1 with the following option.
- Restart after install (recommended):
"%~dp0SP1\setup.exe" /q - Do not restart after install (Visual Studio or .NET Framework may not work until you do, but subsequent installs may work before rebooting):
"%~dp0SP1\setup.exe" /q /norestart
- Restart after install (recommended):
You might consider adding some error processing for reboot return codes after each command. See the attached batch script for an example.
Running unattended setup
If you plan on deploying Visual Studio 2010 with SP1 over the network, you can share out the location you created above, ex: <drive>:\VS2010. As noted in the Administrator Guide, spaces in the share path may cause setup to fail so its best you avoid using spaces.
Since the batch file already passes the right options to the installers, the deployment scripts or developers can execute unattend.bat in an elevated command prompt directly.
How to: Deploy Visual Studio with SP1 using Microsoft System Configuration Manager (SCCM)
You’ll use the distribution point you created above to create or modify a package for SCCM to install Visual Studio 2010 RTM and SP1. You’ll follow the process documented in How to: Deploy Visual Studio Using Microsoft System Configuration Manager (SCCM) and add a program to the package after Visual Studio.
- Create the network image as documented above in the section “Creating a network or local image”.
- Follow the instructions in How to: Deploy Visual Studio Using Microsoft System Configuration Manager (SCCM) up till and including “Create a Program That has Setup and Installation Parameters for Visual Studio”.
- Create a program for the Visual Studio 2010 SP1 package.
- Right-click on Programs, point to New, and then click Program.
- On the General page, type a name for the package in the Name box, which in this example is “Visual Studio 2010 SP1 silent installation” (without quotes).
- In the Command line box, type: SP1\setup.exe /q /norestart
- In the Run list, select Hidden.
- In the After running list, verify that No action required is selected. Click Next, and then on the Requirements page click Nextagain.
- On the Environment page, in the Program can run list, select whether a user must be logged on. This will enable Run with administrative rights for the Run mode. Leave Drive mode set to Runs with UNC name, and then click
