Client reimaged, SMS can't find it out, don't push agent

[Mirdus0001]

Hi,
machine reimaged, its account deleted in AD.
syspreped image on machine starts, joins succesfully domain with still the same comp. name.

SMS unable to discover that on machine is different inst, consequently agent push is not triggered.

When new machine(with not used comp name) joined everything works perfectly.
I do not suspect dns problems. In ddm.log for affected(reimaged) pc is "The DDR contains 25 properties, but none has new values".

How it is possible smsm is unable "find out" that it is new machine account-with new sid, having only comp name the same ???

Any tip appreciated. Thank you

 

[ncotton]

Do you want to fix this instance, or are you looking for future proofing against this issue?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[Mirdus0001]

I want to fix this instance and also prevent any other occurence in the future.

I mean I can deploy agent for particular machine some other way but I need SMS doing its job - pushing agent in every scenario.(new machine, existing machine reimaged.)

 

[willir]

What version of SMS are you using?

With SMS 2003 sp1, I reimage our test workstations all the time, and SMS always discovers them. I will actually end up with two records -- one for the newly imaged workstation and one for the old obsolete one. You can configure the old records to be deleted via the SMS setup. (Under Site settings -> Site Maintenance -> Tasks -> Delete Obsolete Client discovery Data set to True)

You probably know this...
To automatically update workstations also via the Site Settings -> Client Installation Methods -> Client Push Instllation - enable client push installation to assigned resources. ... if this is what you want. (Wish list would be to able to apply a filter on what workstations get the SMS client)

You can not use SMS to push a client install -- it needs the client to run a push.

I include SMS in the build rather than deploying SMS to all workstations on the LAN. It is part of the run after in an unattended install...

[GuiRunOnce]
Command0="C:\temp\MyCommand.exe

 

[SMSwannabe]

Hello,

is the Maintenance Task: Clear Install Flag enbaled?