The SMS 2003 Setup program always creates the database and log files as Sms.db and Sms.log when you use the unattended installation method in SMS 2003 (843068)
The information in this article applies to:
- Microsoft Systems Management Server 2003
SYMPTOMSWhen you use the unattended installation method to script the installation of a Microsoft Systems Management Server (SMS) 2003 primary site, and you specify the SMS database file name and the SMS transaction log file name in the .ini file, these file name settings may be ignored. Instead, the SMS 2003 Setup program creates the SMS database file name as Sms.db and creates the SMS transaction log file name as Sms.log. CAUSE This problem occurs if you use Microsoft SQL Server version 7.0 or Microsoft SQL Server 2000. The DatabaseDevice= entry and the LogDevice= entry are not utilized when you use SQL Server 7.0 or SQL Server 2000. By default, the database file name is Sms.db and the SMS transaction log file name is Sms.log.
Note Because the SMS 2003 Setup program uses the same file names for every unattended installation, we recommend that you do not try to install multiple site databases on a single SQL Server-based server.RESOLUTIONTo resolve this problem, install SMS 2003 Service Pack 2 or a later service pack. For more information about how to obtain SMS 2003 Service Pack 2, visit the following Microsoft Web site: STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Systems Management Server 2003 Service Pack 1.REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
273734
SMS: How to set up unattended installation scripts
Modification Type: | Major | Last Reviewed: | 9/13/2006 |
---|
Keywords: | kbSMS2003SP1fix kbServer kbinterop kbsetup kbBug KB843068 kbAudITPRO |
---|
|