How to deploy Visual Studio 2005 by using Systems Management Server

Article translations Article translations
Article ID: 907759 - View products that this article applies to.
For a Microsoft Visual Studio .NET 2003 version of this article, see 327792.
For a Microsoft Visual Studio .NET 2002 version of this article, see 309657.

Expand all | Collapse all

On This Page

INTRODUCTION

This step-by-step article describes how to use Microsoft Systems Management Server (SMS) to deploy Visual Studio 2005 and its system dependencies across a network. You can use SMS to deploy programs that have administrative rights across a network.

This article assumes that all client computers to which you are deploying Visual Studio 2005 meet the minimum requirements for Visual Studio 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
908452 Contents of Microsoft Visual Studio 2005 Setup Issues Readme file

MORE INFORMATION

Create a network image

You can run the Visual Studio 2005 Setup program from a network share instead from CDs or DVDs. The following procedure shows how to prepare Visual Studio 2005 for installation from a network share.

Note Visual SourceSafe is not installed when you run the Visual Studio 2005 Setup program. However, you can copy the contents of the Visual SourceSafe installation media to a separate folder on the server to deploy these products over a network as separate installations.

Share the Visual Studio 2005 installation files

  1. Create a folder on the server. For example, create a folder that is named VisualStudio2005.
  2. In the VisualStudio2005 folder, create two folders. Name these folders VisualStudio and MSDN. The path names of these folders appear as follows:
    • VisualStudio2005\VisualStudio
    • VisualStudio2005\MSDN
    Note These path name examples are used throughout this article.
  3. Copy the contents of all the CDs that are labeled Visual Studio 2005 to the VisualStudio2005\VisualStudio folder. If prompted, overwrite existing files.
  4. Copy the contents of all the CDs that are labeled MSDN Library for Visual Studio 2005 to the VisualStudio2005\MSDN folder. If prompted, overwrite existing files.
  5. In a text editor such as Notepad, open the Setup.ini file. The Setup.ini file is located in the VisualStudio2005\VisualStudio folder.
  6. In the [Documentation] section, locate the following line.
    [Documentation]
    DIR=
  7. Change the line that you located in step 6 to the following.
    [Documentation]
    DIR=..\MSDN
  8. Save and then close the file.

    Note This change prevents disk-swapping requests during the Setup process. This change also provides the correct path of the MSDN Library CD to the Setup program.
  9. Open the Setup folder. This folder is located in the VisualStudio2005\VisualStudio folder.
  10. In a text editor such as Notepad, open the Setup.sdb file. Add the following lines to the end of the file.
    [Product Key]
    XXXXXXXXXXXXXXXXXXXXXXXXX 
    
    Note XXXXXXXXXXXXXXXXXXXXXXXXX is the 25 character product key that is located on the CD packaging. Do not enter the dashes (-) that appear in the product key.
  11. Save and then close the file.

    Note This change pre-populates the product key box during the Setup process.
  12. Share the VisualStudio2005 folder on the network. Set the appropriate security settings on the shared VisualStudio2005 folder. The path of the Visual Studio 2005 Setup.exe file on the network looks like the following:
    \\ServerName\VisualStudio2005\VisualStudio\Setup.exe
    Note During the installation process, the Setup process will fail if any combination of a path and a file name exceeds 260 characters. In Visual Studio, the maximum length of a path is 221 characters. Therefore, we recommend that you copy the installation files to a path that has less than 70 characters. If you create a network share for a network image, we recommend that the UNC path of the root installation location contain less than 39 characters.

    Note The Setup process may also fail if the folder names in the installation paths include spaces. For example, the Setup process may fail if you use the following installation paths:
    \\ServerName\VisualStudio 2005\MSDN
    \\ServerName\VisualStudio2005\Visual Studio

System requirements for deployment

Before you can install Visual Studio 2005 on an SMS client computer, the client computer must have all the system components that Visual Studio 2005 requires. The network administrator must verify that all client computers have the required system components.

