6.

Deploying Visual Studio 2008 using Active Directory

6.1 Deploying a component using Active Directory

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 (.msi) must be extracted from the .exe file.

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, see "Deploying & Configuring
Applications" at http://go.microsoft.com/fwlink/?LinkId=52324

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.

Table 2. A list of Visual Studio components that can be deployed using Active Directory.

Component .exe file or .msi file Directory Name Component Command File
location Extrac
tion
Requir
ed

Microsoft x86:  
Core XML WCU\dotNetFramework\
Services dotNetFX30\x86\msxml
(MSXML) 6.0 6.msi 
msxml6 msiexec /qb /a msxml6.msi TARGETDIR=c:\msxml6
x64:
WCU\dotNetFramework\
dotNetFX30\x64\msxml
6.msi

Software x86: x86:  

Rasterizer for WCU\dotNetFramework\ msiexec /qb /a RGB9RAST_x86.msi
the Microsoft dotNetFX30\RGB9RAS REBOOT=ReallySuppress
DirectX 9.0 T_x86.msi TARGETDIR=c:\RGBRAST
Software rgbrast
Development x64: x64:
Kit (SDK) WCU\dotNetFramework\ msiexec /qb /a RGB9RAST_x64.msi
dotNetFX30\RGB9RAS REBOOT=ReallySuppress
T_x64.msi TARGETDIR=c:\RGBRAST

.NET WCU\dotNetFramework\ dotNetFX20 x86:  

Framework dotNetFX20 msiexec /a netfx20a_x86.msi /update
2.0 SP1 ASPNET.msp;CLR.msp;CRT.msp;NetFX_CA.msp;
NetFX_Core.msp;NetFX_Other.msp;PreXP.msp;Wi
nForms.msp;DW.msp 
USING_EXUIH=1 REBOOT=ReallySuppress /l*
%TEMP%\logs\netfx20sp1_x86.log
 TARGETDIR=c:\dotNetFX20

x64:
msiexec /a Netfx20a_x64.msi /update
ASPNET_64.msp;CLR_64.msp;CRT_64.msp;DW_6
4.msp;
NetFX_Core_64.msp;NetFX_Other_64.msp;WinFor
ms_64.msp;ASPNET.msp;CLR.msp;CRT.msp;NetF
X_CA.msp;
NetFX_Core.msp;NetFX_Other.msp;PreXP.msp;Wi
nForms.msp;DW.msp 

USING_EXUIH=1 REBOOT=ReallySuppress /l*

%TEMP%\netfx20sp1_x64.log
TARGETDIR=c:\dotNetFX20 

Note: each .msp file must be preceded by its full

path.

.NET x86:  
Framework msiexec /a netfx30a_x86.msi /update
3.0 SP1 WCF.msp;WCS.msp;WF.msp;WPF1.msp;WPF2.ms
p;WPF_Other.msp;
XPS.msp;WF_32.msp;WPF2_32.msp;WPF_Other_
32.msp 

USING_EXUIH=1 REBOOT=eallySuppress /l*

%TEMP%\netfx30sp1_x86.log
TARGETDIR=c:\dotNetFX30

WCU\dotNetFramework\ x64:
dotNetFX30
dotNetFX30 msiexec /a netfx30a_x64.msi /update
WCF.msp;WCS.msp;WF.msp;WPF1.msp;WPF2.ms
p;
WPF_Other.msp;XPS.msp;WCF_64.msp;WCS_64.
msp;WF_64.msp;WPF1_64.msp;WPF2_64.msp;
WPF_Other_64.msp 
USING_EXUIH=1 REBOOT=ReallySuppress /l*
%TEMP%\netfx30sp1_x64.log
TARGETDIR=c:\dotNetFX30 

Note: each .msp file must be preceded by its full

path.

.NET x86:
Framework WCU\dotNetFramework\
3.5 dotNetFX35\x86\netfx35
_x86.exe msiexec /qb /a vs_setup.msi USING_EXUIH=1
dotNetFX35 REBOOT=reallySuppress √
x64: TARGETDIR=c:\dotNetFX35
WCU\dotNetFramework\
dotNetFX35\x64\netfx35
_x64.exe

Microsoft
WCU\DExplore\DExplor DExplore.exe /q /c:"msiexec /qb /a dexplore.msi
Document DExplore √
e.exe TARGETDIR=c:\DExplore"
Explorer 2008

.NET WCU\NetCF\NetCFSetu NetCFSetupv2 msiexec /qb /a NetCFSetupv2.msi  

