See all of the top support solutions for our most common issues here
~ Larry Mosley
Every once in a while, we here in product support will get a call where someone has deployed a task sequence that formats and installs a new OS to the ‘All Systems’ collection, or to a collection that contains many computers. Please, always be vigilant and careful when targeting OSD task sequences (or any software, really) to the ‘All Systems’ collection, or any other collection with a large number of important computers in it. Configuration Manager doesn’t have an intention checker, and if you deploy a Task Sequence that does something like format the hard drive and apply an OS image, Configuration Manager will happily tell the clients to follow those instructions, wiping the disks and installing a new image to all the machines that receive the policy.
Needless to say, this can have serious consequences, and there is no ‘UNDO’ or ‘I didn’t meant to do that!’ button in Configuration Manager.
Larry Mosley | Senior Escalation Engineer | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
ConfigMgr 2007 ConfigMgr 2012 R2
jejejeje... This is how you see the entire world falling over you!.... I had to stop this mess 2 times for different clients.. It also can happen if you create a collection and left an empty collection query... by default It will add everything!. So YES!...
check 10 times the collection prior send anything...
There could be multiple ways to stop the execution but this is what I used to do so:
Yes creating an empty query collection will result in this as has been described in this KB: