|
|
Hi,
Can someone point out how many clients can the Windows Internal Database
that ships with WSUS server support? Can the Windows Internal Database
supports more than 10000 workstations or do we need to go for Microsoft SQL
Server 2005 (full-featured database)? How many WSUS servers will be
recommended to be installed to handle these workstations (10000)?
I've read the WSUS30DeploymentGuide from Microsoft, however it only gives me
a very general overview.
If you have a good WSUS deployment guide, please let me know. Thanks.
|
|
"bacot" <bacot[ at ]discussions.microsoft.com> wrote in message
news:1DD0624D-8E8D-4FE9-A29F-367468AA4201[ at ]microsoft.com...
[Quoted Text] > Can someone point out how many clients can the Windows Internal Database
> that ships with WSUS server support?
The WSUS3 Deployment Guide doesn't offer any specific database guidelines
(unlike the WSUS2 Deployment Guide, which did), but empirical evidence
showed that the WMSDE was good for about 2,500 clients (give or take,
depending on hardware configuration). The WSUS3/SQL2005 package has been
reported to have a 50% performance improvement, so that suggests that the
WID might be good for as much as 3,500-4,000 clients.
> Can the Windows Internal Database
> supports more than 10000 workstations or do we need to go for Microsoft
> SQL
> Server 2005 (full-featured database)?
For 10,000 clients I'd say not only do you need a full SQL Server 2005
installation, but you really need to split the environment into the
dual-server configuration, with the database on a dedicated back-end
database server. While you could, theoretically, throw enough hardware at a
single-server to support 10,000 client systems, I think you'd find the
dual-server scenario is cheaper, both in terms of hardware and OS licensing
(The dual server environment can run on two Standard Edition servers, or a
Web Edition and Standard Edition. The single-server 10,000 client
environment would absolutely require Enterprise Edition, just to support the
RAM necessary to support IIS and SQL on the same box for that many clients.)
> How many WSUS servers will be
> recommended to be installed to handle these workstations (10000)?
It really depends on the distribution amongst the remote sites and what the
connectivity is to the remote sites. As long as you have more than 5kb/sec
of bandwith per system at each remote site, it's conceivable that a single
dual-server farm in the central office can handle all 10,000 clients.
But, if you have a site with a large number of clients, or a very restricted
connection to the main office, it would be a better solution to put a
replica server on the remote site (or an autonomous downstream server if you
have an onsite WSUS Administrator).
--
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
.....
|
|
Hi Lawrence,
Thanks for the detailed explanation. I just want to further clarify a couple
of issues.
[Quoted Text] > For 10,000 clients I'd say not only do you need a full SQL Server 2005
> installation, but you really need to split the environment into the
> dual-server configuration, with the database on a dedicated back-end
> database server. While you could, theoretically, throw enough hardware at a
> single-server to support 10,000 client systems, I think you'd find the
> dual-server scenario is cheaper, both in terms of hardware and OS licensing
> (The dual server environment can run on two Standard Edition servers, or a
> Web Edition and Standard Edition. The single-server 10,000 client
> environment would absolutely require Enterprise Edition, just to support the
> RAM necessary to support IIS and SQL on the same box for that many clients.)
Does it mean we have to setup a NLB SQL server? Or do you mean setting up 2
- single processor WSUS servers that act as the front end servers which
connect to a server that has Microsoft SQL server 2005 installed on it.
"Lawrence Garvin (MVP)" wrote:
> "bacot" <bacot[ at ]discussions.microsoft.com> wrote in message
> news:1DD0624D-8E8D-4FE9-A29F-367468AA4201[ at ]microsoft.com...
>
> > Can someone point out how many clients can the Windows Internal Database
> > that ships with WSUS server support?
>
> The WSUS3 Deployment Guide doesn't offer any specific database guidelines
> (unlike the WSUS2 Deployment Guide, which did), but empirical evidence
> showed that the WMSDE was good for about 2,500 clients (give or take,
> depending on hardware configuration). The WSUS3/SQL2005 package has been
> reported to have a 50% performance improvement, so that suggests that the
> WID might be good for as much as 3,500-4,000 clients.
>
> > Can the Windows Internal Database
> > supports more than 10000 workstations or do we need to go for Microsoft
> > SQL
> > Server 2005 (full-featured database)?
>
> For 10,000 clients I'd say not only do you need a full SQL Server 2005
> installation, but you really need to split the environment into the
> dual-server configuration, with the database on a dedicated back-end
> database server. While you could, theoretically, throw enough hardware at a
> single-server to support 10,000 client systems, I think you'd find the
> dual-server scenario is cheaper, both in terms of hardware and OS licensing
> (The dual server environment can run on two Standard Edition servers, or a
> Web Edition and Standard Edition. The single-server 10,000 client
> environment would absolutely require Enterprise Edition, just to support the
> RAM necessary to support IIS and SQL on the same box for that many clients.)
>
> > How many WSUS servers will be
> > recommended to be installed to handle these workstations (10000)?
>
> It really depends on the distribution amongst the remote sites and what the
> connectivity is to the remote sites. As long as you have more than 5kb/sec
> of bandwith per system at each remote site, it's conceivable that a single
> dual-server farm in the central office can handle all 10,000 clients.
>
> But, if you have a site with a large number of clients, or a very restricted
> connection to the main office, it would be a better solution to put a
> replica server on the remote site (or an autonomous downstream server if you
> have an onsite WSUS Administrator).
>
>
> --
> 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
> .....
>
>
>
|
|
"bacot" <bacot[ at ]discussions.microsoft.com> wrote in message
news:649A2EE1-C4EA-473B-9132-8853B0FAC5AA[ at ]microsoft.com...
[Quoted Text] >> For 10,000 clients I'd say not only do you need a full SQL Server 2005
>> installation, but you really need to split the environment into the
>> dual-server configuration, with the database on a dedicated back-end
>> database server. While you could, theoretically, throw enough hardware at
>> a
>> single-server to support 10,000 client systems, I think you'd find the
>> dual-server scenario is cheaper, both in terms of hardware and OS
>> licensing
>> (The dual server environment can run on two Standard Edition servers, or
>> a
>> Web Edition and Standard Edition. The single-server 10,000 client
>> environment would absolutely require Enterprise Edition, just to support
>> the
>> RAM necessary to support IIS and SQL on the same box for that many
>> clients.)
> Does it mean we have to setup a NLB SQL server?
Absolutely not!
> Or do you mean setting up 2
> - single processor WSUS servers that act as the front end servers which
> connect to a server that has Microsoft SQL server 2005 installed on it.
Nor did I mean that.
I meant a single front-end web server, and a single back-end database
server. Two servers, both Standard Edition, 2GB RAM, dual-core processors,
and appropriately configured disk subsystems (RAID 1 on the web server for
~\inetput and the ~\WSUSContent folders; RAID 10 on the database 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
.....
|
|
Hi Lawrence, Thanks for the reply.
So, you are saying that 1 WSUS server should be enough to handle the
requirement as long as we are using SQL server 2005?
Do you have a detailed documentation on how to setup the WSUS + SQL server
2005. Sorry if I annoy you. This will be my first time setting the WSUS
server on SQL server 2005.
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "bacot" <bacot[ at ]discussions.microsoft.com> wrote in message > news:649A2EE1-C4EA-473B-9132-8853B0FAC5AA[ at ]microsoft.com... > > >> For 10,000 clients I'd say not only do you need a full SQL Server 2005 > >> installation, but you really need to split the environment into the > >> dual-server configuration, with the database on a dedicated back-end > >> database server. While you could, theoretically, throw enough hardware at > >> a > >> single-server to support 10,000 client systems, I think you'd find the > >> dual-server scenario is cheaper, both in terms of hardware and OS > >> licensing > >> (The dual server environment can run on two Standard Edition servers, or > >> a > >> Web Edition and Standard Edition. The single-server 10,000 client > >> environment would absolutely require Enterprise Edition, just to support > >> the > >> RAM necessary to support IIS and SQL on the same box for that many > >> clients.) > > > Does it mean we have to setup a NLB SQL server? > > Absolutely not! > > > Or do you mean setting up 2 > > - single processor WSUS servers that act as the front end servers which > > connect to a server that has Microsoft SQL server 2005 installed on it. > > Nor did I mean that. > > I meant a single front-end web server, and a single back-end database > server. Two servers, both Standard Edition, 2GB RAM, dual-core processors, > and appropriately configured disk subsystems (RAID 1 on the web server for > ~\inetput and the ~\WSUSContent folders; RAID 10 on the database 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> ..... > > > |
|
"bacot" <bacot[ at ]discussions.microsoft.com> wrote in message
news:23FE23F4-CB28-40D0-8FE2-F6363B1A3064[ at ]microsoft.com...
[Quoted Text] > Hi Lawrence, Thanks for the reply.
>
> So, you are saying that 1 WSUS server should be enough to handle the
> requirement as long as we are using SQL server 2005?
Yes, but more specifically, as long as the SQL Server 2005 is installed on a
dedicated database server (not the WSUS front-end web server).
(And, as long as the hardware configuration meets the minimum requirements
for a 10,000 client environment)
> Do you have a detailed documentation on how to setup the WSUS + SQL server
> 2005. Sorry if I annoy you. This will be my first time setting the WSUS
> server on SQL server 2005.
Detailed documentation can be found in the WSUS Deployment Guide, available
at:
http://go.microsoft.com/fwlink/?linkid=79983
--
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
.....
|
|
Hi Lawrence,
[Quoted Text] > Yes, but more specifically, as long as the SQL Server 2005 is installed on a
> dedicated database server (not the WSUS front-end web server).
If we have a SQL database that runs SQL server 2005. Can we use this shared
server to create an instance for the WSUS server. Do you think we should have
a server that is only dedicated for the WSUS database and no other instances
should be installed on this server?
Do you have any hardware recommendation (spec wise) for the front end web
server?
"Lawrence Garvin (MVP)" wrote:
> "bacot" <bacot[ at ]discussions.microsoft.com> wrote in message
> news:23FE23F4-CB28-40D0-8FE2-F6363B1A3064[ at ]microsoft.com...
> > Hi Lawrence, Thanks for the reply.
> >
> > So, you are saying that 1 WSUS server should be enough to handle the
> > requirement as long as we are using SQL server 2005?
>
> Yes, but more specifically, as long as the SQL Server 2005 is installed on a
> dedicated database server (not the WSUS front-end web server).
>
> (And, as long as the hardware configuration meets the minimum requirements
> for a 10,000 client environment)
>
> > Do you have a detailed documentation on how to setup the WSUS + SQL server
> > 2005. Sorry if I annoy you. This will be my first time setting the WSUS
> > server on SQL server 2005.
>
> Detailed documentation can be found in the WSUS Deployment Guide, available
> at:
> http://go.microsoft.com/fwlink/?linkid=79983
>
> --
> 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
> .....
>
>
>
>
|
|
"bacot" <bacot[ at ]discussions.microsoft.com> wrote in message
news:1C7A0EFD-0145-4B1D-B74F-B75F03B70CAF[ at ]microsoft.com...
[Quoted Text] >> Yes, but more specifically, as long as the SQL Server 2005 is installed
>> on a
>> dedicated database server (not the WSUS front-end web server).
> If we have a SQL database that runs SQL server 2005. Can we use this
> shared
> server to create an instance for the WSUS server.
Absolutely!
> Do you think we should have
> a server that is only dedicated for the WSUS database and no other
> instances
> should be installed on this server?
No... that's not likely necessary. But your DBA should be consulted on the
expected load brought by WSUS and ensure that the database server has
sufficient resources to handle the load from the additional database.
> Do you have any hardware recommendation (spec wise) for the front end web
> server?
Minimum hardware specifications are documented in the WSUS Deployment Guide.
--
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
.....
|
|
|