Microsoft KB Archive/327792

= How to deploy Visual Studio .NET 2003 by using Systems Management Server =

Article ID: 327792

Article Last Modified on 3/14/2007

-

APPLIES TO


 * Microsoft Visual Studio .NET 2003 Professional Edition
 * Microsoft Visual Studio .NET 2003 Enterprise Architect
 * Microsoft Visual Studio .NET 2003 Enterprise Developer
 * Microsoft Visual Studio .NET 2003 Academic Edition

-



This article was previously published under Q327792







For a Microsoft Visual Studio 2005 version of this article, see 907759.



For a Microsoft Visual Studio .NET 2002 version of this article, see 309657.



INTRODUCTION
This step-by-step article describes how to use Microsoft Systems Management Server (SMS) to deploy Visual Studio .NET 2003 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 that you are deploying to meet the minimum requirements for Visual Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

822354 Visual Studio .NET 2003 Readme (Part 1)

Create a network image
Administrator setup is designed to run from a network share instead of from a CD-ROM. The steps in this section describe how to copy the Visual Studio .NET 2003 CD-ROMs or DVD-ROM to a network share. If you copy to the server computer running SMS, the files are available when you author your package. If you copy to a different server, you must share the top-level folder that SMS can copy from during package definition.

Share the installation files from the Visual Studio .NET 2003 CD-ROMs
 Create a top-level folder named VS72003 . Create a subfolder named WCU in the top-level folder. Copy the contents of the Visual Studio .NET Prerequisites CD-ROM to the WCU folder. Create a subfolder named VS in the top-level folder. Copy the contents of the remaining Visual Studio .NET 2003 CD-ROMs to the VS folder. Overwrite any existing files.

Note Optionally, you can copy the contents of other CD-ROMs (such as Microsoft Visual SourceSafe, Microsoft Visio, or other products) to different folders for setup over a network.</li> Open the folder that contains the files that you copied, and then open the VS\Setup folder.</li> In a text editor such as Notepad, open the Setup.sdb file.</li> At the end of the file, add the following text:

[Product Key]

where  is the Product Key that is listed on the CD-ROM packaging.</li> Save the changes, and then close the file.</li></ol>

Share the installation files from the DVD-ROM
<ol> Create a top-level folder named VS7 .</li> Copy the contents of the DVD-ROM to the VS7 folder.

Note Optionally, you can copy the contents of other DVD-ROMs (such as Microsoft Visual SourceSafe, Microsoft Visio, or other products) for setup over a network.</li> Open the folder that contains the files that you copied, and then open the Setup folder.</li> In a text editor such as Notepad, open the Setup.sdb file.</li> At the end of the file, add the following text:

[Product Key]

where  is the Product Key that is listed on the DVD-ROM packaging.</li> Save the changes, and then close the file.</li></ol>

System requirements for deployment
Before you can install Visual Studio .NET 2003 on an SMS client computer, the client computer must have all the system components that Visual Studio .NET 2003 requires. The network administrator must verify that all client computers have the required system components.

Note Microsoft recommends that you deploy the components in the order that they are listed. For example, because the Microsoft .NET Framework requires that you install Microsoft Windows Installer 2.0 first, Windows Installer 2.0 is listed before the .NET Framework.

Note If you plan to develop Microsoft ASP.NET Web applications or Web services, install Microsoft Internet Information Services before you install other components.

System requirements for Windows Server 2003

 * Microsoft Windows Server 2003
 * Microsoft FrontPage 2000 Web Extensions Client
 * Setup Runtime Files
 * Microsoft Visual J# .NET Redistributable Package 1.1

System requirements for Windows 2000

 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows Installer 2.0
 * Microsoft FrontPage 2000 Web Extensions Client
 * Setup Runtime Files
 * Microsoft Internet Explorer 6 Service Pack 1
 * Microsoft Data Access Components 2.7 Service Pack 1
 * Microsoft .NET Framework 1.1
 * Microsoft Visual J# .NET Redistributable Package 1.1

System requirements for Windows XP

 * Microsoft Windows XP
 * Microsoft FrontPage 2000 Web Extensions Client
 * Setup Runtime Files - Microsoft Internet Explorer 6 Service Pack 1
 * Microsoft .NET Framework 1.1
 * Microsoft Visual J# .NET Redistributable Package 1.1

Deploy the required components
Each system component that Visual Studio .NET 2003 requires is located on the Visual Studio .NET Prerequisites CD-ROM or in the WCU folder of the Visual Studio .NET DVD-ROM. The following is a list of some of the folder locations for these components:
 * The Internet Explorer 6 SP1 package is located in the IE60SP1 folder.
 * The Windows Installer 2.0 package is located in the WindowsInstaller\2.0 folder.
 * The Microsoft .NET Framework package is located in the dotNetFramework folder.

