And yes, this tool was all command line driven too. I love that I can take a PKG and drop it in Casper and go. Now take all your DMGs, PKGs, and re-wrap them in order to deploy. Nothing worse than fumble fingering something when you're trying to hurry things along. During my testing I wrote a script to help automate the tasks. All of the client installation was command line driven with switches. While most of us here are technical people and we're not afraid of a terminal window, we often rely on other staff to help support our users. Ask your Windows admins to work without those two pieces and see what they say. So while you can deploy packages it won't do a full OS like Casper Imaging. A few highlights that you might relay back to the SCCM proponents. Granted, this was a couple of months ago and it was beta.
The managers above in the central IT department put us on hold and told us to look at SCCM 2012. We were just about to roll out a plan to have a central Casper service instead of the dispersed installation we have now. Best of breed man, best of breed.įunny this comes up. I hate to see the obviously better product lose to something that only half works, just because of the "we already have it" argument. I hope some of that helps, and I hope others chime in with their thoughts. I suspect you'll be waiting a bit on that, and of course your CEO/CTO/bigwig will want to get upgraded to it right away or else purchase a new Mac that only runs on that OS. Good luck getting an SCCM update to support 10.9 when that comes out. JAMF is also always within a few days of supporting any new OS releases, if not sometimes the day of release.
My response to that is always along the lines of, 'yeah, just like LANDesk or Altiris can effectively manage Macs, right? Oh, right.'īottom line is, do you want to trust your Mac management to a company that has historically short shrifted the Mac platform and usually comes up with some non standard way of implementing a feature, or a company that has a long history of fully understanding and supporting Macs in the enterprise and uses standard built-in technology to manage Mac clients. Just because Microsoft says they can do A, B or C, doesn't mean they do it right. I trust there are many places where SCCM can't stand up to Casper, but so much of it is semantics and bullet points on a spec sheet. As we are moving in the direction of FV2 for all 10.8 managed Macs, this was one thing SCCM couldn't do in relation to Casper. One of the things I discussed with them was the use of Casper's FileVault 2 escrow key management.
I don't know the full details of what Microsoft claims SCCM can do, but we have an SCCM installation here for Windows and, despite having a fully entrenched Casper management framework in place, our SCCM team began to drop hints that maybe we want to phase out Casper in favor of going with SCCM 2012?
0 kommentar(er)
