![]() It isn't able to, for instance, judge that Firefox 29.0.1 is newer than Firefox 29.0. Casper also has issues with seemingly simple things like being able to determine the rank of software's version number. In my opinion, this is all handled much more effectively with Munki. Sometimes, if the package is really large, you end up with a policy that just downloads the package to the client and then another that does the install. Sometimes needing three or four that do slightly different things. And you can end up with pretty complex policies. For instance, to push out a piece of software, you have to upload the installer package to your JSS, go to the web interface to create a policy, add the package to the policy, set a bunch settings, and then scope that policy to a computer or group. The down side to casper is that it's pretty tough to automate anything. Casper lets you do a lot with their smart groups in organizing who gets what software or configuration profiles.Īnd their Self Service app is a really slick solution to give your clients the ability to install software or run scripts without giving them admin access. Munki has been pretty amazing for me with lab computers and automating, but i needed a bit more for our more mobile users. The Windows server and Mac OS server have no problem keeping up with 150 clients. The Windows server is in a Hyper-V cluster, highly available, SAN storage that is replicated to another colo, VM snap shots, full VM backups written to tape, tapes rotated offsite via Iron Mountain, etc. Other than having a local NetBoot server, I don't worry too much about multiple servers, replication, etc. Much faster to image from the NetBoot server directly using full gig Ethernet instead of the 300 Mbps WAN link to the colo. My Windows server is in the colo, NetBoot server is local. I've got DeltaCopy running on my Windows server and a cron job on my Mac OS X NetBoot server to keep packages in sync. My main instance is Windows, and while this works just fine it lacks the ability to distribute packages to other distribution servers. If you can, stick to running the Casper products on Mac OS and Linux. Somewhat overboard maybe, but we had the need to do some fairly targeted stuff. ![]() Yes, I have more policies and groups than I have Macs. I currently have 244 policies in my JSS, and 240 Smart Groups. are involved, and Apple Remote Desktop is a superior tool, so I use ARD. It doesn't work well when firewalls, NAT routers, etc. I used Recon quite a bit for the first week of Casper production to enroll Macs, after my Macs were enrolled I haven't touched it again. Recon will let you enroll Macs if SSH and remote management is enabled on those Macs. Usually you'll only run Casper Imaging from your NetBoot image (unless you're imaging a Mac in Target Disk Mode from another Mac.) Composer creates new packages. Casper Imaging does the actual imaging of Macs. Casper Admin is the tool for adding new packages and setting up your imaging configurations and workflows. There are some things you need the Mac apps for. Polices can deploy software, run a script, do maintenance items, make applications or scripts or other actions appear in the Self Service application, etc. Most of what you do in the web interface is create polices. Searching for Firefox.app on the other hand will bring up what you wanted. For example, searching for Firefox will yield no results. The search could be better in some areas. May require manual touch or some other magic to unenroll with Profile Manager and enroll with Casper. You may have issues transitioning from Profile Manager to Casper as you can only have your Mac (or iOS) enrolled with one MDM solution. You won't need Profile Manger or MCX with Casper, again you can do this in Casper Suite. Maybe you're doing this with Munki and some packaging tools now. Casper's own Self Service application will replace Munki's client, and a NetBoot server and Casper Imaging will replace the job of Deploy Studio.Ĭomposer is great for quickly making new packages that you can push out to your Macs. With Casper suite, you won't need Munki or Deploy Studio. It's very awesome and was well worth the money, though we had security requirements that factored into our decision as well. Currently using Casper for about 150 Macs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |