In my short but long lived 12 year tenure here in IT I have seen SMS attempt to install a service pack to computers on the trade floor in the middle of production hours. I’ve seen SCCM reboot a trade floor in the middle of production hours. I’ve seen CM totally destroy AppV configurations on 50 servers because an administrator decided to make a site level change during production hours (not like it would make a difference). I’ve been prompted more than 5 times in one day to reboot because CM or WSUS has installed a patch on my computer. And I’ve lost the OS on a laptop because of a encryption deployment that went array.
I’m sure we all have our stories as we have struggled to better understand and make due with the various implementations of the once SMS. But, amidst all of the trouble I still believe there is some good in what’s now called CM. That being said, I’ll first admit I’d rather write my own scripts, code and install procedures but sometimes our daily tasks are two cumbersome and we need the help of utilities like CM.
Here are some of the better things CM can do assuming your admin is not a moron and the applications and advertisements (deployments) are configured correctly.
Some of the disadvantages are evident as well. Why cant I just use Group policy for app deployment and configuration management? You can, but why not just fork over the extra cash for license cost and hardware? Blah blah, with SCCM you can schedule deployments to occur during off-peak times, and stagger your deployments, but we all know how that can end up.
What are my alternatives for patch deployment, software deployment, and configuration management?
|
|||
