between chain and replica georgestark 5/9/2007 1:24:00 PM Guys Hope you can help We have 12 offices around the country all linked with VPN (MPLS) sytem, all under one domain. We want to manage wsus from one server in our main office but want clients to get updates from the local office they are in. if we use replicas we have to move all computers into our varoius computer groups (3, test group, laptop group, desktop group) manually on each server. if we use chain we have to approve updates on each server. we want 3 GPOS test, lap, and desk all popinting to the same server http://wsus using round robin and subneting so clients get updates from closest server. hope this makes sense. Warren

Re: between chain and replica "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/15/2007 10:05:50 PM "georgestark" <georgestark[ at ]discussions.microsoft.com> wrote in message news:CD4594D3-B0C1-4E62-88EA-FD95D38A5306[ at ]microsoft.com... [Quoted Text] > Guys Hope you can help > > We have 12 offices around the country all linked with VPN (MPLS) sytem, > all > under one domain. > We want to manage wsus from one server in our main office but want clients > to get updates from the local office they are in. > > if we use replicas we have to move all computers into our varoius computer > groups (3, test group, laptop group, desktop group) manually on each > server. This is only required if you are *not* using Group Policy to assign group memberships using client-side targeting. > if we use chain we have to approve updates on each server. Correct. But with 12 offices, you may or may not need 12 servers. The key question is what is the bandwidth of the connections, and how many systems are on each remote site. If you have 5kb/sec of bandwidth per system, then you can distribute updates from a central location. > we want 3 GPOS test, lap, and desk all popinting to the same server Then you don't have the limitation of manually moving computers into groups on each replica server. > http://wsus using round robin and subneting so clients get updates from > closest server. WSUS using round robin is not a viable deployment strategy, for a number of reasons. BEST SUGGESTION: Look at WSUS 3.0 for additional options to your deployment strategy. Reevaluate how many physical servers you actually need. Design a deployment where every system has one, and only one, assigned WSUS server. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com ..... > >

Re: between chain and replica georgestark 5/21/2007 3:57:03 PM Thanks for your reply Lawrence "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "georgestark" <georgestark[ at ]discussions.microsoft.com> wrote in message > news:CD4594D3-B0C1-4E62-88EA-FD95D38A5306[ at ]microsoft.com... > > Guys Hope you can help > > > > We have 12 offices around the country all linked with VPN (MPLS) sytem, > > all > > under one domain. > > We want to manage wsus from one server in our main office but want clients > > to get updates from the local office they are in. > > > > if we use replicas we have to move all computers into our varoius computer > > groups (3, test group, laptop group, desktop group) manually on each > > server. > > This is only required if you are *not* using Group Policy to assign group > memberships using client-side targeting. > > > if we use chain we have to approve updates on each server. > > Correct. But with 12 offices, you may or may not need 12 servers. The key > question is what is the bandwidth of the connections, and how many systems > are on each remote site. If you have 5kb/sec of bandwidth per system, then > you can distribute updates from a central location. > > > we want 3 GPOS test, lap, and desk all popinting to the same server > > Then you don't have the limitation of manually moving computers into groups > on each replica server. > > > http://wsus using round robin and subneting so clients get updates from > > closest server. > > WSUS using round robin is not a viable deployment strategy, for a number of > reasons. > > BEST SUGGESTION: Look at WSUS 3.0 for additional options to your deployment > strategy. Reevaluate how many physical servers you actually need. Design a > deployment where every system has one, and only one, assigned WSUS server. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > > > > > > > >