What is the logic behind scheduled syncs??!?!


why in world can schedule sync, second approve updates has download them second hit approve.  t1 smoked becasue wsus wants download gigs worth of updates second hit approve...how approve updates delay download until after hours of cannot afford oc3 connection?

"i'm getting there"

why in world can schedule sync, second approve updates has download them second hit approve.  t1 smoked becasue wsus wants download gigs worth of updates second hit approve...how approve updates delay download until after hours of cannot afford oc3 connection?

"i'm getting there"

i feel pain, josh, you're expecting how product designed work, nor desirable behavior.

consider operational paradigm:

1. wsus server synchronizes it's catalog microsoft update wsus administrator can see updates available.

2. wsus administrator reviews catalog contents , determines updates actually needed in environment. different admins have different procedures doing this. preference let client systems scan catalog , report updates need install. evaluate updates, , if they're [a] appropriate installation, [b] aren't cause problems other applications have installed, , [c] not superceded -- approve updates installation.

the key point needs understood here approving update @ wsus server authorizing client systems install updates. client systems cannot install updates unless binary content available them download wsus server, next step required after admin approves update is:

3. wsus server downloads binary content update when approved installation.

4. once content downloaded server, client downloads content , schedules installation according policies configured.

so... let's brutally honest here second... t-1 not smoked because of flaw in product, it's smoked because:
[a] didn't learn how product operates before deploying in production environment
[b] approved hundreds of updates didn't need approve.

so, starting point, suggest wsus product documentation in technet library.

also, i'd suggest webcast did in may, 2009, talks recommended practices initial deployment of wsus server.
lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2009)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
blog: http://onsitechsolutions.spaces.live.com


Windows Server  >  WSUS



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL