wsus 2.0 internal db to wsus 3.0 on separate sql05 db Pete 6/8/2007 4:36:00 PM Hello, Currently my wsus 2.0 is running on local database, I would like to migrate wsus 3.0 to external sql 05 standard db & would like to import all wsus 2.0 existing settings into wsus 3.0. I followed following doc & no success, http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?pf=true, also tried other ways but no luck 2. Did in place upgrade & everything was working ok & I was able to see existing settings, computers. I decided to move the db over to external sql 05, per doc#http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?pf=true, changed following reg entries Find the following key: HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, and in the Value box, type [ServerName]\[InstanceName],and then click OK. If the instance name is the default instance, then simply type [ServerName]. 3. Migration method 3: Move the db from wsus 2.0 to external sql 05, uninstalled wsus 2.0 from server & started 3.0 install, 3.0 did find susdb instance on sql but gave an error that wsus 3.0 was unable to use the db & it can create new db but will overwrite existing data. Can you please point me to a site or give me a suggestion on how I should tackle this problem, thank in advance for reading & answering this post.

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/10/2007 4:55:32 AM "Pete" <Pete[ at ]discussions.microsoft.com> wrote in message news:1935318D-BE85-4F12-B92A-2CE52A2D5857[ at ]microsoft.com... [Quoted Text] > Currently my wsus 2.0 is running on local database, I would like to > migrate > wsus 3.0 to external sql 05 standard db & would like to import all wsus > 2.0 > existing settings into wsus 3.0. I followed following doc & no success, > http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?pf=true, > also tried other ways but no luck > > 2. > Did in place upgrade & everything was working ok & I was able to see > existing settings, computers. I decided to move the db over to external > sql > 05, per > doc#http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?pf=true, > changed following reg entries Okay... four questions: [1] Did the WSUS 2.0 server have WSUS 2.0 =SP1= installed? [2] Which =edition= of SQL Server 2005 did you install on the external SQL server? [3] Do you have SQL Server 2005 =SP1= installed on the external SQL server? > Find the following key: > HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, and in > the > Value box, type [ServerName]\[InstanceName],and then click OK. If the > instance name is the default instance, then simply type [ServerName]. [4] Which of these did you enter in the "SqlServerName" registry value? > 3. Migration method 3: > Move the db from wsus 2.0 to external sql 05, uninstalled wsus 2.0 from > server & started 3.0 install, 3.0 did find susdb instance on sql but gave > an > error that wsus 3.0 was unable to use the db & it can create new db but > will > overwrite existing data. I'm not sure what your point with this paragraph is supposed to be? The only procedures for uninstalling WSUS 2.0 apply to a WSUS 2.0 back-end database server that already exists, running WSUS 2.0. Otherwise, the KB article that you cite requires that: [a] WSUS 2.0 is upgraded to WSUS 3.0 [b] THEN migrate the Windows Internal Database instance database to the back-end SQL Server 2005 instance database. > Can you please point me to a site or give me a suggestion on how I should > tackle this problem, thank in advance for reading & answering this post. I'm not sure what else to tell you. The only 'error' you've described here is from a procedure that's not relevant to your environment. You may be in a situation where your only solutions are: [a] Reinstall WSUS 2.0 SP1 on the original server, and restore the WSUS 2.0 SP1 database, or [b] Install WSUS 3.0 from scratch, configure, synchronize, reapprove updates, and wait for clients to report to completely rebuild the system. -- 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 ..... > > >

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db Pete 6/11/2007 5:22:00 PM Lawrence, Thank you for your response, I am testing this in my test environment. Just to make sure that I didn't miss a step, I had created a image of working wsus 2.0 sp1. I reimaged the server & started from scratch. 1. Installed .net 2.0 on WSUS 2.0 sp1, made sure wsus was reporting computers & updates without any errors. 2. Upgraded WSUS 2.0 sp1 to WSUS 3.0, successfully upgraded & existing info migrated properly on WSUS 3.0 3. Stopped IIS Admin & update service & deattached the db per doc http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?pf=true 4. Copied the folder SUSDB.MDF & SUSDB_log.ldf & pasted in same location on SQL05 sp1 (full standard edition) & attached the db on sql 05 sp1. 5. Modified registry on WSUS 3.0 to point to sql db instance. sql005test\susdb specfied under sqlservername 6. getting error when I launch wsus mmc, Error connection error. Thanks again for your help

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/11/2007 6:40:43 PM "Pete" <Pete[ at ]discussions.microsoft.com> wrote in message news:4489B620-D62E-417B-812B-0520641FBE2A[ at ]microsoft.com... [Quoted Text] > Thank you for your response, I am testing this in my test environment. > Just to make sure that I didn't miss a step, I had created a image of > working wsus 2.0 sp1. I reimaged the server & started from scratch. > 4. Copied the folder SUSDB.MDF & SUSDB_log.ldf & pasted in same location > on > SQL05 sp1 (full standard edition) & attached the db on sql 05 sp1. > 5. Modified registry on WSUS 3.0 to point to sql db instance. > sql005test\susdb specfied under sqlservername *THERE* is your problem! :-) "SUSDB" is the name of the *database*, not the name of the *instance*. If you installed SQL Server 2005 SP1 as the default instance, then, following the documented instructions, you should set the registry value to only the MACHINENAME, (e.g. SQL2005TEST) > 6. getting error when I launch wsus mmc, Error connection error. Because there is no instance name of "SUSDB". :-) >> Find the following key: >> HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, >> and in the Value box, type [ServerName]\[InstanceName],and then click OK. >> If the instance name is the default instance, then simply type >> [ServerName]. -- 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 .....

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db Pete 6/12/2007 1:34:00 PM Lawrence, Thanks again for your feedback I uninstalled sql 05 standard & reinstalled sql05 standard +sp1 & still getting error on wsus mmc. "Lawrence Garvin (MVP)" wrote: [Quoted Text] > > "Pete" <Pete[ at ]discussions.microsoft.com> wrote in message > news:4489B620-D62E-417B-812B-0520641FBE2A[ at ]microsoft.com... > > > Thank you for your response, I am testing this in my test environment. > > Just to make sure that I didn't miss a step, I had created a image of > > working wsus 2.0 sp1. I reimaged the server & started from scratch. > > > 4. Copied the folder SUSDB.MDF & SUSDB_log.ldf & pasted in same location > > on > > SQL05 sp1 (full standard edition) & attached the db on sql 05 sp1. > > > 5. Modified registry on WSUS 3.0 to point to sql db instance. > > sql005test\susdb specfied under sqlservername > > *THERE* is your problem! :-) > > "SUSDB" is the name of the *database*, not the name of the *instance*. > > If you installed SQL Server 2005 SP1 as the default instance, then, > following the documented instructions, you should set the registry value to > only the MACHINENAME, (e.g. SQL2005TEST) > > > 6. getting error when I launch wsus mmc, Error connection error. > > Because there is no instance name of "SUSDB". :-) > > >> Find the following key: > >> HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, > >> and in the Value box, type [ServerName]\[InstanceName],and then click OK. > >> If the instance name is the default instance, then simply type > >> [ServerName]. > > > -- > 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 > ..... > > >

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/13/2007 1:04:55 AM "Pete" <Pete[ at ]discussions.microsoft.com> wrote in message news:C2A167C8-F93A-4881-99FE-7E1D977CEE48[ at ]microsoft.com... [Quoted Text] > I uninstalled sql 05 standard & reinstalled sql05 standard +sp1 & still > getting error on wsus mmc. Okay.. one problem solved. Are you still configuring the registry value as SQL2005TEST\SUSDB <?????> >> > 5. Modified registry on WSUS 3.0 to point to sql db instance. >> > sql005test\susdb specfied under sqlservername >> *THERE* is your problem! :-) >> >> "SUSDB" is the name of the *database*, not the name of the *instance*. >> >> If you installed SQL Server 2005 SP1 as the default instance, then, >> following the documented instructions, you should set the registry value >> to >> only the MACHINENAME, (e.g. SQL2005TEST) >> >> Find the following key: >> >> HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, >> >> and in the Value box, type [ServerName]\[InstanceName],and then click >> >> OK. >> >> If the instance name is the default instance, then simply type >> >> [ServerName]. >> > 6. getting error when I launch wsus mmc, Error connection error. >> Because there is no instance name of "SUSDB". :-) -- 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 .....

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db Pete 6/13/2007 6:14:02 PM Lawrence, Thanks a million for your follow up!!!! I only entered the server name, eg: sql005test & that didn't work. I couldn't even uninstall 3.0 after that so I ended up taking following steps listed below to fix the problem. 1. Had to reimage 3.0 that I couldn't uninstall with wsus 2.0 sp1 image, uninstall 2.0 spq & install fresh copy of 3.0 & point it to external sql db & that worked. I think MS technet doc is missing other reg entries that need to be changed besides servername, I wish I would have exported the registry from 3.0 that failed, that way I could have seen the difference between 2 installs. Next question is it possible to have one sql 05 sp1 serving multiple wsus boxes, none of them will be downstream server, we have fast wan links between sql & wsus servers. Thank you again, "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Pete" <Pete[ at ]discussions.microsoft.com> wrote in message > news:C2A167C8-F93A-4881-99FE-7E1D977CEE48[ at ]microsoft.com... > > > I uninstalled sql 05 standard & reinstalled sql05 standard +sp1 & still > > getting error on wsus mmc. > > Okay.. one problem solved. > > Are you still configuring the registry value as SQL2005TEST\SUSDB <?????> > > > > >> > 5. Modified registry on WSUS 3.0 to point to sql db instance. > >> > sql005test\susdb specfied under sqlservername > > >> *THERE* is your problem! :-) > >> > >> "SUSDB" is the name of the *database*, not the name of the *instance*. > >> > >> If you installed SQL Server 2005 SP1 as the default instance, then, > >> following the documented instructions, you should set the registry value > >> to > >> only the MACHINENAME, (e.g. SQL2005TEST) > > >> >> Find the following key: > >> >> HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, > >> >> and in the Value box, type [ServerName]\[InstanceName],and then click > >> >> OK. > >> >> If the instance name is the default instance, then simply type > >> >> [ServerName]. > > > >> > 6. getting error when I launch wsus mmc, Error connection error. > > >> Because there is no instance name of "SUSDB". :-) > > -- > 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 > ..... > > > >

