Setup Administrator Mode Readme

1. Introduction

Microsoft Visual Studio .NET 2003 Prerequisites Setup offers an administrator mode, which allows deployment to field clients. This mode allows you to initially run setup to select the components that will be deployed. An .INI file is created based on this selection, and this file can then be deployed by running setup in unattend mode, pointing to the generated .INI file. When in unattend mode, setup runs silently, installing the designated options. If there are any errors, setup exits silently with failures. This mode allows deployment through Microsoft Systems Management Server.

For information on deploying Visual Studio .NET using SMS, see http://support.microsoft.com/?scid=kb;en-us;Q327792.

2. Running Administrator Mode Setup

Before running this phase of administrator setup, you must first run Visual Studio .NET 2003 Prerequisites Setup on your machine.  Some of the components installed by the update are required for Visual Studio .NET setup to function.

Note: You must run the setup.exe found in the \setup subdirectory in order to create an .ini file. The setup.exe file found at the root of the CD or DVD does not support administrator setup.

To create the deployment .INI file from CD
  1. Insert the Visual Studio .NET 2003 Prerequisites CD and ignore the autorun message.
  2. On the Start menu, choose Run.
  3. Type the following:
    n:\Setup.exe /createunattend <path to .INI file>

    For example:
    D:\setup.exe /createunattend c:\bsln_deployment.ini
To create the deployment .INI file from DVD
  1. Insert the Visual Studio .NET 2003 DVD and ignore the autorun message.
  2. On the Start menu, choose Run.
  3. Type the following:
    n:\pre\Setup.exe /createunattend <path to .INI file>

    For example:
    D:\pre\setup.exe /createunattend c:\bsln_deployment.ini
To run setup with the deployment .INI file
  1. Verify that the Visual Studio .NET 2003 Prerequisites CD is available on the network (see "Creating a Network Image" below).
  2. On the Start menu, choose Run.
  3. Type the following:
    \\...\Setup.exe /unattendfile <path to .INI file>

    For example:
    \\computer\share\setup.exe /unattendfile \\computer\share\bsln_deployment.ini

3. Creating a Network Image

Visual Studio .NET 2003 setup may be run from a network share as an alternative to running setup from CDs or DVDs.

The following procedure illustrates how to prepare Visual Studio .NET 2003 for installation from a network share.

Example procedure for sharing installation files from CDs
  1. Create a folder (for example, VS2003) on the server.
  2. Create three subfolders, named PRE, VS, and MSDN within the top-level folder. For example:

    VS2003\PRE
    VS2003\VS
    VS2003\MSDN
  3. Copy the contents of the CD labeled Visual Studio .NET 2003 Prerequisites to the subfolder named PRE.

    Copy the contents of all CDs labeled as Visual Studio .NET 2003 to the subfolder named VS folder. If prompted, overwrite existing files.

    Copy the contents of all CDs labeled MSDN Library for Visual Studio .NET 2003 to the subfolder named MSDN. If prompted, overwrite existing files.
  4. Open setup.ini in the VS subfolder using a text editor, such as Notepad.
  5. In the [Baseline] section, change the line that starts with "DIR=" as follows:
    [Baseline]
    DIR=..\PRE
    FileName=setup.exe
    In the [Documentation] section, change the line that starts with "DIR=" to "DIR=..\MSDN". For example:
    [Documentation]
    DIR=..\MSDN
  6. Save your changes and close the file.

    Note Completing this step prevents disk-swapping requests during setup and informs setup of the correct paths to the Visual Studio .NET 2003 Prerequisites and the MSDN Library CDs.

  7. In the VS subfolder, open the Setup folder.
  8. Open setup.sdb using a text editor, such as Notepad, and add the following lines to the end of the file:
    [Product Key]
    XXXXXXXXXXXXXXXXXXXXXXXXX
    Note XXXXXXXXXXXXXXXXXXXXXXXXX is the 25 digit product key, entered without dashes, found on the CD packaging.
  9. Save your changes and close the file.

    Note Completing this step enables pre-populating the product key for the user.

  10. Share the VS2003 folder on the network and set the appropriate security settings. The path to Visual Studio .NET 2003 setup from the network looks as follows: \\[servername]\VS2003\VS\setup.exe.

    Note When installing, setup fails if any path and file name combination exceeds 260 characters. The maximum length of a path in Visual Studio is 221 characters; accordingly, you should copy files to a path with less than 70 characters. If you create a network share for a network image, the UNC path to the root install location should contain fewer than 39 characters.

    Note Setup may fail if the folder names in this path include embedded spaces, for example “\\[servername]\VS 2003\MSDN\” or “\\[servername]\VS2003\Visual Studio\”.

    Note Visual SourceSafe and Visio are not part of Visual Studio .NET 2003 setup. However, you may also copy the contents of the Visual SourceSafe and Visio CDs to separate folders on your server to facilitate setup of these products over a network as separate installations.

4. Required Prerequisite Components

The following components are required for Visual Studio .NET2003. It is recommended that you choose the default list of components in the administrator mode of setup, because these components are required before you install Visual Studio .NET 2003. You can choose, however, not to include all default components, as you may wish to deploy some components using alternative methods.  When you run setup in createunattend mode, setup displays only the list of components required for the operating system you are currently running.  If you wish to deploy the Visual Studio .NET Prerequisites Setup to multiple operating systems, you must run createunattend for each operating system.

4.1. Components with Language Version Conflicts

Visual Studio .NET 2003 setup requires that certain prerequisites be installed in the same language version as the language version of your operating system. However, Visual Studio .NET 2003 setup might not include the language version that your operating systems require for these components. You can download the correct language version from the Internet and deploy it separately. See local.htm in the same directory as this file for more information.

 5. Deploying VSS and Visio
 5.1.  Visio

To deploy Visio run with the following command -- msiexec /qn

 5.2.  VSS

Details of VSS deployment can be found in the following KB article -- Q195828

6. Known Installation Issues

6.1. Data file cannot be created

If you run setup in createunattend mode using a file that already exists, an error appears stating "The data file <filename> cannot be created. Setup cannot continue." Either delete the existing file, or provide a unique file name.

6.2. Visibility of user-specific data

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.

7. Running Administrator Mode Uninstall

Before running this phase of administrator setup, you must first have Visual Studio .NET installed on your machine. 

Note: You must run the setup.exe found in the \setup subdirectory in order to create an .ini file. The setup.exe file found at the root of the CD or DVD does not support administrator setup.

To create the uninstall .INI file

1.          Insert the Visual Studio .NET 2003 CD 1 or DVD and ignore the autorun message.

2.          Choose the Start menu and then choose Run.

3.          Type the following:

n:\setup\Setup.exe /createunattend <path to .INI file>

For example:

D:\setup\setup.exe /createunattend c:\vs7_uninstall.ini

4.          On the Visual Studio .NET Maintenance screen, select the Uninstall Microsoft Visual Studio .NET link.

5.          Click the Done link after the file is saved successfully.

 

 

To run setup with the generated file on a client

1.          Verify that Visual Studio .NET 2003 is available on the network (see Creating a Network Image).

2.          Choose the Start menu and then choose Run.

3.          Type the following:

\\<computer>\<share>\...\setup\Setup.exe /unattendfile <path to .INI file>

For example:

\\products\VisualStudio\setup\setup.exe /unattendfile \\computer\share\vs7_uninstall.ini