INF: SQL 7.0 Remote Unattended Install

ID: Q231735


The information in this article applies to:
  • Microsoft SQL Server version 7.0


SUMMARY

Some companies may have the need to do an unattended remote setup of SQL Server 7.0. This document explains how you can accomplish this task.

NOTE: Remote Unattended Install is not built into SQL Server 7.0. This Knowledge Base article documents operator initiated steps that may sufficiently provide Remote Unattended Install for a customer. Any product related issues resulting from these steps are not supported.


MORE INFORMATION

What is Needed

Initially, perform a complete remote install, choosing the exact components the future install will require.

NOTE: Remember to choose LocalSystem for the Service Accounts

  • Copy of setup directory (located in x86/setup folder of the CD).


  • Setup.iss (calls the procedures on the install).


    • Where to get Setup.iss: Comes from the initial remote install of SQL Server (located in Admin$ or <WINNT> on the local computer).


  • Remsetup.ini (pointer document that gives information to the Remsetup.exe about the iss file, sqlsetup file, and so forth).


    • Where to get Remsetup.ini: Initially comes from a full remote setup of SQL Server (located in Admin$ or <WINNT> on the local computer).


  • Remsetup.exe, scm.exe, cnvsvc.exe, cnvrem.dll.


    • Where to get these files: Run the remote setup until the first dialog box appears in the setup. Go to the %temp%\_istmpxx.dir directory to retrieve the four files.


Steps to Execute the Remote Unattended Install

  1. Place the Remsetup.exe, scm.exe, cnvsvc.exe, cnvrem.dll and Remsetup.ini into a folder on one of your local drives.


  2. Modify the Remserver.ini file so that the password is anything except a blank. Example: Make the password "fake" or "bogus" (without the quotation marks). Also, change any necessary path statements (see below for copy of sample Remsetup.ini file).


  3. Use the following calls from the command line:

    • Scm.exe -Action 5 -Silent 1 -Server "remotemachinename" -Service "SQL Server 7.0 Setup" -ExePath "C:\yourpath\cnvsvc.exe" -SvcAccount "DOMAIN\user" -SvcPwd "plain-text password"

      NOTE: Wait a minute to run the second command.


    • Remsetup.exe remsetup.ini.




Things to Look for/Caveats

After the first command line call wait for a minute or so to run the second command line. This is to allow the service to be properly installed on the remote computer.

The "SvcAccount" in the first command line call should be an account with Administrator permissions on both computers (and the same password on both computers). You need to have the right to "log on as a service" and so forth.

You also need to configure the server (for the first time) with LocalSystem Accounts for the services. This can be accomplished on the first run through to obtain the .iss and .ini files.

To obtain the .iss and .ini files by running the install, select the exact parameters/components you plan on installing during the unattended install. Diversion from this step results in an error in setup because of a dialog mismatch.

For desktop installs modify the cmdlineformat to include the statement k=Dk to this line.

Other information

Information Included in the Remsetup.ini File

The current .ini file looks like the following:

[args]
app=\\A419610\D$\7x0082\x86\SetupStd\setupsql.exe
server=testserver
script=\\A419610\admin$\setup.iss
cmdlineformat=%s k=Rm -s -f1 %s
user=DOMAIN\user
password=1048df52fb81524bb60257  
********MODIFY TO****** 
password=bogus 
In this example the following are defined:
  • App - This is the path to the setupsql executable.


  • Server - The name of the server.


  • Script - The path to the script file, setup.iss.


  • Cmdlineformat - This is the command line for installations.


  • User - This is the user name to log onto the remote computer.


  • Password - This is the encrypted password for the remote computer.


Additional query words:

Keywords : SSrvInst kbSQLServ700
Version : winnt:7.0
Platform : winnt
Issue type : kbinfo


Last Reviewed: July 13, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.