|
|
Hi,
At the moment we have a dedicated WSUS 2 server also running SQL Server 2000
on it our WSUS DB Sits on the SQL server and is 1.6gig in size, there is also
about another 15 DB's sat on this SQL Server.
I'm currently running WSUS 3 in our test environment pushing out updates to
20 workstations and 4 servers, this is not at all a true reflection of the
live environment we will be running though.
My question is this...
Our network consists of 275 sites, at least 1 DC on each site and 6000+
client PC's for arguments sake we'll say 6,500 units will be receiving
updates from this one server. At the moment we are deciding whether to
upgrade to SQL Server 2005 or to use Windows Internal Database, at the moment
WID is looking favourable as it requires the least ammount of work and the
least ammount of cost. Will WID handle our configuration without any
problems or is it worth upgrading to SQL Server 2005?
|
|
"Adam Johnson" <Adam Johnson[ at ]discussions.microsoft.com> wrote in message
news:2CBC6B2D-3AFC-4219-983F-B0BF44E38D9F[ at ]microsoft.com...
[Quoted Text] > At the moment we have a dedicated WSUS 2 server also running SQL Server
> 2000
> on it our WSUS DB Sits on the SQL server and is 1.6gig in size, there is
> also
> about another 15 DB's sat on this SQL Server.
> I'm currently running WSUS 3 in our test environment pushing out updates
> to
> 20 workstations and 4 servers, this is not at all a true reflection of the
> live environment we will be running though.
>
> My question is this...
>
> Our network consists of 275 sites, at least 1 DC on each site and 6000+
> client PC's for arguments sake we'll say 6,500 units will be receiving
> updates from this one server. At the moment we are deciding whether to
> upgrade to SQL Server 2005 or to use Windows Internal Database, at the
> moment
> WID is looking favourable as it requires the least ammount of work and the
> least ammount of cost. Will WID handle our configuration without any
> problems or is it worth upgrading to SQL Server 2005?
WID will handle (based on my educated extrapolations, which are based on
empirical performance results on WMSDE) about 4,000 clients on appropriately
configured (and dedicated to WSUS) hardware. That would suggest that you'd
need at least two WSUS servers in your environment.
The other key to supporting remote clients is the available bandwidth from
the client, across the WAN, to the WSUS Server. A WSUS environment requires
about 5kbit/sec of bandwidth per PC to function in a remote environment. If
you envision distributing service packs via WSUS, then you'd probably want
10kbit/sec per PC -- or at least a burstable package that would give you
10kbit/sec, if/when needed.
Given that you have 275 sites, I don't really think you want to deploy 275
remote WSUS servers (given that you already have the server platforms
deployed), although doing so would ensure you could use WIS for all client
systems. Probably a more practical arrangement would be a few remote
servers, configured to handle approx 1,000 remote clients each -- if you
intended to deploy the WSUS servers to remote locations.
Where the servers are located really isn't that significant, except with
regards to the available bandwidth, and you may find it's more practical to
deploy three or four WSUS servers in your central office, albeit assigned to
maintain remote PCs. You might split them up by platform, by language, or by
geographic region. Depending on how many of those 6,500 units are in the
local LAN, you might only need two servers. One for local access, and one
for remote systems.
Upgrading your SQL 2000 to SQL 2005 (which, btw, you *need* to do anyway,
forget about the WSUS decision which should be a trivial reason in that
discussion!), would allow you to continue supporting all 6500 units on one
front-end server. (If I'm reading your description correctly, and you're
running IIS for WSUS on the SQL Server, which is also supporting 15 other
databases, then you really do need to move the IIS to a separate front-end
server and let the database server be a dedicated database server. The
memory and CPU requirements of IIS and ASP.NET, are negatively impacting
your database performance on all databases.)
--
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
.....
|
|
|