Note We recommend that you deploy the components in the order that they appear in this list. For example, Microsoft Windows Installer 3.1 appears before the Microsoft .NET Framework because you cannot install the .NET Framework unless you have already installed Windows Installer 3.1.

Note If you plan to develop Web applications or Web services by using Microsoft ASP.NET, install Microsoft Internet Information Services (IIS) before you install the other components.

System requirements for Windows Server 2003

  • Microsoft Windows Server 2003 Service Pack 1 (SP1)
  • Microsoft .NET Framework 2.0
  • Microsoft Visual Studio Tools for Office Redistributable Package
    (This package is only required for the Microsoft Visual Studio Tools for Office product.)
  • Microsoft MSXML 6.0
  • Microsoft Visual Studio 2005 64-bit prerequisites
    (These prerequisites are only required for 64-bit computers.)
  • Microsoft Visual J# Redistributable Package 2.0
  • Microsoft Document Explorer 2005
  • Microsoft Visual Studio 64-bit software development kits (SDKs)
    (These SDKs are required to debug 64-bit applications.)

System requirements for Windows 2000

  • Microsoft Windows 2000 Service Pack 4 (SP4)
  • Microsoft Internet Explorer 6 SP1
  • Microsoft Windows Installer 3.1
  • Microsoft Data Access Components 2.8 SP1
  • Microsoft .NET Framework 2.0
  • Microsoft Visual Studio Tools for Office Redistributable Package
    (This package is only required for the Microsoft Visual Studio Tools for Office product.)
  • Microsoft MSXML 6.0
  • Microsoft Visual Studio 2005 64-bit prerequisites
    (These prerequisites are only required for 64-bit computers.)
  • Microsoft Visual J# .NET Redistributable Package 2.0
  • Microsoft Document Explorer 2005
  • Microsoft Visual Studio 64-bit SDKs
    (These SDKs are required to debug 64-bit applications.)

System requirements for Windows XP

  • Microsoft Windows XP Service Pack 2 (SP2)
  • Microsoft Internet Explorer 6 SP1
  • Microsoft .NET Framework 2.0
  • Microsoft Visual Studio Tools for Office Redistributable Package
    (This package is only required for the Microsoft Visual Studio Tools for Office product.)
  • Microsoft MSXML 6.0
  • Microsoft Visual Studio 2005 64-bit prerequisites
    (These prerequisites are only required for 64-bit computers.)
  • Microsoft Visual J# .NET Redistributable Package 2.0
  • Microsoft Document Explorer 2005
  • Microsoft Visual Studio 64-bit SDKs
    (These SDKs are required to debug 64-bit applications.)

Deploy the required components

Each system component that Visual Studio 2005 requires is located in the WCU folder of the Visual Studio CD-ROM or DVD-ROM. The following is a list of some folder locations for these components:
  • The Microsoft Document Explorer 2005 package is located in the DExplore folder.
  • The Microsoft MSXML 6.0 package is located in the MSXML folder.
  • The Microsoft .NET Framework package is located in the dotNetFramework folder.
Note For Visual Studio 2005 to correctly run, you must deploy the version of the .NET Framework that is located in the dotNetFramework folder.

For more information about how to deploy Windows Installer Setup packages by using Systems Management Server 2.0, visit the following Microsoft Web site:
http://www.microsoft.com/smserver/techinfo/deployment/20/deployosapps/deploymsi.mspx
For more information about how to install the Microsoft .NET Framework, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms994395.aspx
To deploy the remaining components, you must follow these steps:
  1. Create the component package.
  2. Create the component program.
  3. Create the component distribution point.
  4. Create the component advertisement.

