I think this will happen to most of us sooner or later, you send out an advertisement of an application or even worse an OSD deployment and it targets more than you bargained for, end result, mayhem and panic ensues. In the midst of the panic you might do something that will make figuring out who is affected by this even harder so to save you some grief i’ll tell you:
* do keep the advertisement
* do EXPIRE the advertisement,
* do keep the package/osd task sequence
* do NOT delete anything !
* do NOT delete the advertisement, deleting it will mean you cannot run reports on it and it will be removed from the ConfigMgr database along with reporting details that would make debugging your mess easier.
If you are wondering why I say don’t delete the advertisement, well think of this, being able to run reports will tell you who got the advertisement, who accepted it, who ran it, etc. Without it (by deleting it) will mean you have none of that data easily available. You could of course pull the execmgr.log logfiles from all clients to see were they affected by the old Advertisement ID….
In addition, if you delete the advertisement that doesn’t stop it from executing on the clients that already received the policy until they get a policy refresh. If you want to halt the advertisement in its tracks then you need to Expire it. Expiring an advertisement will PUSH a policy change to all clients that received the advertisement and thereby disable it. To expire the advertisement select the Schedule TAB and fill in your Expiration details and click Apply.
Related reading >
- How To Remediate An Incorrectly Deployed OSD Task Sequence In System Center Configuration Manager 2007
- How to stop an errant Advertisement in SMS 2003 / SCCM 2007
- SCCM Task Sequence blew up Australia’s CommBank