I’ve finally had enough. Maybe it’s the result of hearing people just blindly repeat false garbage and claiming it as fact (I call it “phact” now). But after hearing yet another so-called (another meme-ish aphorism du jour) engineer state to a group of other so-called engineers that “SCCM can ‘just randomly reimage computers'” because either:
A. They’ve seen it, or more often…
B. They heard a friend say they saw it happen.
Truth: NO. SCCM CANNOT RANDOMLY REIMAGE COMPUTERS. IT DOES NOT. IT WILL NOT. IT CAN’T. IT WON’T. Stop saying stupid shit like this.
The real reason is that someone (aka a stupid idiot, yes, double redundancy intended) was poking around and made changes without knowing what they were doing. That’s it. I’ve seen “unintended” cases of SCCM involved with reimaging computers, but it was ALWAYS ALWAYS ALWAYS (and still is) due to human stupidity.
I’m probably missing a few steps here, in fact, yes, I see one right now: The Task Sequence Deployment setting labelled “Make available to the following” from the Deployment Settings tab (e.g. “Only media and PXE” versus “Configuration Manager clients, media and PXE”, etc.)
In short, your resident idiot would have to target the wrong collection, OR, put the wrong machines into the targeted collection, OR, use the wrong deployment assignment setting, AND…
Have the machine on a subnet with access to PXE, AND boot to the network (boot config), AND press F12 before the boot time-out expires, AND (either) did not put a password on the Task Sequence deployment OR entered the password. That’s a lot of “accidental” stuff to accidentally trip over by accident. Maybe your admin needs a walker and a crash helmet.
- RANT OVER