I'm preparing a system image that will be on machines going to customers. The system is a Dell PE1950, running Windows Server 2003. One of the applications that these machines will run requires IIS and SQL 2005 Express.
All my research says that SQL should break when sysprep is run, but unconfigured IIS should be OK. I did a quick test in a VM to see what would happen to SQL when sysprep is run, but everything seems to be working fine...
A few examples of the info I'm finding:
The problem:
http://community.sgdotnet.org/.../2005/12/13/23344.aspx
http://blogs.msdn.com/virtual_...-server-installed.aspx
And the fix:
http://support.microsoft.com/kb/303774
Now my machine name definitely changed. Yet my app runs fine, Management Studio Express shows the new db server name, everything seems to be totally OK.
Is SQL Express immune to this? Am I just missing the real problem?
Viper GTS
All my research says that SQL should break when sysprep is run, but unconfigured IIS should be OK. I did a quick test in a VM to see what would happen to SQL when sysprep is run, but everything seems to be working fine...
A few examples of the info I'm finding:
The problem:
http://community.sgdotnet.org/.../2005/12/13/23344.aspx
http://blogs.msdn.com/virtual_...-server-installed.aspx
And the fix:
http://support.microsoft.com/kb/303774
Now my machine name definitely changed. Yet my app runs fine, Management Studio Express shows the new db server name, everything seems to be totally OK.
Is SQL Express immune to this? Am I just missing the real problem?
Viper GTS
