WSUS Downstream Server - How to point clients to it
so have wsus 3.0 sp2 configured , working great. server sits in main office , pushes out updates main office 4 other offices connected via t1 connections. offices in same domain but have own organizational units. offices have own subnets. 1 of these offices 100+ users , saturates our t1 connection office when updates pushed out. have configured downstream server in office. appears getting updates upstream server. i'm trying figure out how force clients in office it's updates downstream server instead of main wsus server.
right now, group policy (specify intranet microsoft update service location properties) applied @ domain level , points computers main wsus server. best idea far i'm trying stop applying policy @ domain level , set individually each of our ous (therefore each office). common way handle i'm trying or there better way?
thanks.
right now, group policy (specify intranet microsoft update service location properties) applied @ domain level , points computers main wsus server. best idea far i'm trying stop applying policy @ domain level , set individually each of our ous (therefore each office). common way handle i'm trying or there better way?
thanks.
> thought wsus clients used bits default?
they do! bits of misleading entity, determines bandwidth availability based on =lan= connection of machine, not slowest pipe in entire download path. that's using group policy configure bandwidth availability (either throughput, or time of day) becomes essential. if there's more megabit of available bandwidth on lan connection (and there these days), bits try use bandwidth on wan connection.
> decent amount of our users shut down computers @ night - meaning wouldn't updates.
> management pretty never backs @ shop, enforcing policies proves extremely difficult for
> it. working on wake on lan solution separate project may me out wsus, it's still
> several months away implementation.
the default configuration of wuagent can of here. if scheduled installation event missed overnight (because pc powered off), wuagent initiate installation of scheduled updates @ 1 minute after automatic updates service restarts @ boot time. (this value can extended 60 minutes, via group policy.) let users annoyed enough power-on installation/reboot scenarios, , point out need avoid inconvenience is leave machine powered on overnight, , problem solve itself. (you can scenario sending notification when approve updates deployment particular site.)
also... note windows xp sp2 , later systems support installation of updates @ shutdown event, , if natural practice power off machines @ end of day, encourage users use "install updates , shutdown" feature avoid inconvenience of installations @ power on.
as "management"... learned long time ago -- best way management support wanted, if couldn't achieve simple intelligent logic, make "not supporting it" unpleasant possible them. in other words -- biggest cheerleader leaving machines powered on, or using "install updates , shutdown" inconveniencing cio, or staff members who whine , cry cio, when he/they have sit through morning restarts in order install updates @ power on. excuse: "uhh... sorry. that's behavior of wuagent. can't change it." (they'll never check documentation find out that's not entirey true. >;-d
lawrence garvin, m.s., mcitp:ea, mcdba
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
they do! bits of misleading entity, determines bandwidth availability based on =lan= connection of machine, not slowest pipe in entire download path. that's using group policy configure bandwidth availability (either throughput, or time of day) becomes essential. if there's more megabit of available bandwidth on lan connection (and there these days), bits try use bandwidth on wan connection.
> decent amount of our users shut down computers @ night - meaning wouldn't updates.
> management pretty never backs @ shop, enforcing policies proves extremely difficult for
> it. working on wake on lan solution separate project may me out wsus, it's still
> several months away implementation.
the default configuration of wuagent can of here. if scheduled installation event missed overnight (because pc powered off), wuagent initiate installation of scheduled updates @ 1 minute after automatic updates service restarts @ boot time. (this value can extended 60 minutes, via group policy.) let users annoyed enough power-on installation/reboot scenarios, , point out need avoid inconvenience is leave machine powered on overnight, , problem solve itself. (you can scenario sending notification when approve updates deployment particular site.)
also... note windows xp sp2 , later systems support installation of updates @ shutdown event, , if natural practice power off machines @ end of day, encourage users use "install updates , shutdown" feature avoid inconvenience of installations @ power on.
as "management"... learned long time ago -- best way management support wanted, if couldn't achieve simple intelligent logic, make "not supporting it" unpleasant possible them. in other words -- biggest cheerleader leaving machines powered on, or using "install updates , shutdown" inconveniencing cio, or staff members who whine , cry cio, when he/they have sit through morning restarts in order install updates @ power on. excuse: "uhh... sorry. that's behavior of wuagent. can't change it." (they'll never check documentation find out that's not entirey true. >;-d
lawrence garvin, m.s., mcitp:ea, mcdba
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
Post a Comment