Hiya,

Our setup is as follows, but our links are 100mb between sites, not sure 
if thats classed as slow or not.

Main WSUS server in HQ
6 remote sites with downstream servers

Downstream servers sync with the master between 2 and 3 AM, so there is no 
intersite traffic during working hours, unless I approve something then I 
manually sync it, but it wouldn't be a massive size.

The servers and desktops were recently seperated onto their own WSUS 
servers, the servers are managed by a single WSUS in HQ.

We have the desktops managed by GPO into their target groups with install 
time set to 4pm, which actually runs at 3pm due to daylight bloody savings 
time.
Reboot prompts are set to 30 minute intervals.

Main gotcha I came across when setting it up was that the downstream 
servers need to manally sync quite a number of times before they get all 
the updates downloaded.

Just run the server cleanup wizard on the master before setting up the 
downstreams, otherwise you;ll be transferring updates that aren't needed.

HTH


Tony Patton
Desktop Operations Cavan
Ext 8078
Direct Dial 049 435 2878
email: [email protected]



Clayton Doige <[email protected]> 
10/06/2009 09:37
Please respond to
"NT System Admin Issues" <[email protected]>


To
"NT System Admin Issues" <[email protected]>
cc

Subject
WSUS WAN Advice







Hi all, I am hoping some of you can offer some advice with regards to 
deploying Child WSUS server in a Windows 2003 server/XP Professional 
environment when the organisation is spread across multiple sites 
connected by slow WAN/VPN links.
 
How do you manage the deployment of patches to child servers at the sites, 
how are you setting up computer groups (via group policy or WSUS itself). 
I am just looking to get an idea of the best way to deploy the Child sites 
to minimise the impact of update downloads on the WAN links really.
 
Not urgent, just seeking any advice, experience and gotchas I might want 
to be aware of.
 
Many thanks
 
Clayton
 
 
====================================================================
http://www.quinn-insurance.com

This e-mail is intended only for the addressee named above. The contents
should not be copied nor disclosed to any other person. Any views or
opinions expressed are solely those of the sender and
do not necessarily represent those of QUINN-Insurance, unless otherwise
specifically stated . As internet communications are not secure,
QUINN-Insurance is not responsible for the contents of this message nor
responsible for any change made to this message after it was sent by the
original sender. Although virus scanning is used on all inbound and
outbound e-mail, we advise you to carry out your own virus check before
opening any attachment. We cannot accept liability for any damage sustained
as a result of any software viruses.

====================================================================

QUINN-Life Direct Limited is regulated by the Financial Regulator.
QUINN-Insurance Limited is regulated by the Financial Regulator and
regulated by the Financial Services Authority for the conduct of UK
business.

====================================================================

QUINN-Life Direct Limited is registered in Ireland, registration number
292374 and is a private company limited by shares.
QUINN-Insurance Limited is registered in Ireland, registration number
240768 and is a private company limited by shares.
Both companies have their head office at Dublin Road, Cavan, Co. Cavan.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to