|2. Deploying Visual Studio 2005 through Administrator Mode Setup|
|2.1 Running Administrator Mode Setup|
|2.2 Deploying Visual Studio components individually|
|2.3 Installation Maintenance|
|3. Deploying Visual Studio 2005 using Active Directory|
|3.1 Prerequisites for deploying Visual Studio 2005|
|3.2 Deploying a component using Active Directory|
|3.3 Create the transform for Visual Studio Installation|
|3.4 Using group policy object to create deployment|
|4. Specifying Watson Settings|
|5. Known Installation Issues|
|5.1. Data file cannot be created|
|5.2. Visibility of user-specific data|
|5.3. Installing Visual Studio on Vista|
|6.1. Visual Studio Log File Locations|
|6.2. Windows Installer Error Codes|
|7. Deployment of Visual Studio Service Releases|
Microsoft Visual Studio 2005 offers two ways to facilitate deployment to field clients:
Before running this phase of administrator setup, the required prerequisites for Visual Studio must be installed on the targeted clients. For any of the prerequisites or optional components, Windows Installer 3.1 must be on the target computer. The following is a list of components required for Visual Studio 2005. Visual Studio unattended setup will fail if the prerequisites are not met.
n:\setup\Setup.exe /createunattend <path to .ini file>
D:\setup\setup.exe /createunattend c:\vs2005_deployment.ini
Note:XXXXXXXXXXXXXXXXXXXXXXXXXis the 25 character product key found on the CD packaging. Do not enter the dashes in the product key.[Product Key]
\\<computer>\<share>\...\setup\Setup.exe /unattendfile <path to .ini file>
\\server\VisualStudio\setup\setup.exe /unattendfile \\server\share\vs2005_deployment.ini
For Non-Quiet install:
msiexec /i <path to msdn.msi (at the root of the installation source)> SETUP_EXE=yes
- or -
For Unattended install:
msiexec /qb /i <path to msdn.msi (at the root of the installation source)> SETUP_EXE=yes
- or -
For Silent install:
msiexec /qn /i <path to msdn.msi (at the root of the installation source)> SETUP_EXE=yes
- or -
msiexec.exe /qb /i \\products\VisualStudio\MSDN\msdn.msi SETUP_EXE=yes
Note: For further details on MSDN setup options, please refer to the readme in the top-level MSDN folder.
Network administrators can also deploy Visual Studio 2005 components individually. The following table shows all the Visual Studio components that can be installed unattended along with their locations on the Visual Studio CD or DVD and their silent install commands. For a list of the End User License Agreements, go to http://go.microsoft.com/fwlink/?LinkId=52035.
|Component||Directory||Unattended Install Command|
|Microsoft Windows Installer 3.1||wcu\msi31||WindowsInstaller-KB893803-v2-x86.exe /quiet|
|Microsoft .NET Framework 2.0||wcu\dotnetFramework||dotnetfx.exe /q:a /c:"install /q"|
|Microsoft .NET Framework 2.0 Language Pack||\wcu\dotnetFramework||langpack.exe /q:a /c:"install /q"|
|Microsoft 64 bit .NET Framework||wcu\dotnetFramework\x64||NetFx64.exe /q:a /c:"install /q"|
|Microsoft 64 bit .NET Framework Language Pack||\wcu\dotnetFramework\x64||langpack.exe /q:a /c:"install /q"|
|Microsoft J# Redistributable||wcu\JSharpRedistCore||vjredist.exe /q:a /c:"install /q"|
|Microsoft J# Redistributable Language Pack||wcu\JSharpRedistCore||vjredist-LP.exe /q:a /c:"install /q"|
|Microsoft Visual Studio Tools for Office runtime||wcu\VS Tools for Office||vstor.exe /q:a /c:"install /q"|
|Microsoft Visual Studio Tools for Office runtime Language Pack||wcu\VS Tools for Office||vstolp20.exe /q:a /c:"install /q"|
|Microsoft SQL Server Express||wcu\SSE||SQLExpr.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPR SCCCHECKLEVEL=IncompatibleComponents:1;MDAC25Version:0 SQLAUTOSTART=1 ERRORREPORTING=2 /watsongenman=SQL???.mft ComponentType=3|
|Microsoft Data Access Components||wcu\mdac28||mdac_typ.exe /Q /C:"dasetup /Q /N"|
|Microsoft .NET Compact Framework||wcu\netCF||NetCFSetupv2.msi /qb|
|Microsoft SQL Server 2005 Mobile Edition||wcu\SQLCE||sqlmobile30devtoolsenu.msi /qb|
|Microsoft Device Emulator||wcu\ARM||vs_emulator.exe /q:a /c:"install /q"|
|Microsoft MSXML6||wcu\msxml||msxml6.msi /qb|
|Microsoft 64 bit Visual Studio Prerequisites||wcu\64bitPrereq\x64||vs_bsln.exe /Q|
|Microsoft Document Explorer 2005||wcu\DExplore||DExplore.exe /q:a /c:"install /q"|
|Microsoft Document Explorer 2005 Language Pack||\wcu\DExplore||dexplorelp.exe /q:a /c:"install /q"|
|Microsoft Visual Studio 2005 Code Profiler||wcu\Profiler||vs_profiler.exe /q:a /c:"install /q"|
|Microsoft .NET Framework 2.0 64 bit Software Development Kits||wcu\SDK\x64||setup.exe /q:a /c:"install /q"|
dotnetfx.exe /q:a /c:"install /q"
Setup can be run again on a computer with an existing installation to access setup maintenance features. Users or administrators should run setup from Add or Remove Programs in the Control Panel. To use the maintenance mode of setup, users need to be logged on with administrative permissions on the local computer.
Client computers must have all the system components that Visual Studio 2005 requires installed prior to Visual Studio 2005 installation. Network administrators must verify that all client computers have the required system components. Visual Studio installation will fail if the prerequisites are not met.
Note: It is mandatory that you deploy the required components in the order that they are listed. The component installation setup will fail if they are deployed in a different order. For example, Microsoft .NET Framework 2.0 requires that you install Microsoft Windows Installer 3.1 first, so Windows Installer is listed before the .NET Framework. All the components without an asterisk (*) are located in the WCU folder of the Visual Studio CD or DVD-ROM.
Prerequisites for deploying on Windows 2003 Server
Prerequisites for deploying on Windows 2000
Prerequisites for deploying on Windows XP
Prerequisites for deploying on all Windows Platforms
These components can be installed anytime after the required components for the platform and Visual Studio are installed.
* These components are subjected to their own license agreements.
This section describes the specific procedures for using Active Directory to deploy the Windows Installer setup package for a specific component across a network. To deploy components that require file extraction with administrator privileges, the Windows Installer file must be extracted from the .exe file. For example, to deploy the .NET Framework redistributable package, the Netfx.msi file must be extracted from the .exe file to be used for deployment.
Before installing a Windows Installer setup package on an Active Directory client computer, the client computer must have the Windows Installer installation service installed. The procedure described in this section assumes that Windows Installer 3.1 is installed on all client computers prior to the deployment of any components.
For .NET Framework deployment, there are minimum configuration requirements that must be met prior to installation. For specific software and hardware requirements and recommendations.
The following table shows the list of components that can be deployed using Active Directory. Note that SQL Server Express is not deployable via Active Directory. For a list of the End User License Agreements, go to http://go.microsoft.com/fwlink/?LinkId=52035.
|Component||.exe file or .msi file location||Directory Name||Component Command||File Extraction Required|
|.NET Framework 2.0||wcu\dotnetFramework\dotnetfx.exe||dotnetfx||dotnetfx.exe /q /c:"msiexec /qb /a netfx.msi TARGETDIR=c:\dotnetfx"||√|
|.NET Framework 2.0 Language Pack||wcu\dotnetFramework\langpack.exe||dotnetfx||langpack.exe /q /c:"msiexec /qb /a langpack.msi TARGETDIR=c:\dotnetfx"||√|
|J# Redistributable||wcu\JSharpRedistCore\vjredist.exe||jsredist||vjredist.exe /q /c:"msiexec /qb /a jsredist.msi TARGETDIR=c:\jsredist"||√|
|J# Redistributable Language Pack||wcu\JSharpRedistCore\vjredist-lp.exe||jsredist||vjredist-lp.exe /q /c:"msiexec /qb /a langpack.msi TARGETDIR=c:\jsredist"||√|
|Visual Studio Tools for Office runtime||wcu\VS Tools for Office\vstor.exe||vstor||vstor.exe /q /c:"msiexec /qb /a vsto.msi TARGETDIR=c:\vstor"||√|
|Visual Studio Tools for Office runtime Language Pack||wcu\VS Tools for Office\vstolp20.exe||vstor||vstolp20.exe /q /c:"msiexec /qb /a vstolp20.msi TARGETDIR=c:\vstor"||√|
|Device Emulator||wcu\ARM\vs_emulator.exe||vs_emulator||vs_emulator.exe /q /c:"msiexec /qb /a vs_emulator.msi TARGETDIR=c:\vs_emulator"||√|
|Microsoft Document Explorer 2005||wcu\DExplore\DExplore.exe||DExplore||DExplore.exe /q /c:"msiexec /qb /a dexplore.msi TARGETDIR=c:\DExplore"||√|
|Microsoft Document Explorer 2005 Language Pack||wcu\DExplore\DExplorelp.exe||DExplore||DExplorelp.exe /q /c:"msiexec /qb /a dexplorelp.msi TARGETDIR=c:\DExplore"||√|
|Microsoft Visual Studio 2005 Code Profiler||wcu\Profiler\vs_profiler.exe||vs_profiler||vs_profiler.exe /q /c:"msiexec /qb /a vs_profiler.msi TARGETDIR=c:\vs_profiler"||√|
|Microsoft .NET Framework 2.0 64 bit Software Development Kits||wcu\SDK\x64\setup.exe||netfxsdk||setup.exe /q /c:"msiexec /qb /a netfxsdk.msi TARGETDIR=c:\netfxsdk"||√|
|.NET Compact Framework||wcu\NetCF\NetCFSetupv2.msi||NetCFSetupv2||msiexec /qb /a NetCFSetupv2.msi TARGETDIR=c:\NetCFSetupv2|
|SQL Server 2005 Mobile Edition||wcu\SQLCE\sqlmobile30devtoolsenu.msi||sqlmobile30devtoolsenu||msiexec /qb /a sqlmobile30devtoolsenu.msi TARGETDIR=c:\sqlmobile30devtoolsenu|
|MSXML6||wcu\MSXML\msxml6.msi||msxml6||msiexec /qb /a msxml6.msi TARGETDIR=c:\msxml6|
mkdir [Directory Name]
Since most packages only allow local administrators of the computer to install the package, you should use elevated privileges to advertise the package per-computer in Group Policy. Network administrators can create policies for one user, one computer, or a group of users. See the System Policy Editor Help for more information on creating special policy profiles and the Group Policy snap-in Help for more information on configuring policies.
Note: You can use the System Policy Editor and Windows Installer policy to set the Always install with elevated privileges policy. You must set the policy for the computer and for each user. If you choose not to use the Group Policy Editor or the System Policy Editor, you can specify the same setting on each computer by changing a value in the Windows registry.
To deploy other Visual Studio components, simply repeat Step 1 and add the .msi file to the designated Active Directory Group Policy.
In Windows Installer terminology, a relational database contains information about components, features, and setup properties. A transform is based on a particular package and contains the modifications to apply to that package during installation. This transform provides a full install at the default install location of Visual Studio 2005.
<path to Visual Studio 2005> setup.exe /CreateTransform <filepathname>
D:\setup\setup.exe /CreateTransform c:\mydeploymentfolder\myVSTransform.mst
Refer to Section 3.4 for detail.
The vs_setup.msi file is located at the root of the Visual Studio CD or DVD. Refer to Section 3.2 Step 2 for detail.
If you are deploying Visual Studio in one language to a computer with a different default operating system language:
Note:You will also need to set the "Ignore language when deploying this package" for the .NET Framework language pack and the J# language pack.
Refer to Section 3.2 Step 3 for detail.
An administrative installation point for Visual Studio 2005 and all related files must be created for Active Directory deployment. You must have write access to the administrative installation point on the server and the appropriate privileges to deploy Visual Studio using Active Directory. Visual Studio setup accepts many different command line options. You can create the administrative installation point using the /a command line option. The following table lists all of the command line options for setup:
|Command line option||Description|
|Required only for Windows 98 systems where Msiexec is not directly in the path.|
|Executable file name for Windows Installer.|
|Enables Windows Installer to apply an update to an existing installation.|
[path\name of update MSP file]
|Path and file name of the MSP file for the update.|
|Enables Windows Installer to perform an administrative installation of a product on a network share.|
[path\name of MSI file]
|Path and file name of the Windows Installer package for your original administrative image.|
|Sets the user interface to the basic level (simple progress and error handling).|
|Turns on logging and sets a path for the log file. The *v flag causes the switch to log all information.|
[path\name of log file]
|Path and file name of the Windows Installer log file. If none is given, look for MSI*.log in the temp folder of the computer where command was run.|
[path\name of target folder]
|Path and name of the target folder where admin image will live.|
Use the following syntax for all setup commands:
[start] msiexec /p[path\name of update MSP file]/a[path\name of MSI file]/qb /L*v[path\name of log file]TRANSFORMS =VS2005Tran.mst PIDKEY = <25 character product key with no spaces or dashes>TARGETDIR=[path\name of target folder]
[start] msiexec /a[path\name of MSI file]TRANSFORMS=<name of transform file created in section 3.3 Step 1>PIDKEY= <25 character product key with no spaces or dashes>
Note: If you are deploying an edition of Visual Studio that uses a product key pre-populated by setup, you need to locate the product key (PID) and enter the correct sequence as the value for PIDKEY.
To locate the product key
You can configure how Visual Studio Watson behaves on individual computers using the following registry sub-key:
under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PCHealth\ErrorReporting\ DW\VSSetup\Product Name Value\Product Version Number
Replace Name Value\Product Version Number with the values for VSSWProdName and VSSWProdVer flags specified in the file setup.sdb located at n:\setup\ on the installation CD or DVD-ROM.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PCHealth\ErrorReporting\DW\VSSetup\Visual C# 2005 Express Edition Beta\8.0.xxxx]
If you run setup in createunattend mode with a file that already exists, the following error appears: "The data file <filename> cannot be created. Setup cannot continue."
To correct this error, either delete the existing file, or provide a unique file name.
When you create an unattended install file, some user-specific data might appear in the file. Specifically, the name of the user who created the file and their organization name appear as two line items:
You can change the values of these variables before using the .ini file, but do not delete the lines completely.
Visual Studio setup attempts to install .NET Framework 2.0 but fails if the 2.0 Framework is already installed on the machine. On a Vista machine, this will fail because the 2.0 Framework is already is built into the operating system.
To correct this issue you can edit the unattend .ini file to prevent VS unattended setup from attempting to install .NET Framework 2.0.
The following log files are generated during Visual Studio 2005 setup:
During Visual Studio setup , the log files are located in the %temp% directory. For example:
C:\Documents and Settings\[User Name]\Local Settings\Temp
After Visual Studio installation , the log files are located in the Logs directory in the path that Visual Studio is installed. For example:
C:\Program Files\Microsoft Visual Studio 8\[Product Name]\Logs
After a Visual Studio failed installation and uninstallation , the log files are left in the %temp% directory.
Note: For other Visual Studio components, such as the Microsoft SQL Server Express, the Visual Studio .NET Framework, and the Visual Studio J# Redistributable Package, also generate log files. These files can be found under the %temp% directory or under [Drive]:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
To view the list of error codes, go to http://go.microsoft.com/fwlink/?LinkId=51677
For information on downloading and deploying Visual Studio Service Releases, see http://go.microsoft.com/fwlink/?LinkId=10605.