Note For Visual Studio .NET 2003 to run correctly, 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
In this section, you create the component package. <ol> Click Start, point to Programs, and then click Systems Management Server to open the SMS Administrator console.</li> In the Site Database tree, right-click Packages, point to New, and then click Package.</li> On the General tab of the Package Properties dialog box, add the following values:

Name:

Version:

Publisher: Microsoft

Language:

</li> 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.</li> Click Set.</li> In the Set Source Directory dialog box, click Local drive on site server, and then click Browse.</li> <li>In the Browse for Folder dialog box, select the folder for the component that you are installing based on the following list: </li> <li>Click OK three times to close the dialog boxes.</li></ol>

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 that runs on each destination computer to control how the package runs. <ol> <li>Under Packages in the Site Database tree of the SMS Administrator console, expand the appropriate node.</li> <li>Right-click Programs, point to New, and then click Program.</li> <li>On the General tab of the Program Properties dialog box, type  Program in the Name text box, and then add the appropriate value in the Command Line box based on the following list: </li> <li>In the After running list box, select the appropriate value based on the following list: </li> <li>On the Environment tab, click Run with administrative rights. If you are running SMS 2003, click to clear the Allow users to interact with this program check box. If you are running SMS 2.0, click to clear the User input required check box.</li> <li>Click OK to close the Program Properties dialog box.</li></ol>

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 gain access to 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 that you want to copy the package to.
 * 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   Advertisement in the Name text 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 that you want to deploy to.
 * 6) Click OK to close the Advertisement Properties dialog box.

Before you deploy the program
To deploy Visual Studio .NET 2003, you must create the unattend file for the Visual Studio .NET 2003 installation, and then download SMSWrapperPackage.exe: <ol> <li>Run the following command at a command prompt to create the unattend file for the Visual Studio .NET 2003 installation:

c:\vs72003\vs\setup\setup.exe /createunattend c:\vs.ini /no_bsln_check

For more information about how to run setup with the /createunattend switch, see the Adminreadme.htm file that is located in the Setup folder.</li> <li>Share the Vs.ini file. You must point to this file when you run setup on the client computers. In this example, the file is shared at \\SMSServer\Ini\Vs.ini.</li> <li>Download the SMSWrapperPackage.exe file, and then save SMSWrapperPackage.exe to the same location that you copied the Visual Studio CD-ROMs to (the examples in this article use C:\VS72003\VS). The following file is available for download from the Microsoft Download Center:

Download the SMSWrapperPackage.exe package now.

Release Date: March 21, 2002

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.</li></ol>

Step 1: Create the Visual Studio .NET 2003 package
<ol> <li>In the Site Database tree of the SMS Administrator console, right-click Packages, point to New, and then click Package.</li> <li>On the General tab of the Package Properties dialog box, add the following values:

Name: Visual Studio .NET 2003

Version: 7.1

Publisher: Microsoft

Language:

</li> <li>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.</li> <li>Click Set.</li> <li>In the Set Source Directory dialog box, click Local drive on site server, and then click Browse.</li> <li>In the Browse for Folder dialog box, select the C:\VS72003\VS folder. This is the folder where you extracted the files to earlier.</li> <li>Click OK three times to close the dialog boxes.</li></ol>

Step 2: Create the Visual Studio .NET 2003 program
<ol> <li>Under Packages in the Site Database tree of the SMS Administrator console, expand the appropriate node.</li> <li>Right-click Programs, point to New, and then click Program.</li> <li>On the General tab of the Program Properties dialog box, type Visual Studio .NET Program in the Name text box, and then type the following text in the Command Line text box:

smswrapper.exe setup\setup.exe /unattendfile \\smsserver\ini\vs.ini /no_bsln_check

</li> <li>On the Environment tab, click Run with administrative rights. If you are running SMS 2003, click to clear the Allow users to interact with this program check box. If you are running SMS 2.0, click to clear the User input required check box.</li> <li>Click OK to close the Program Properties dialog box.</li></ol>

Step 3: Create the Visual Studio .NET 2003 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 that you want to copy the package to.
 * 4) Click Finish.

Step 4: Create the Visual Studio .NET 2003 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 .NET 2003 Advertisement in the Name text box.
 * 3) In the Package list, select the Visual Studio .NET 2003 package.
 * 4) In the Program list, select the Visual Studio .NET 2003 program.
 * 5) Click Browse, and then select the collection of computers that you want to deploy to.
 * 6) Click OK to close the Advertisement Properties dialog box.

Known Issues
The SMSWrapper.exe will pass the appropriate parameters to the Setup.exe. The SMSWrapper.exe keeps SMS aware that the installation process is active until it has been completed. SMSWrapper.exe will not return the expected non-zero value to SMS. In every case SMSWrapper.exe will report failure to SMS even when the installation is successful.

<div class="references_section">