Microsoft KB Archive/309657

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

Article ID: 309657

Article Last Modified on 3/14/2007

-

APPLIES TO


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

-



This article was previously published under Q309657





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



For a Microsoft Visual Studio .NET 2003 version of this article, see 327792.



INTRODUCTION
This step-by-step article describes how to use Microsoft Systems Management Server (SMS) to deploy Visual Studio .NET and its system dependencies across a network. Systems Management Server allows you to deploy software that has administrative privileges 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:

312779 Visual Studio .NET Readme (Part 1)

Create a network image
Administrator setup is designed to run from a network share rather than from a CD. The steps in this section demonstrate how to copy the Visual Studio .NET CDs to a network share.

If you copy to the SMS server, the files are available when you author your package. If you copy to a different server, you need to share the top-level folder that SMS can copy from during package definition.

Share the installation files from the Visual Studio .NET CDs
 Create a top-level folder named VS7. Create a subfolder named WCU within the top-level folder. Copy the contents of the Visual Studio .NET Windows Component Update CD to the WCU folder. Create a subfolder named VS within the top-level folder. Copy the contents of the remaining Visual Studio .NET CDs to the VS folder. Choose to overwrite existing files.

Note Optionally, you can copy the contents of other CDs (such as Microsoft Visual SourceSafe, Microsoft Visio, or other products) to different folders for setup over a network. 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 packaging.</li> Save the changes, and then close the file.</li></ol>

Share the installation files from the DVD
<ol> Copy the contents of the DVD into a top-level folder named VS7.

Note Optionally, you can copy the contents of other DVDs (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 packaging.</li> Save the changes, and then close the file.</li></ol>

System requirements for deployment
Before you can install Visual Studio .NET on an SMS client computer, the client computer must have all the system components that Visual Studio .NET requires. The network administrator must ensure 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, you should also install Microsoft Internet Information Services before you install other components.

System requirements for Windows NT 4.0

 * Microsoft Windows NT 4.0 Service Pack 6.0a
 * Microsoft FrontPage 2000 Server Extensions Service Release 1.2
 * Microsoft Windows Installer 2.0
 * Microsoft Windows Management Instrumentation
 * Microsoft FrontPage 2000 Web Extensions Client
 * Setup Runtime Files
 * Microsoft Internet Explorer 6
 * Microsoft Data Access Components 2.7
 * Microsoft Jet 4.0 Service Pack 3
 * Microsoft .NET Framework

System requirements for Windows 2000

 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows Installer 2.0
 * Microsoft FrontPage 2000 Web Extensions Client
 * Setup Runtime Files
 * Microsoft Internet Explorer 6
 * Microsoft Data Access Components 2.7
 * Microsoft .NET Framework

System requirements for Windows XP

 * Microsoft Windows XP
 * Microsoft FrontPage 2000 Web Extensions Client
 * Setup Runtime Files
 * Microsoft .NET Framework

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

Deploy the required components
Each system component that Visual Studio .NET requires is located on the Windows Component Update CD or in the WCU folder of the Visual Studio .NET DVD. The following list outlines some of the folder locations for these components:
 * The Internet Explorer 6 package is located in the IE60 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 to function, you must deploy the version of the .NET Framework from the dotNetFramework folder.

For more information about how to deploy Windows Installer 2.0, refer to the following Microsoft Web site:

Deploying Windows Installer Setup Packages with Systems Management Server 2.0

http://www.microsoft.com/technet/prodtechnol/sms/sms2/depovg/deplymsi.mspx

For more information about how to install the Microsoft .NET Framework, refer to the following Microsoft Web site:

Redistributing the .NET Framework

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> On the Start menu, 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, select the This package contains source files check box, 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> In the Browse for Folder dialog box, select the directory for the component that you are installing based on the following list: <ul> <li>Component: Windows NT 4.0 Service Pack 6a

Directory: .\NTSP6a\</li> <li>Component: Windows 2000 Service Pack 2

Directory: .\Win2kSP2\</li> <li>Component: FrontPage 2000 Server Extensions Service Release 1.2

Directory: .\FrontPageServer\</li> <li>Component: Windows Installer Management Instrumentation

Directory: .\WMI\</li> <li>Component: FrontPage 2000 Web Extensions Client

Directory: .\</li> <li>Component: Setup Runtime Files

Directory: .\</li> <li>Component: Microsoft Data Access Components 2.7

Directory: .\MDAC27\</li> <li>Component: Jet 4.0 Service Pack 3

Directory: .\Jet\</li></ul> </li> <li>Click OK three times to close each dialog box.</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 targeted computer to control the execution of the package.
 * 1) In the Site Database tree, under the Packages node, click to 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   Program in the Name text box, and then add the appropriate value for the Command Line text box based on the following list:
 * 4) * Component: Windows NT 4.0 Service Pack 6a

