Accidently deleted workstations from SCCM database

[guest]

I am getting some inventory and software metering errors and noticed it's because some workstations were accidently deleted from the SCCM database.

I've re-imported the workstations (manualy) in the database. However, these workstations have new SMS GUIDs that do not correspond to the GUIDs on the physical workstations.

Will these GUIDs re-synchronize automaticaly through SCCM or must I do something? Was this the best way to handle accidently deleted workstations?

[guest]

No, you do not need to reinstall the client. The clients need to send up a heartbeat, also known as "Discovery Data Collection Cycle", if you're looking at a client's Contro Panel ConfigMgr applet, Actions tab.

Then either wait for those to be retried, or just have those boxes send up a full Hinv and Full Sinv. If you go with the "just wait", it'll resolve itself over time. But if you want to force it, I'd do a Heartbeat; wait a few min, then a hinv, wait again (then check v_gs_workstationstatus.lasthwscan, joined to v_r_system_valid, and make sure it's what you expect, then a Sinv. I'd do Sinv last simply because it's a hog on the client. hinv is quicker.

Personally, I'd just go with the please wait; and let them resolve themselves. But I'm probably inherently lazy.... I know it'll fix itself over time. But I understand if you just want it to "get it back". You'l lose the advertisement history for those specific boxes in the database--that won't come back unless you d a restore--but the boxes themselves won't lose their history. They'll have a history locally of having run any advertisements. So it should be fine; unless you've done some really really creative things with collection creation targets for advertisements based on advertisement success/failure. Most people don't, so I doubt you'll have something like that.
--------------------------------------------------------------------------------