Master Image Problem

[Trunk]

SMS 2.0 Site (SP5)

A few months ago, in preparation for deploying hundreds of new Windows 2000 PC's to our users, we created a master image that had the SMS client components installed, but with the unique SMS GUID removed. At the time the master image was created, our site was SP4. However, before the PC's were deployed, we upgraded our site to SP5.

It has now been two months since these hundreds of machines were deployed and they are still not showing up in our SMS site, despite the fact that we run SMSLS.BAT in our login script.

Upon investigation, we have found that these PC's still do not have a SMS GUID, the components are still SP4, and the SMS Client service is not starting because of a logon failure.

I am guessing that the fact that the SMS Client service is not starting (SMSCliSvcAcct&) is at the heart of the problem.

I can programmatically start services through our login script, but not if there is a logon failure.

Does anyone know of anything I can do other than having techs go around and deinstall the client manually? Sure would like to get the SMS Client service started somehow.


Tom Thaden
thadents@usano.ksc.nasa.gov

 

[RodTrent]

Are you saying all you did was remove the SMS ID? There's more to the SMS client than just the ID...there's only a few files that you can safely pre-install.

What happens if you deinstall the SMS client on a single computer? Will it correctly reinstall the client and fix the logon error?

Rod Trent
Microsoft.MVP.SMS
=======================================
Main site:

http://www.myITforum.com

=======================================

 

[Trunk]

Thanks for responding Rod...

It turned out that the master image we created was OK except for the fact that somehow the SMSCliSvcAcct& had lost the "Log on as a service" right. Therefore the SMS Client service was not starting on these machines.

Since these were Windows 2000 machines in a Windows 2000 domain, I was able to fix it by creating a Group Policy in the domain that gave the SMSCliSvcAcct& account the necessary privileges. These imaged machines are now showing up in our site.


Tom Thaden
thadents@usano.ksc.nasa.gov