Those domains are Apple hosts related to push notifications, crashes, and Apple bug reports.
#MACOS UPDATE LIST SOFTWARE#
That'd be a way to push out updates off-cycle, but to also avoid overloading the Apple servers.) It is possible to cascade the Software Update Servers, so you could tailor the updates to specific local servers using this and DNS entries that'd be a way to move the updates closer to your clients.Īfter having set up local services, I haven't seen all that much load with multiple Apple devices around, though you will get the first updates going to the Apple servers for updates that aren't cached, and Software Update Server will chew up a whole lot of bandwidth when you first start it. It wouldn't surprise me to find push updates being used underneath the update notifications, either now or real soon now.
(Off-hand, I don't know of a way to schedule the Mavericks software update checks, and don't see any obvious settings in the defaults. With earlier versions, there are some controls on the scheduling and the frequency listed here. With Mavericks, the overnight updates typically happen between 2 and 5AM local time. One of the few somewhat-detailed discussions I've encountered is here. This based on comments around the forums. The two services reportedly do sometimes duplicate some data.Ĭaching Server 2 is restricted to certain network configurations and to certain geographies it's apparently not available world-wide, and only works with a properly structured NAT'd network.
Does it allow us to schedule the clients downloads or limit the clients sessions as a way to control the internal network bandwidth as well ?Ĭaching Server 2 and Software Update Server provide a means to host the updates, with the former hosting various software updates and iOS updates, while the latter hosts all current OS X and OS X Server updates and related materials.
0 kommentar(er)