Step 1: Create the component package

  1. Click Start, point to Programs, and then click Systems Management Server to open the SMS Administrator console.
  2. In the Site Database tree, right-click Packages, point to New, and then click Package.
  3. On the General tab of the Package Properties dialog box, add the following values to the appropriate fields.
    Collapse this tableExpand this table
    FieldValue
    NameComponent Name
    VersionComponent Version
    PublisherMicrosoft
    LanguageComponent Language
  4. On the Data Source tab, click to select the check box for This package contains source files, and then click Always obtain files from source directory.
  5. Click Set.
  6. In the Set Source Directory dialog box, click Local drive on site server, and then click Browse.
  7. In the Browse for Folder dialog box, select the folder for the component that you are installing based on the following list.
    Collapse this tableExpand this table
    ComponentFolder
    Microsoft Windows Installer 3.1.\msi31
    Microsoft Data Access Components 2.8 SP1.\MDAC28
    Microsoft .NET Framework 2.0.\dotNetFramework
    Microsoft Visual Studio Tools for Office Redistributable Package.\VS Tools for Office
    Microsoft MSXML6.0.\msxml
    Microsoft Visual Studio 2005 64-bit prerequisites.\64bitPrereq\x64
    Microsoft Visual J# .NET Redistributable Package 2.0.\JSharpRedistCore
    Microsoft Document Explorer.\DExplore
    Microsoft Visual Studio 64-bit SDKs.\SDK\x64 8
  8. Click OK three times to close the dialog boxes.

Step 2: Create the component program

In this section, you create a program for the package. Each SMS package contains at least one SMS program. The SMS program is a command-line program that runs on each destination computer to control how the package runs.
  1. Under Packages in the Site Database tree of the SMS Administrator console, expand the appropriate node.
  2. Right-click Programs, point to New, and then click Program.
  3. On the General tab of the Program Properties dialog box, type Component Name Program in the Name box. Then, type the appropriate value in the Command Line box based on the following list.
    Collapse this tableExpand this table
    ComponentCommand Line value
    Microsoft Windows Installer 3.1WindowsInstaller-KB893803-v2-x86.exe /quiet
    Microsoft Data Access Components 2.8 SP1mdac_typ.exe /Q /C:"dasetup /Q /N"
    Microsoft .NET Framework 2.0dotnetfx.exe /q:a /c:"install /q"
    Microsoft Visual Studio Tools for Office Redistributable Packagevstor.exe /q:a /c:"install /q"
    Microsoft MSXML 6.0msxml6.msi /qb
    Microsoft Visual Studio 2005 64-bit prerequisitesvs_bsln.exe /Q
    Microsoft Visual J# .NET Redistributable Package 2.0vjredist.exe /q:a /c:"install /q"
    Microsoft Document ExplorerDExplore.exe /q:a /c:"install /q"
    Microsoft Visual Studio 64-bit SDKssetup.exe /q:a /c:"install /q"
  4. In the After running list, select the appropriate value that is based on the following list.
    Collapse this tableExpand this table
    ComponentAfter running value
    Microsoft Windows Installer 3.1No action required
    Microsoft Data Access Components 2.8 SP1No action required
    Microsoft .NET Framework 2.0No action required
    Microsoft Visual Studio Tools for Office Redistributable PackageNo action required
    Microsoft MSXML6.0No action required
    Microsoft Visual Studio 2005 64-bit prerequisitesNo action required
    Microsoft Visual J# .NET Redistributable Package 2.0No action required
    Microsoft Document ExplorerNo action required
    Microsoft Visual Studio 64-bit SDKsNo action required
  5. On the Environment tab, click to clear the check box for User input required, and then click Run with administrative rights.
  6. Click OK to close the Program Properties dialog box.

Step 3: Create the component distribution point

In this section, you create a distribution point for the package. SMS distribution points are shares on site systems. You copy the package source files to an SMS distribution point so that client computers can access the source files.
  1. Under the appropriate node in the Site Database tree of the SMS Administrator console, right-click Distribution Points, point to New, and then click Distribution Points.
  2. In the New Distribution Points Wizard, click Next.
  3. Select the distribution point to which you want to copy the package.
  4. Click Finish.

Step 4: Create the component advertisement

In this section, you create an advertisement for the program. An advertisement specifies what program is available to the client computers, which computers receive the advertisement, and when the program is scheduled for installation.
  1. In the Site Database tree of the SMS Administrator console, right-click Advertisements, point to New, and then click Advertisement.
  2. On the General tab of the Advertisement Properties dialog box, type Component Name Advertisement in the Name box.
  3. In the Package list, select the appropriate component.
  4. In the Program list, select the appropriate component program.
  5. Click Browse, and then select the collection of computers to which you want to deploy the program.
  6. Click OK to close the Advertisement Properties dialog box.

