need to force detection (not install) between 7 at night and 5 in the morning.


i have install time set gp, need prohibit detection/download time non-buisness hours.  know detection interval can used, seems "detect within many hours of last reboot time" - meaning if users reboots @ 3:00 pm detect time of 22 hours, detect every day between before lunch , after dinner.

can limited range of clock times, rather moment service last started?

i have install time set gp, need prohibit detection/download time non-business hours.

you cannot restrict detection time. occurs every x hours (22 hours default).

you can, however, restrict when downloads can occur. done configuring background intelligent transfer service (bits). please refer wsus technical reference guide:  improve wsus download performance bits for more information.

i know detection interval can used, seems "detect within many hours of last reboot time"

actually it's based on "so many hours" since last detection time.

meaning if users reboots @ 3:00 pm detect time of 22 hours, detect every day between before lunch , after dinner.

it has built in 0-20% negative offset, in reality, next detection time (randomly) sometime between 17.6 , 22.0 hours after end of recent detection time, detection will not occur in same time block every successive day.

can limited range of clock times

no.


lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
solarwinds head geek
microsoft mvp - software distribution (2005-2013)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
the views expressed on post mine , not reflect views of solarwinds.



Windows Server  >  WSUS



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607