Re: wsus 2.0 internal db to wsus 3.0 on separate sql05 db "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/14/2007 2:24:00 AM "Pete" <Pete[ at ]discussions.microsoft.com> wrote in message news:3BF63E24-2994-44A2-BDF9-E28B34AF7E5D[ at ]microsoft.com... [Quoted Text] > Next question is it possible to have one sql 05 sp1 serving multiple wsus > boxes, none of them will be downstream server, we have fast wan links > between > sql & wsus servers. No. One *database* per WSUS Server. However.... the real association is one database /INSTANCE/ per server, because the database name is not user configurable. With SQL 2000 this was really an irrelevant point, because you had to have multiple licenses for multiple instances of SQL 2000 on the same server, so the idea of doing that was never really an economically feasable idea. But the licensing for SQL 2005 has changed, and you can now install multiple instances of SQL Server 2005 on the same physical box with just the single-CPU SQL Server 2005 license. The database name is fixed at "SUSDB" (and created by the installer), but the instance name is configurable (and configured when you manually install SQL Server 2005 SP1 as part of the prerequisite installation). So, you could, theoretically, at least, have the following installed instances on the same machine: SQLSERVER\WSUS1 SQLSERVER\WSUS2 SQLSERVER\WSUS3 serving three different WSUS servers. Now... here is why you do *NOT* want to do this? [1] Remote database performance across a WAN link sucks. You'd be better off to use a local (free) installation of the Windows Internal Database on the front-end server, than try to use a remote database server across a WAN link. [2] In order to support multiple instances of SQL Server 2005 on a single server, you need to have sufficient RAM and CPU resources installed (not to mention multiple additional disk drive spindles). Add 2GB (minimum) RAM for each installed database instance, and depending on the client load per WSUS front-end server, another CPU for every 2-3 additional installed instances (not counting the one or two you need for the first instance). This also means you'd need a license for Windows Server 2003 ENTERPRISE Edition, in order to support the necessary RAM for the multiple instances. And, from there, you'd find out pretty quickly that it's cheaper to put a brand new Standard Edition server w/WSUS3 and WID on the remote site, than try to beef up a "Datacenter Server" to support multiple back-ends for several remote front-ends. (Even assuming you were satisfied with the WAN-based performance -- which you won't be.) -- 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 .....