Deploy Visual Studio 2005

Before you deploy the program

program To deploy Visual Studio 2005, you must create the unattend file for the Visual Studio 2005 installation. To do this, follow these steps:
  1. To create the unattend file for the Visual Studio 2005 installation, run the following command at a command prompt:
    c:\vs8\vs\setup\setup.exe /createunattend c:\vs.ini
    For more information about how to run the Setup program by using the /createunattend switch, see the Adminreadme.htm file that is located in the Setup folder.

    Note You must create a unique .INI unattend file for each target operating system. For example, for a Windows XP Professional installation, you must create an unattend file for Windows XP Professional. A Windows Server 2003 unattend file will not be usable for a Windows XP Professional installation.
  2. Share the Vs.ini file. You must point to this file when you run the Setup program on the client computers. In this example, the file is shared at the following location:
    \\SMSServer\Ini\Vs.ini


    Note The examples in this article use the VisualStudio2005\VisualStudio folder.

Step 1: Create the Visual Studio 2005 package

  1. In the Site Database tree of the SMS Administrator console, right-click Packages, point to New, and then click Package.
  2. On the General tab of the Package Properties dialog box, add the following values.
    Collapse this tableExpand this table
    FieldValue
    NameVisual Studio 2005
    Version8.0
    PublisherMicrosoft
    LanguageProduct Language
  3. On the Data Source tab, click to select the check box for This package contains source files, and then click Always obtain files from source directory.
  4. Click Set.
  5. In the Set Source Directory dialog box, click Local drive on site server, and then click Browse.
  6. In the Browse for Folder dialog box, select the VisualStudio2005\VisualStudio folder. This is the folder to which you extracted the files earlier.
  7. Click OK three times to close the dialog boxes.

Step 2: Create the Visual Studio 2005 program

  1. Under Packages in the Site Database tree of the SMS Administrator console, expand the appropriate node.
  2. Right-click Programs, point to New, and then click Program.
  3. On the General tab of the Program Properties dialog box, type Visual Studio Program in the Name box.
  4. Type the following in the Command Line box:
    smswrapper.exe setup\setup.exe /unattendfile \\smsserver\ini\vs.ini /no_bsln_check
  5. On the Environment tab, click to clear the check box for User input required, and then click Run with administrative rights.
  6. Click OK to close the Program Properties dialog box.

Step 3: Create the Visual Studio 2005 distribution point

  1. Under the appropriate node in the Site Database tree of the SMS Administrator console, right-click Distribution Points, point to New, and then click Distribution Points.
  2. In the New Distribution Points Wizard, click Next.
  3. Select the distribution point to which you want to copy the package.
  4. Click Finish.

Step 4: Create the Visual Studio 2005 advertisement

  1. In the Site Database tree of the SMS Administrator console, right-click Advertisements, point to New, and then click Advertisement.
  2. On the General tab of the Advertisement Properties dialog box, type Visual Studio 2005 Advertisement in the Name box.
  3. In the Package list, select the Visual Studio 2005 package.
  4. In the Program list, select the Visual Studio 2005 program.
  5. Click Browse, and then select the collection of computers to which you want to deploy Visual Studio 2005.
  6. Click OK to close the Advertisement Properties dialog box.

REFERENCES

For more information about Systems Management Server, visit the following Microsoft Web site:
http://www.microsoft.com/smserver/default.mspx
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913445 The computer may restart unexpectedly when you install Visual Studio 2005 in unattended mode

Properties

Article ID: 907759 - Last Review: March 14, 2007 - Revision: 2.5
APPLIES TO
  • Microsoft Visual Studio 2005 Professional Edition
  • Microsoft Visual Studio 2005 Express Edition
Keywords: 
kbhowtomaster kbinfo KB907759

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com