Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
WindChaser
Posting Yak Master
225 Posts |
Posted - 2008-05-23 : 08:22:35
|
Hi folks.When installing SQLServer 2005 Express, I use the following command line: cmdline = " /qb ADDLOCAL=SQL_Engine,SQL_Data_Files SECURITYMODE=SQL INSTANCENAME=MyServer SAPWD=MyPwd DISABLENETWORKPROTOCOLS=0 SQLAUTOSTART=1 requiresmsiengine=1"I noticed that when installing on a Windows XP machine, the installation results in a SQLServer instance which is configured with Built-in account = Network Service. However, with the same command line used on Windows 2000 machines, the configuration winds up being Built-in account = Local System. My understanding is that the default configuration is supposed to be Local System.What can I do to ensure that the instance configuration is always Local System during the silent installation? This is required otherwise, under the Network Service configuration, it creates a messy situation to attach DBs.Thanks!Mike |
|
WindChaser
Posting Yak Master
225 Posts |
Posted - 2008-05-23 : 15:17:47
|
After hours of searching, just found the information on MSDN as well as the solution. I'm posting it for future reference in case someone else encounters the same problem.According to MSDN, [SQLACCOUNT], [SQLPASSWORD], [AGTACCOUNT], [AGTPASSWORD], [ASACCOUNT], [ASPASSWORD], [RSACCOUNT], and [RSPASSWORD]This is information for the Service Accounts dialog box. These parameters are required for both stand-alone and virtual server installations. If these parameters are not specified, Setup will fail.If these parameters are not specified for installations of SQL Server Express Edition, Setup will default to a specific built in machine account depending on the underlying Operating System:For Windows XP and Windows 2003, the default service account will be NetworkService (NT AUTHORITY).For Windows 2000, the default service account is LocalSystem (NT AUTHORITY\SYSTEM).Important: Microsoft recommends that you do not use the Network Service account for the SQL Server or SQL Server Agent services. Local User or Domain User accounts are more appropriate for these SQL services. My dumb-ass question is why does Microsoft make the default service = NetworkService for Windows XP and Windows 2003 if they recommend not using it !!!!!!!!!!!! But I digress. The appropriate command line parameters are:/qb ADDLOCAL=SQL_Engine,SQL_Data_Files SECURITYMODE=SQL INSTANCENAME=MyServer SAPWD=MyPwd SQLAccount="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SQLAUTOSTART=1 requiresmsiengine=1Thanks to all who took time to look at the post! |
|
|
|
|
|
|
|