|
|
In WSUS 2.0 there was an equation to how many computers you can manage, the
equation being 15,000 computers at 22 hour checkin, 7500 computers per 11
hour checkins, etc. In WSUS 3.0 I have found no reference to this and have
read it can support many more clients than before. From what I can find in
the read me docs, it doesnt appear to have a limitation with the database but
is more related to the hardware that WSUS is running on.
http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true
My question is, if a front end server with a backend SQL is done with 3.0
does the hardware requirement apply to both servers are is one much more
important than the other. I would prefer that clients and server check in as
frequent as possible but as I found out in 2.0 it will overfill the tbevents
field leaving your server unfuctional and having to manually clean out the
table. We currently have around 4000 pc's and 100 servers. I would like to
have my servers checkin every one hour and PC's every 3 hours. Does anyone
feel I will have problems with this bogging the WSUS server down or worste
the clients. My front end server is dual 3.0 xeons with 1 gig of ram and a
back end SQL 2005 server on dual 2.8 xeons with 2 gigs of ram. I am also
guessing that the IIS logs will be larger so a bit more space may be needed
on the front end, I also planned to schedule the script to reindex the the
database every weekend . Any help or insight would be appreciated in specing
out my setup.
|
|
"Daniel the Security Guy" <DanieltheSecurityGuy[ at ]discussions.microsoft.com>
wrote in message news:B20C3E12-0529-40D9-8A9B-064626D5ACE6[ at ]microsoft.com...
[Quoted Text] > In WSUS 2.0 there was an equation to how many computers you can manage,
> the
> equation being 15,000 computers at 22 hour checkin, 7500 computers per 11
> hour checkins, etc. In WSUS 3.0 I have found no reference to this and
> have
> read it can support many more clients than before. From what I can find
> in
> the read me docs, it doesnt appear to have a limitation with the database
> but
> is more related to the hardware that WSUS is running on.
The 15,000 client limitation in WSUS 2.0 was directly caused by a limitation
in the database maintenance procedures written for WSUS 2.0.
Those procedures have been remediated, and the only limitation in WSUS 3.0
is a function of the actual server capacity.
However, if you review the WSUS 3.0 Deployment Guide, you'll find that the
documentation places an arbitrary cap at 20,000 clients, presuming a 64-bit
server farm deployment.
> My question is, if a front end server with a backend SQL is done with 3.0
> does the hardware requirement apply to both servers are is one much more
> important than the other.
The primary hardware constrainst will vary from FE to BE server. For
example, on the BE server, the primary issue is with sufficient RAM to
support caching for the database server.
With the front end server, the primary constraints will be CPU (to handle
the client requests, and the middleware requests and post-processing to the
database), and the disk I/O (to handle file download requests). A secondary
limitation would be RAM, in terms of supporting sufficient filesystem
caching to assist in the disk I/O demands.
> I would prefer that clients and server check in as
> frequent as possible but as I found out in 2.0 it will overfill the
> tbevents
> field leaving your server unfuctional and having to manually clean out the
> table.
This has been fixed in WSUS 3.0 and is no longer a concern.
> We currently have around 4000 pc's and 100 servers. I would like to
> have my servers checkin every one hour and PC's every 3 hours. Does
> anyone
> feel I will have problems with this bogging the WSUS server down or worste
> the clients.
100 servers every hour is 2200 servers once a day, and 4000 PCs every 3
hours is 12,000 pc once a day --- or the equivalent of < 15,000 PCs per
day -- well within the constraints of a single-server deployment on
recommended hardware.
> My front end server is dual 3.0 xeons with 1 gig of ram and a
> back end SQL 2005 server on dual 2.8 xeons with 2 gigs of ram.
Piece of cake. :-)
> I am also
> guessing that the IIS logs will be larger so a bit more space may be
> needed
> on the front end, I also planned to schedule the script to reindex the the
> database every weekend . Any help or insight would be appreciated in
> specing
> out my setup.
You'd have to chat directly with Microsoft as pertains to direct maintenance
of the database, although with the norm being *monthly* distributions of
updates, I highly doubt that weekly reindexing would be a requirement --
perhaps quarterly would be sufficient -- but then if a reindex only takes 10
minutes, why not do it every week! :-)
--
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
.....
|
|
|