|
|
I've the following setup.
a) a master wsus2.0 on a win2003 sp2, internal database is susdb (not sql
server)
b) a replica wsus2.0 on a win2003 sp2, internal database is susdb (not sql
server)
Both are running fine.
1. Can i upgrade the master wsus first ? And LATER time, upgrade the replica
?
2. Can i continue to retain using internal windows database, rather than sql
2005 ?
3. Can i AFTER upgraded (a), (b), then change database to SQL 2005 ?
|
|
You will HAVE TO upgrade the master server first. WSUS 2 can report to a WSUS
3 master but not the other way around.
You can continue to use the built in DB for now but I'm not sure if moving
to SQL2005 later will be an a straight update or if you'll need to do a more
involved upgrade of the database.
hope this helps
KIV
"IT Staff" wrote:
[Quoted Text] > I've the following setup.
>
> a) a master wsus2.0 on a win2003 sp2, internal database is susdb (not sql
> server)
> b) a replica wsus2.0 on a win2003 sp2, internal database is susdb (not sql
> server)
>
> Both are running fine.
>
> 1. Can i upgrade the master wsus first ? And LATER time, upgrade the replica
> ?
> 2. Can i continue to retain using internal windows database, rather than sql
> 2005 ?
> 3. Can i AFTER upgraded (a), (b), then change database to SQL 2005 ?
>
>
>
>
>
|
|
"IT Staff" <jkklim[ at ]hotmail.com> wrote in message
news:ej$XjurwHHA.840[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > I've the following setup.
>
> a) a master wsus2.0 on a win2003 sp2, internal database is susdb (not sql
> server)
> b) a replica wsus2.0 on a win2003 sp2, internal database is susdb (not sql
> server)
Okay.. first thing we need to clarify is the difference between the
*database* and the *server*. SUSDB is the name of the *database*. That
database will exist in every possible configuration of WSUS 2.0. The
*servers* that you have would be:
[a] MSDE2000 on Windows 2000 or Windows Server 2003, Web Edition.
[b] WMSDE on Windows Server 2003, Standard or Enterprise Edition.
[c] SQL Server 2000
[d] SQL Server 2005.
A server can have gazillions of databases, one of which would be the WSUS
database named "SUSDB".
> 1. Can i upgrade the master wsus first ? And LATER time, upgrade the
> replica ?
As noted by Kiv, you *must* upgrade the master first.
> 2. Can i continue to retain using internal windows database, rather than
> sql 2005 ?
By default WSUS 3 will install the Windows Internal Database unless SQL
Server 2005 is already installed and in use by WSUS 2.
> 3. Can i AFTER upgraded (a), (b), then change database to SQL 2005 ?
Yes, you can, but it's a pain in the neck. I just went through migrating
from WID to SQL 2005, exactly as documented in the WSUS 3 documentation, and
there are some weak links in the documentation. I'm lobbying to get them
remediated. If I'm unsuccessful with that, I may 'rewrite' the procedure and
post it on my website.
My best suggestion is to pick your database environment from the start, and
deploy the upgrade/migration appropriately to serve that database.
Also keep in mind that using SQL 2005 has CAL requirements that you may not
actually possess. This is a significant expense, so unless you're needing to
put several thousand clients on a single WSUS server, and you've got the
budget for tens of thousands of dollars of licensing fees (or already have
the SQL CALs), you'll likely find that SQL 2005 is not a viable solution.
Practically speaking, you can deploy three or four individual WSUS 3 servers
using the Windows Internal Database, serving 2,500 clients on each server
for less money than it would take to deploy a back-end database solution for
10,000 clients.
--
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://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|