Compact pv2.msi
Framework TARGETDIR=c:\NetCFSetupv2

.Net Compact  
WCU\NetCF\NetCFSetu msiexec /qb /a NetCFSetupv35.msi
Framework NetCFSetupv35
pv35.msi TARGETDIR=c:\NetCFSetupv35
v3.5

Microsoft
Visual Studio
2005 Tools
WCU\VS Tools for vstor.exe /q /c:"msiexec /qb /a vsto.msi
for the 2007 vstor √
Office\vstor.exe TARGETDIR=c:\vstor"
Microsoft
Office System
Runtime

Microsoft
Visual Studio
Tools for the
WCU\VS Tools for vstor30.exe /q /c:"msiexec /qb /a trin_trir.msi
Microsoft vstor30 √
Office\vstor30.exe TARGETDIR=c:\vstor30"
Office system
(version 3.0
Runtime)

Windows
Mobile 5.0 WCU\WindowsMobileS WindowsMobileS msiexec /qb /a MagOrcasPPC.msi
 
SDK R2 for DK\MagOrcasPPC.msi DK TARGETDIR=c:\WindowsMobileSDK
Pocket PC

Windows  
Mobile 5.0 WCU\WindowsMobileS WindowsMobileS msiexec /qb /a MagOrcasSP.msi
SDK R2 for DK\MagOrcasSP.msi DK TARGETDIR=c:\WindowsMobileSDK
Smartphone

Device Vista x64 only: Vista x64 only:

Emulator WCU\ARM\vs_emulator vs_emulator_x64_vista.exe /q /c:"msiexec /qb /a
_x64_vista.exe sde_vsd64.msi TARGETDIR=c:\vs_emulator"
vs_emulator √
Other platforms: Other platforms:
WCU\ARM\vs_emulator. vs_emulator.exe /q /c:"msiexec /qb /a sde_vsd.msi
exe TARGETDIR=c:\vs_emulator"

Microsoft x86: x86:

Visual Studio WCU\Profiler\PerfCollec PerfCollectionTools_x86.exe /q /c:"msiexec /qb /a
2008 tionTools_x86.exe dynamicanalysis_collectionbits.msi
Performance TARGETDIR=c:\vs_profiler"
Collection x64: vs_profiler √
Tools WCU\Profiler\PerfCollec x64:
tionTools_x64.exe PerfCollectionTools_x64.exe /q /c:"msiexec /qb /a
dynamicanalysis_collectionbits.msi
TARGETDIR=c:\vs_profiler"

Step 1: Create the administrator install point

1. Download the .exe file or the .msi/msp(s) on to the C:\ drive on your local computer.
2. From the Start menu, choose Run.
 3. Type in CMD, and press OK.

4. Change the directory to the root of the C:\ drive.

cd c:\

5. At the command prompt, type the following to create a directory in which to copy the .exe file:

mkdir [Directory Name]

6. Copy the file to the directory created in item 5.

7. Extract the file, if it is marked for extraction in Table 2.

8. Create target directory.

9. Type the corresponding Component Command (see Table 2) to create the install point in the directory

10. Close the command prompt window.

11. Open Windows Explorer and navigate to c:\[Directory Name] to verify that the files were extracted.

12. Move the target folder and all its contents to the network share you intend to use for deployment.

13. Copy the .msi file from the source to the network share.

Step 2: Add a setup package to an Active Directory Group Policy

1. From the Start menu, choose Programs and then choose Administrative Tools.

2. Choose Component Services and then expand Active Directory Users and Computers. The Active
Directory Users and Computers tree is displayed.

3. Right-click the Domain node and then choose Properties.

4. In the Properties dialog box, choose the Group Policy tab and then click Edit.

5. If you intend to set policies that apply to computers regardless of who logs on to them, expand Computer
Configuration\Software Settings. 
Note: Ensure that you map to the shared location on the Active Directory server; otherwise, it will not let
you create a package for installation.

6. Right-click Software installation, choose New and then choose Package.

7. In the Open dialog box, browse to the location where you copied the deployment folder, and select the
.msi file.

8. In the Deploy Software dialog box, choose Assigned and then click OK.

9. Choose Auto Install to install the software automatically on every computer in the domain.

10. Click OK and then exit the Active Directory Users and Computers console.

Step 3: Set the Elevated Privileges via Group Policy

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.

1. From the Start menu, choose Programs and then choose Administrative Tools.

2. Choose Component Services and then expand Active Directory Users and Computers. The Active
Directory Users and Computers tree is displayed.
 3. Right-click the Domain node and then choose Properties.

4. Select the Group Policy tab.

5. In the Group Policy Objects Links box, select a Group Policy Object and then click Edit.

6. Open the Local Computer Policy\Administrative Templates\Windows Component\Windows Installer

folder.

7. In the details pane, double-click the Always install with elevated privileges policy.

8. In the Group Policy Property dialog box, enable the policy, select the check box to turn the setting on,
and then click OK.

9. Open the User Configuration\Administrative Templates\Windows Component\Windows Installer folder

and repeat Steps 8 and 9.

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.

Step 4: Verify that package is ready to be assigned to computers

1. [Component Name] - English Properties dialog box, select the Deployment tab.

2. Under Deployment type choose Assigned.

3. Under Deployment options, select the correct options for when and how to deploy the component.

4. Browse the other available tabs and make choices as necessary. For details, see Group Policy Help
available in the dialog box.

Step 5: Deploy other required components

To deploy other Visual Studio components, simply repeat Step 1 and add the .msi file to the designated Active
Directory Group Policy.

Back to the top

6.2 Create the transform for Visual Studio Installation

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 2008.

Step 1: Create the transform

1. From the Start menu, choose Run.

2. Type the following:

<path to Visual Studio 2008>\Setup\setup.exe /CreateTransform <path to Visual

Studio 2008>setup.exe /CreateTransform <filepathname>

For example:

D:\Setup\setup.exe
/CreateTransform C:\MyDeploymentFolder\myVSTransform.mst

3. Follow the directions on the Start page of setup and then click Continue.

 4. On the Options page, select the features you intend to deploy, and then click Create Transform.

Step 2: Create the administrative installation point

Refer to Section 6.3 for detail.

Step 3: Add the Visual Studio 2008 setup package to Group Policy

The vs_setup.msi file is located at the root of the Visual Studio CD or DVD.  Refer to Section 6.1 Step 2 for detail. 
If you are deploying Visual Studio in one language to a computer with a different default operating system
language:

1. Open the Group Policy Object Editor for your domain & policy.

2. Open the properties of the Visual Studio 2008 <language> package.

3. Click the Deployment tab.

4. Click the Advanced... button.

5. Check the box for Ignore language when deploying this package.

6. Click OK.

7. Click OK.

Note: You will also need to set the "Ignore language when deploying this package" for the .NET Framework
language pack.   

Step 4: Verify that the package is ready to be deployed

1. Visual Studio 2008 - English Properties dialog box, select the Deployment tab.

2. Under Deployment type choose Assigned.

3. Under Deployment options, select the correct options for when and how to deploy Visual Studio.

4. Select the Modifications tab, and then click Add.

5. Select the transform file you created earlier, such as myVSTransform.mst, and then click Open to add the
file.

6. Browse the other available tabs and make choices as necessary.

Step 5: Set elevated privileges via Group Policy

Refer to Section 6.1 Step 3 for detail.

Step 6: Verifying that the recently created Active Directory package can be installed

1. Restart one of the client computers where Visual Studio 2008 was deployed.
2. Log on to the restarted computer and verify that Visual Studio 2008 has been installed. 
Note: Do not choose Cancel on the Windows Installer dialog box that appears when the product starts.

Back to the top

6.3 Using group policy object to create deployment

An administrative installation point for Visual Studio 2008 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 /acommand line option. The following table
lists all of the command line options for setup:

Table 3. A list of Visual Studio setup command line options.

Command line option Description

Msiexec Executable file name for Windows Installer.

/p Enables Windows Installer to apply an update to an existing installation.

[path\name of update Path and file name of the MSP file for the update.
MSP file]

/a 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.

/qb Sets the user interface to the basic level (simple progress and error handling).

/L*v 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 Path and name of the target folder where admin image will live.
folder]

Use the following syntax for all setup commands:

msiexec /p [path\name of update MSP file] /a [path\name of MSI file] /qb

/L*v [path\name of log file] TRANSFORMS=VS2008Transform.mst PIDKEY=<25 character
product key with no spaces or dashes> TARGETDIR=[path\name of target folder]

To create the administrative installation point

1. From the Start menu, choose Run.

2. Type the following:

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 forPIDKEY.

To locate the product key

1. At the root of the Visual Studio 2008 DVD-ROM, open the file Setup\setup.sdb using a text editor
such as Notepad.
2. The product key is located below [Product Key].