Newsroom Update
Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >
Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >
Just wondering if anyone can confirm whether or not the Caching Service or Software Update Service in Mountain Lion Server supports Mavericks clients? Or, does it only support Mountain Lion clients?
Thanks,
Kristin.
Bugger.
OK, that rules out SUS. How about the Caching Service? Anyone know if that feeds Mavericks clients? I was really hoping to use the Caching Service (versus SUS) as part of our Mavericks migration, but with the File Sharing issues in Mavericks Server, we're stuck on Mountain Lion Server for the time being. So, still hope for the Caching Service...?
Officially as per the article infinite vortex linked to the Mountain Lion SUS server does not support Mavericks clients.
Unofficially you probably could modify it to server Mavericks updates as well however it just is not worth the hassle. You would instead be far better of replacing Apple's SUS module with the free Reposado software which as standard lets you server all versions no matter what version of OS X it is running on. In fact Reposado does not even have to run on a Mac at all, many people run it in a Linux server environment.
See https://github.com/wdas/reposado
You can also get a web admin interface for Reposado
Yea, I've been wresting with SUS since Leopard Server, modifying the SUS preferences (and related) to feed unsupported clients, but it's always been a back & forth battle, with each update, reboot, etc. Plus, with more and more client machines being "mobile", not having them locked to a LAN-based SUS was a major "pro" for the caching service. So, kinda have my hopes set on Caching Service being able to deal with Mavericks clients. And, in the event that that doesn't/didn't pan out, a third-party SUS (like Reposado) was my fallback plan.
Have you considered maybe running yourself a 2nd server to specifically run these services? For instance, my primary server pair are running Lion Server on mid-2011 Mac minis and what we've done it to grab our much older, and deprecated, early-2009 Mac mini server and put Mavericks server on it and run it solely for those services that Lion server doesn't offer, like Caching and SUS. While all services are fully configured to test implementations with they're turned off for the most part.
Yea, I actually run our current SUS on an older Mac Pro. It provides both Apple software updates and Adobe software updates (for our Adobe deployments) and is dedicated to these two services. My primary server (running Mountain Lion—capable of Mavericks, but again, because of the File Sharing issues in Mavericks Server, we're sticking with ML Server for the time being) is a loaded 2009 Xserve—which I don't run "secondary services" (my term <G>), like SUS, on.
Unfortunately, the current SUS box won't do Mavericks Server (though, I have tested running a VM of Mavericks Server, just for SUS and Caching, inside the physical OS, and it worked fine, but seemed like a waste of system resources and just really didn't make much sense—and a bare metal install doesn't work because of RAID, etc.), so I was considering the Caching Service in ML as an alternative (if it did, in fact, feed Mavericks clients). I realize I could just "turn it on" and see what happens, but would rather look into first (as I assumed others would have ML Caching Service on, and probably had Mavericks clients on the network, so would have the info I was looking for).
Anyway, at this point, unless ML Server Caching Service will do the trick, Reposado it is.
k.
Well, I went ahead and activated Caching Service in Mountain Lion Server. Downloaded a couple updates on my iOS 7.1 device, all good (Caching Server reported a 32 MB cache, which was the size of the two downloads combined). Then, a couple updates appeared for my Mavericks clients so I downloads them (ARD update @ ~20 MB and Server update @ ~100 MB). Checked back in Mountain Lion Server, and sure enough—total cache was just over 132 MB, which leads me to believe it's caching Mavericks updates (as the Server update that was offered was a Mavericks-only update).
So, looking good so far for Mountain Lion Server Caching Service supporting Mavericks clients...
k.
Mountain Lion Server: Does the Caching or SUS support Mavericks clients?
