a few WSUS 3 SP1 questions
i'll try keep clear , concise.
1. have 1 wsus server , 1 replica here @ our corporate offices (both dual core 2.3 ghz w/ 2 gb of ram running in vmware). have 60 - 70 remote offices through out continent of na , 7500 clients total. have seen on wsus sp2 documentation wsus can handle 25000 clients. if needed update of comptuers windows xp sp3 2 servers able handle or there i'm missing.
2. plan upgrade wsus3 sp2 , i've been reading through opsguide , deployment guide microsoft. should there other required reading understanding of wsus , optimizing it? or other helpful websites.
3. 1 of other things haven't been able find answer is, can have computers update patched status wsus don't directly downloads wsus? such maybe laptop users or users want let them own updating?
4. going sp1 sp2 in wsus there optimizations should once upgrade complete?
please let me know if need more info. appreciate or direction. thank you
1. have 1 wsus server , 1 replica here @ our corporate offices (both dual core 2.3 ghz w/ 2 gb of ram running in vmware). have 60 - 70 remote offices through out continent of na , 7500 clients total. have seen on wsus sp2 documentation wsus can handle 25000 clients. if needed update of comptuers windows xp sp3 2 servers able handle or there i'm missing.
2. plan upgrade wsus3 sp2 , i've been reading through opsguide , deployment guide microsoft. should there other required reading understanding of wsus , optimizing it? or other helpful websites.
3. 1 of other things haven't been able find answer is, can have computers update patched status wsus don't directly downloads wsus? such maybe laptop users or users want let them own updating?
4. going sp1 sp2 in wsus there optimizations should once upgrade complete?
please let me know if need more info. appreciate or direction. thank you
1. have 1 wsus server , 1 replica here @ our corporate offices (both dual core 2.3 ghz w/ 2 gb of ram running in vmware). have 60 - 70 remote offices through out continent of na , 7500 clients total. have seen on wsus sp2 documentation wsus can handle 25000 clients. if needed update of comptuers windows xp sp3 2 servers able handle or there i'm missing.
if have sufficient bandwidth between central server , remote sites, can update 7500 clients xp sp3 one wsus server. assuming you're not trying 7500 in 1 24 hour period, primary constraint deploying service pack via wsus available bandwidth of client download content. you'll need 10kb/sec of bandwidth per client @ site functionally support downloading of content. long time ago (~2005), in days of wsus v2, wrote article posted in wsus newsgroup examined, in great detail, bandwidth requirements deploying windows xp service pack 2 remote site using wsus. that's 10kb/sec number comes from. ostensibly article should archived in google groups. published on website, until crashed couple of years ago -- , i'm still searching around see if have 'copy' of website somewhere can recover content. based on 260mb size of xpsp2, needs adjusted increased size of xpsp3 25% larger --- 15kb/sec safe limit work xp sp3.
from server side, you'll have aggregate bandwidth consumption determine bottleneck in terms of how many simultaneous download sessions can support corporate wan connection -- or, perhaps, how many simultaneous sites can support. considering 7500 clients across 70 sites, that's bit on 100 clients per site, on average. i'm sure reality has range of clients. working 100 clients/site, however, that's 100/22 = 4.5 clients initiating download of xpsp3 each hour on first 22 hours time update approved. (my working assumption post approval late in day on friday , allow these downloads occur on weekend, not disrupt normal network activity.) package 316mb, can calculate based on available bandwidth how long take these downloads complete. @ minimum of 15kb/sec of bandwidth package can downloaded in 48 hours, , installed sunday evening across standard weekend. beyond bare minimum, can use available pipeline, adding download session every 12-15 minutes (based on 100 clients/site on 22 hour detection interval), maximum sustainable number of sessions site's pipeline -- , determine how long actual download period last. can adjust segmenting machines on site smaller deployment groups, if necessary , mix-n-match sites in deployment groups based on number of simultaneous connections wsus server need supported.
incidentally, load specification wsus3sp2 have been rewritten in sp2 deployment guide, , single-server scenario rated handle 100,000 clients 7 hour detection interval. determine wsus capacity requirements:
configuration: single server, non-nlb
capacity: 100k clients
hardware requirements:
intel core 2 quad cpu q6600 2.4ghz (or equivalent)
4gb ram
windows server 2003 standard edition sp2 x64
client synchronization configuration: 7 hour detection
assuming average of 10 requests per client, produces transaction rate on server of 6 clients per second.
the section contains paragraph relating point 100k client cap imposed cap, not performance-related cap:
be aware organization’s performance results may vary if choose use different hardware; however, maximum supported capacity figures not change. is, if use higher performance server indicated in table follows, there may increase in number of client synchronizations per second. however, there no increase in maximum number of supported clients configuration.
in wsus3sp1 there imposed cap maximum of 30,000 clients managed single server. value can changed via api call, option not exposed wsus admin console. interestingly enough, value has not been changed in wsus3sp2, deploying scenario may require 'tweaks' using api reset value "maximum allowed computers". setting documented in iupdateserverconfiguation.maximumallowedcomputers.
note: also, configuration assumes installation of windows internal database 32-bit environment. on win2003x64 run in wow64 mode. while microsoft not officially support higher client load -- it's matter of simple mathematics better performing database environment can produce better client transaction rates, , functionally service more clients officially supported -- theoretically. using back-end 64-bit database server have additional performance increases.
in event, offer simple answer question after dragging through extended dissertation -- wsus server not constrained resource in scenario -- network bandwidth.
2. plan upgrade wsus3 sp2 , i've been reading through opsguide , deployment guide microsoft. should there other required reading understanding of wsus , optimizing it? or other helpful websites.
the key document review regards upgrade release notes. relates optimizing wsus, microsoft hasn't published lot on topic; documentation, you've noted, tends focus more on functionality, rather optimizing. question, though, far optimization goes, place start optimizing database service platform wsus server using. if you're using back-end sql server, standard optimization objectives sql server apply. routine maintenance, reindexing, consistency checks, etc.
if you're using windows internal database, bit of optimization can obtained ensuring \wsus folder on dedicated physical volume (for database), , relocating \wsus\wsuscontent dedicated physical volume (for content storage). also, monitor actual memory usage of sqlserver.exe process, , if exceeds 1gb on 2gb machine, consider allocating more memory vm. thing keep in mind asp.net v2.0 resource consumer on machine, , needs it's own pool of cpu , memory support activities of asp.net webservices. frequent utilization of server cleanup wizard keep 'dead weight' out of database, , minimizing size of catalog scanned, reduces volume of data needs cached (or read disk if buffer cache not large enough) helpful. subsequent running scw, might find beneficial rebuild indexes. finally, radical optimization technique, can split client load os platform (and/or language) across multiple replica servers, reduces volume of metadata needs stored in database -- reduces size of catalog scanned, etc., etc. etc.
3. 1 of other things haven't been able find answer is, can have computers update patched status wsus don't directly downloads wsus?
absolutely!
to configure clients obtain content directly microsoft.com rather wsus server, still approvals wsus server, you'll need replica server configured not store local content. absence of local content store cause wsus server instruct clients download content microsoft.com. common deployment solution scenario describe mobile users.
4. going sp1 sp2 in wsus there optimizations should once upgrade complete?
i believe release notes has comments on this, 1 thing might consider rebuilding indexes. documentation doing in wsus operations guide.
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
if have sufficient bandwidth between central server , remote sites, can update 7500 clients xp sp3 one wsus server. assuming you're not trying 7500 in 1 24 hour period, primary constraint deploying service pack via wsus available bandwidth of client download content. you'll need 10kb/sec of bandwidth per client @ site functionally support downloading of content. long time ago (~2005), in days of wsus v2, wrote article posted in wsus newsgroup examined, in great detail, bandwidth requirements deploying windows xp service pack 2 remote site using wsus. that's 10kb/sec number comes from. ostensibly article should archived in google groups. published on website, until crashed couple of years ago -- , i'm still searching around see if have 'copy' of website somewhere can recover content. based on 260mb size of xpsp2, needs adjusted increased size of xpsp3 25% larger --- 15kb/sec safe limit work xp sp3.
from server side, you'll have aggregate bandwidth consumption determine bottleneck in terms of how many simultaneous download sessions can support corporate wan connection -- or, perhaps, how many simultaneous sites can support. considering 7500 clients across 70 sites, that's bit on 100 clients per site, on average. i'm sure reality has range of clients. working 100 clients/site, however, that's 100/22 = 4.5 clients initiating download of xpsp3 each hour on first 22 hours time update approved. (my working assumption post approval late in day on friday , allow these downloads occur on weekend, not disrupt normal network activity.) package 316mb, can calculate based on available bandwidth how long take these downloads complete. @ minimum of 15kb/sec of bandwidth package can downloaded in 48 hours, , installed sunday evening across standard weekend. beyond bare minimum, can use available pipeline, adding download session every 12-15 minutes (based on 100 clients/site on 22 hour detection interval), maximum sustainable number of sessions site's pipeline -- , determine how long actual download period last. can adjust segmenting machines on site smaller deployment groups, if necessary , mix-n-match sites in deployment groups based on number of simultaneous connections wsus server need supported.
incidentally, load specification wsus3sp2 have been rewritten in sp2 deployment guide, , single-server scenario rated handle 100,000 clients 7 hour detection interval. determine wsus capacity requirements:
configuration: single server, non-nlb
capacity: 100k clients
hardware requirements:
intel core 2 quad cpu q6600 2.4ghz (or equivalent)
4gb ram
windows server 2003 standard edition sp2 x64
client synchronization configuration: 7 hour detection
assuming average of 10 requests per client, produces transaction rate on server of 6 clients per second.
the section contains paragraph relating point 100k client cap imposed cap, not performance-related cap:
be aware organization’s performance results may vary if choose use different hardware; however, maximum supported capacity figures not change. is, if use higher performance server indicated in table follows, there may increase in number of client synchronizations per second. however, there no increase in maximum number of supported clients configuration.
in wsus3sp1 there imposed cap maximum of 30,000 clients managed single server. value can changed via api call, option not exposed wsus admin console. interestingly enough, value has not been changed in wsus3sp2, deploying scenario may require 'tweaks' using api reset value "maximum allowed computers". setting documented in iupdateserverconfiguation.maximumallowedcomputers.
note: also, configuration assumes installation of windows internal database 32-bit environment. on win2003x64 run in wow64 mode. while microsoft not officially support higher client load -- it's matter of simple mathematics better performing database environment can produce better client transaction rates, , functionally service more clients officially supported -- theoretically. using back-end 64-bit database server have additional performance increases.
in event, offer simple answer question after dragging through extended dissertation -- wsus server not constrained resource in scenario -- network bandwidth.
2. plan upgrade wsus3 sp2 , i've been reading through opsguide , deployment guide microsoft. should there other required reading understanding of wsus , optimizing it? or other helpful websites.
the key document review regards upgrade release notes. relates optimizing wsus, microsoft hasn't published lot on topic; documentation, you've noted, tends focus more on functionality, rather optimizing. question, though, far optimization goes, place start optimizing database service platform wsus server using. if you're using back-end sql server, standard optimization objectives sql server apply. routine maintenance, reindexing, consistency checks, etc.
if you're using windows internal database, bit of optimization can obtained ensuring \wsus folder on dedicated physical volume (for database), , relocating \wsus\wsuscontent dedicated physical volume (for content storage). also, monitor actual memory usage of sqlserver.exe process, , if exceeds 1gb on 2gb machine, consider allocating more memory vm. thing keep in mind asp.net v2.0 resource consumer on machine, , needs it's own pool of cpu , memory support activities of asp.net webservices. frequent utilization of server cleanup wizard keep 'dead weight' out of database, , minimizing size of catalog scanned, reduces volume of data needs cached (or read disk if buffer cache not large enough) helpful. subsequent running scw, might find beneficial rebuild indexes. finally, radical optimization technique, can split client load os platform (and/or language) across multiple replica servers, reduces volume of metadata needs stored in database -- reduces size of catalog scanned, etc., etc. etc.
3. 1 of other things haven't been able find answer is, can have computers update patched status wsus don't directly downloads wsus?
absolutely!
to configure clients obtain content directly microsoft.com rather wsus server, still approvals wsus server, you'll need replica server configured not store local content. absence of local content store cause wsus server instruct clients download content microsoft.com. common deployment solution scenario describe mobile users.
4. going sp1 sp2 in wsus there optimizations should once upgrade complete?
i believe release notes has comments on this, 1 thing might consider rebuilding indexes. documentation doing in wsus operations guide.
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