SMS Client causing Logon problem with NT4 clients

[SerXI]

Basically we have a NT4 ghost build which has now been rolled out to around 15 clients, the SID's have not been removed from this image so are all the same, this does not cause a problem in a DOmain enviroment, so everything has been fine. We have now just rolled out SMS client and all looked OK but then we had users reporting they were having logon problems either a)After pressing CTRL+ALT+Del to logon, only 2 boxes appear (username & password) no Domain box, after rebooting several times the correct logon box would appear. or B) after logging in PC would freeze before desktop appeared. Again after several reboots would be OK.

Does the SMS client use the Local SID in anyway ?

We have managed to fix some of these by uninstalling the SMS client then removing PC form the Domain, running Ghost walker to change the SID's. But this has not worked for all of them.

Any ideas ?

 

[gupel]

There is an utility - newuid.exe in the BackOffice RK, that can change SMS ID. SMS client uninstallation also solves the problem. Than delete all client with duplicated ID from SMS database.
It is better do not include SMS client in the image and use sysprep or Ghost walker before you join the domain.

 

[wrarmykeys]

As Gupel stated, running newuid.exe is the most efficient way to resolve a cloning issue. Run the utility with the /s /allocate switches. Newuid.exe is included with the SMS resource kit. Here a link for more information regarding managing duplicate SMS GUID's:

http://www.microsoft.com/smserver/techinfo/administration/20/maintaining/newuid.asp

It is possible to uninstall the client with 20Clicln.bat, but you will also need to manually delete two files and a registry key containing the SMS unique identifier.