Re: WSUS 3.0 WITH SQL 2005

[[ Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]

CarlosA wrote:
> Hi there
>
> I´m working in a wsus design for a little more of 20.000 computer clients,
> I´m planning configure just one wsus server (upstream server) + one
> sql20k5
> server, + 7 replica servers.
> anybody has any valuable recommendation to take in count for my design?
> does
> is truth that any clien need a sql licence?
>
> another question, its acceptable a wsus solution for + 20.000 clients
> working without sql server just working with msde?
>
> I really apreciate your help!
>
> regards,
> CarlosA

> CarlosA wrote:

>> I´m working in a wsus design for a little more of 20.000 computer
>> clients,
>> I´m planning configure just one wsus server (upstream server) + one
>> sql20k5 server, + 7 replica servers.

>> anybody has any valuable recommendation to take in count for my design?

Read the WSUS Deployment Guide. Thoroughly.


>> does is truth that any clien need a sql licence?

Yes. If you're using a full installation of SQL Server (Workgroup, Standard,
Enterprise), then every machine that connects to WSUS requires a SQL Client
Access License.

Another reason to read the Deployment Guide. You may discover that you don't
actually need the full SQL Server, depending on how those 20,000 clients are
spread across your 8 WSUS Servers.


>> another question, its acceptable a wsus solution for + 20.000 clients
>> working without sql server just working with msde?

Another question easily answered by reviewing the Deployment Guide, and
alluded to in my previous comment.

Specifically, a single machine, with appropriate hardware configuration, can
support up to 3000 clients per machine using the Windows Internal Database.
A properly configured 64-bit server can support up to 20,000 clients on a
single machine. There are no limitations on the capabilities of the Windows
Internal Database, so there's no real advantage to installing SQL Server on
the WSUS Server.

The advantage to installing a back-end server is overcoming hardware
limitations, or because the back-end SQL Server already exists and has
unused capacity. (In such cases, quite often, the front-end web server
already exists as well, and WSUS can be deployed into an environment with no
new hardware.)

A back-end server might also be used if clustering is desired -- although
I'm not personally of the opinion that the expense of clustering is a
justifiable deployment for WSUS.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin