Just trying to get a feel for how long it takes WSUS to push out updates to your machines. Time it takes to go from update approval to client download and install. (self.sysadmin) submitted 3 years. The 'Automatic Updates detection frequency setting' can only be set to a number of hours and controls how often clients check in and look.
We have a wsus server running. All our servers and clients refer to this wsus for updates. We also have the gpo in place and the option 'Configure automatic updates' is set to '3'. Now i have an update which i want to push to my clients/servers directly and i want it to be installed (and rebooted) immediatly and automatic. I changed the configure automatic updates setting to 4 and the schedule is every saturday at 20:00 (one hour from now).
I also disabled 'No auto restart' and I've set the auto detection frequency to 1 hour. Will this work or do i need to do something else? I'm not sure because all of this is set in the computer settings of a gpo so i got this feeling that i need to reboot all servers/clients upfront before they see the changes in the gpo.
If I understand your question correctly your asking i need to reboot all servers/clients upfront before they see the changes in the gpo. If the GPO will be seen by the devices or do you need to reboot them. The answer to your question is if you go to the server and force the GPOs out to the machines then you shouldn't have to restart the devices. You can do this by I didn't see you specify your server OS so I choose server 2012r2 its pretty similar across the board to force the GPO to refresh down to the clients.
Ever wondered how rate limits on Distribution Points in ConfigMgr 2012 work? When I one day accidentally updated all the distribution points at a customer site it was time to learn quickly. There are three modes for rate limits and these are set per Distribution Point. Unlimited sending is self-explainatory, but the pulse mode and the option to limit specific maximum transfer rates per hour are useful in different scenarios. I´ll explain the limited to specified maximum transfer rates by hour option first, since it was what helped me quickly in my scenario. First of all, there is no native ConfigMgr support for BITS when distributing content to Distribution Points, therefore, ConfigMgr does not monitor the traffic and/or the amount of data going over the link. Instead, it uses the time available for sending and divides the time into time slots where it sends 100% of data.
![Instrument detection limit calculation Instrument detection limit calculation](http://eskonr.com/wp-content/uploads/2015/04/image25.png)
So, for instance, if you use the option to use only 50% of bandwidth during work hours (ie 8AM to 4PM), it will divide the amount of available time into time slots and send 100% of data 50% of the time, and send 0% data the other 50% of the time. This is useful if you don´t want to clog the available bandwidth on the network during work hours or if you need to limit the transfers for some other reason. This can be set per hour for every day, but unfortunately you can´t set it for specific days (as you sort of could in Configuration Manager 2007). It is also possible to use pulse mode, in which case you can specify the size of the data blocks sent by the site system to the distribution point and a delay in seconds for how often these blocks should be sent. This is useful if you have slow links to your distribution points, but it requires you to calculate how much data is sent. If you set it too low your packages will never be distributed, if you set it too high it will still clog your bandwidth. Notice that these are radio buttons, so you can only choose one option at a time for one specific Distribution Point.
As you can see in my example I set it to transfer only 50% during working hours for all my distribution points, and I immediately saw the effect on my site servers bandwidth. It is also possible to use the Schedule option on your Distribution Point to restrict what kind of traffic can be sent during different hours of the day. This applies to the priority of content, so say that you have software update packages that you know you want to distribute but everything else can wait. If you set your software update packages to high priority and everything else at medium, then you can effectively block medium priority content from being distributed but let high priority content get distributed by selecting the option Allow high priority only.
![Wsus Script Force Update Detection Limit Calculation Wsus Script Force Update Detection Limit Calculation](https://play.vidyard.com/dp3eRc6ME4EndDAcVLbppM.jpg)
You can read more about the in the Configuration Manager Document Library.