I know I have asked this before, but before I go on with a solid set of policies I want to get some feed back from the community on what works best for all of you. I have now set up 6 SUS servers, all 10.5.8 to cascade from one parent server to 5 children servers. I also upgraded every xserve with multiple drives so they are all running RAID 5 now. So, all I have to do is set up my parent SUS to select whatever downloads I want and enable them all my children servers will synchronize updates from the parent. Each child is set to auto download and enable from the parent. So I set it once and forget about it.
In the JSS I set up each SUS based on a network segment. So, I did some mass edits of locations and client data in the JSS to reflect this. Now, if I set up a self service policy to run software update, it will pull updates from the SUS set by the network segment settings correct?
I also want to write a simple Apple Script that interacts with the user and informs them a restart is required. I figure my users never reboot anyway so if they want the new version of iTunes they are getting a reboot. I want to warn them though, so they quit all their apps and save their data. This can be easily done with the System Events in Apple Script.
So, now that I have everything setup and working exactly how I want it to, I need to figure out how to implement the software updates to the clients. I am thinking self service is the way I will go, but not quite sure how to execute it just yet. Do I script it, via manual trigger policy, and then set each manual trigger policy to pull from the subnet it was triggered on? Do I just let Casper do all the driving? I do not want any updates to be downloaded across the WAN. Each building has it's own server and I want to keep all traffic with in the VLANs of each building from the building specific SUS.
Thanks in advance for sharing,
Tom