WSUS Design Question/Clarification

[AParker83]

We are about to implement WSUS in an environment of approximately 300
employees. A few questions about our design strategy have arose:

1.) We have 11 offices. We are planning on having one WSUS server in each
office. We're considering one of two design strategies:
a.)One primary WSUS server, with all other WSUS servers basing their
update information on this one server. Each WSUS server would download
updates individually from Microsoft Update as opposed to distributing the
updates over the WAN. Central management over all 11 WSUS servers (from the
primary WSUS server?)
b.)Dividing offices by region into three centralized management groups:
West, Central, and East. This would basically work the same way as option
A, but each region would be centrally managed as opposed to all 11 offices.
We'd also still want each individual WSUS server to download updates from
Microsoft Update, and not have them distributed across the WAN.

2.) We host our SQL databases on a SAN in our data center. Would it be
feasible (or even possible) to use this as the home for the WSUS databases
for all WSUS servers? Or does the "one WSUS database per SQL install" still
apply for remote SQL deployments?

3.) We have a lot of users that are frequently not in an office. Does WSUS
allow for a "fall back" location where updates can be downloaded from (i.e.
accessing Microsoft Update directly)?

That looks like a lot. :-) I think that's it for now.

[CrossGeorge]

Hello,

did you get an answer to your question?