Command Line Value: sp6i386.exe -q -n
 * 1) * Component: Windows 2000 Service Pack 2

Command Line Value: w2ksp2.exe -q -n
 * 1) * Component: Windows Installer 2.0 [Windows NT]

Command Line Value: instmsiw.exe /q
 * 1) * Component: FrontPage 2000 Server Extensions Service Release 1.2

Command Line Value: fpse2k.exe /c:fpseq.inf
 * 1) * Component: Windows Installer Management Instrumentation

Command Line Value: wmicore.exe /s
 * 1) * Component: FrontPage 2000 Web Extensions Client

Command Line Value: msiexec /i weccom.msi /q
 * 1) * Component: Setup Runtime Files

Command Line Value: msiexec /i bootstrap.msi /q
 * 1) * Component: Microsoft Data Access Components 2.7

Command Line Value: mdac_typ.exe /q:a /c:&quot;dasetup.exe /q&quot;
 * 1) * Component: Jet 4.0 Service Pack 3

Command Line Value: jetsetup.exe /q:a
 * 1) In the After running list, select the appropriate value based on the following list:
 * 2) * Component: Windows NT 4.0 Service Pack 6a

After running value: Program restarts computer
 * 1) * Component: Windows 2000 Service Pack 2

After running value: Program restarts computer
 * 1) * Component: FrontPage 2000 Server Extensions Service Release 1.2

After running value: SMS restarts computer
 * 1) * Component: Windows Installer Management Instrumentation

After running value: Program restarts computer
 * 1) * Component: FrontPage 2000 Web Extensions Client

After running value: No action required
 * 1) * Component: Setup Runtime Files

After running value: No action required
 * 1) * Component: Microsoft Data Access Components 2.7

After running value: No action required
 * 1) * Component: Jet 4.0 Service Pack 3

After running value: No action required
 * 1) On the Environment tab, clear the User input required check box, and then click Run with administrative rights.
 * 2) 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 where package source files are copied so that client computers can access the source files.
 * 1) In the Site Database tree, right-click Distribution Points under the appropriate node, 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 will be scheduled for installation.
 * 1) In the Site Database tree, right-click the Advertisements node, 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.

Deploy Visual Studio .NET
To deploy Visual Studio .NET, you must follow these initial steps: <ol> <li>Run the following command at a command prompt to create the unattend file for the Visual Studio .NET installation:

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

For more information about how to run setup with the /createunattend switch, refer to the Adminreadme.htm file that is located in the Setup folder.</li> <li>Share the Vs.ini file. You need to 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 CDs to (for example, C:\VS7\VS in the preceding steps).

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 package
<ol> <li>In the Site Database tree, right-click the Packages node, 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

Version: 7.0

Publisher: Microsoft

Language:

</li> <li>On the Data Source tab, select the This package contains source files check box, 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:\VS7\VS directory (which is where you extracted the files to earlier).</li> <li>Click OK three times to close each dialog box.</li></ol>

Step 2: Create the Visual Studio .NET program
<ol> <li>In the Site Database tree, under the Packages node, click to 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, clear the User input required check box, and then click Run with administrative rights.</li> <li>Click OK to close the Program Properties dialog box.</li></ol>

Step 3: Create the Visual Studio .NET distribution point

 * 1) In the Site Database tree, right-click Distribution Points under the appropriate node, 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 advertisement

 * 1) In the Site Database tree, right-click the Advertisements node, point to New, and then click Advertisement.
 * 2) On the General tab of the Advertisement Properties dialog box, type Visual Studio .NET Advertisement in the Name text box.
 * 3) In the Package list, select the Visual Studio .NET package.
 * 4) In the Program list, select the Visual Studio .NET 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 expectd 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">