Whenever someone asks me why we went with SCCM "instead of" WSUS, I tell it like this:
Picture the average pizza delivery guy. He has a Ford Fiesta or something, and he drives around with one pizza at a time, delivering it the way everyone expects he would. Everything is working fine, deliveries are on time, the pizza's always hot like it should be, and everyone generally gets what they ordered. Or, at least, whatever went into the car with the delivery guy, anyway (back end issues aren't his fault).
All of a sudden, this one place starts ordering pizza, but not a single pizza at a time. They want 1000 pizzas at a time, and they want all of the pizzas to be different. But in the end, the pizzas are still all made of the same stuff, so the same delivery guy is forced to abandon his Fiesta, and he now delivers the pizzas in a Mack truck. Same pizzas, same ingredients, but 1000 of them at a time, and this is where the fun starts. Because it's just one guy loading all the pizzas into the truck, they're cold when he finally arrives, he has no idea where anything is in the truck, and it's anyone's guess as to who gets which pizza, whether they got what they wanted, whether all the pizza made it in to the truck in the first place or whether that really even is pizza in the box in the first place, because the delivery guy is so swamped dealing with the sheer volume of it all that he's forgotten what he was doing really well in the Fiesta in the first place.
That, my friends, is SCCM. Fuck that entire product as a patching mechanism. It manages to take WSUS and make it so overly complicated that you lose sight of the trees, and hopefully, you get what you want from the forest. Eventually.
