Prev: Remote Desktop Credentials for Vista
Next: Reinstall WSUS - Missing Instance SERVER\MICROSOFT##SSEE
From: rondmc on 21 Dec 2007 10:45 I am about to apply the transition pack to my SBS R2 Standard server. My server has service pack 2 applied but the transition media has service pack 1 integrated. Would it be best for me to slipstream service pack 2 to the transition pack first?
From: Charlie Russel - MVP on 21 Dec 2007 14:08 I'm not sure how well slipstreaming would work, though you could try it. I'd be more inclined to roll back SP2, do the transition, then re-apply the Server 2k3 SP2 after the transition is complete. Also, FWIW, my standard suggestions on the transition pack installation: Before you run the Transition Pack there are a few steps you should take to ensure a smooth transition: 1.) Do a thorough, complete, VERIFIED backup. If it isn't verified and tested, it isn't a backup, IMHO. 2.) Clean up your HD. Remove temporary files, old logs, and so forth. Run Disk Cleanup (cleanmgr.exe) 3.) Defragment the HD. Use the built in, or use a good third party such as PerfectDisk from Raxco. 4.) Disconnect the server from the internet completely. (Easiest way is just unplug the network from the back of the server.) 5.) Stop any third party services that are running as a system account and set them to disabled or uninstall them. This includes AV, disk utilities, and any real-time monitoring programs. 6.) Remove Veritas BackupExec (see KB: 914990) 7.) Run regedit and check for the presence of the key: HKLM\Software\Microsoft\Small Business. If it exists, remove it. That's it. Just make sure you have the matching TP version to your SBS version. (ie, SP1 for SP1 SBS, etc.) Also, make sure you have media kits available for your individual server software packages. You shouldn't need them, but it's good to have, just in case. Finally, just run the transition. Expect it to take 2+ hours, and 7 or more reboots. Even if you give it the logon password, you may get prompted the first reboot - I did in 4 of 7 transitions I did last spring. No discernable pattern to it. Once that first one completes, though, you can go grab some lunch/dinner/whatever and it should run by itself. -- Charlie. http://msmvps.com/xperts64 http://mvp.support.microsoft.com/profile/charlie.russel "rondmc" <rondmc(a)discussions.microsoft.com> wrote in message news:DCDFA617-D1A3-4CD6-B8FC-89CB8CB9D715(a)microsoft.com... >I am about to apply the transition pack to my SBS R2 Standard server. My > server has service pack 2 applied but the transition media has service > pack 1 > integrated. Would it be best for me to slipstream service pack 2 to the > transition pack first?
From: rondmc on 21 Dec 2007 17:43 "Charlie Russel - MVP" wrote: > I'm not sure how well slipstreaming would work, though you could try it. I'd > be more inclined to roll back SP2, do the transition, then re-apply the > Server 2k3 SP2 after the transition is complete. Do you think slipstreaming might break the transition pack? > > Also, FWIW, my standard suggestions on the transition pack installation: > > Before you run the Transition Pack there are a few steps you should take to > ensure a smooth transition: > > 1.) Do a thorough, complete, VERIFIED backup. If it isn't verified and > tested, it isn't a backup, IMHO. I agree! > 2.) Clean up your HD. Remove temporary files, old logs, and so forth. Run > Disk Cleanup (cleanmgr.exe) Done. > 3.) Defragment the HD. Use the built in, or use a good third party such as > PerfectDisk from Raxco. The built didn't do very well. Thanks for the Raxo tip! I'll give it a try. > 4.) Disconnect the server from the internet completely. (Easiest way is just > unplug the network from the back of the server.) OK > 5.) Stop any third party services that are running as a system account and > set them to disabled or uninstall them. This includes AV, disk utilities, > and any real-time monitoring programs. OK. > 6.) Remove Veritas BackupExec (see KB: 914990) I use Acronis. > 7.) Run regedit and check for the presence of the key: > HKLM\Software\Microsoft\Small Business. If it exists, remove it. Its a gonner. > That's it. Just make sure you have the matching TP version to your SBS > version. (ie, SP1 for SP1 SBS, etc.) Yep, except for SP 2 applied to the server. > Also, make sure you have media kits available for your individual server > software packages. You shouldn't need them, but it's good to have, just in > case. Got them. > Finally, just run the transition. Expect it to take 2+ hours, and 7 or more > reboots. Even if you give it the logon password, you may get prompted the > first reboot - I did in 4 of 7 transitions I did last spring. No discernable > pattern to it. Once that first one completes, though, you can go grab some > lunch/dinner/whatever and it should run by itself. Thanks for the tips. If I try slipstreaming I will let you know how it works out.
From: Charlie Russel - MVP on 22 Dec 2007 01:27 Well, yes, actually, I'm afraid it might. It's not a scenario I ever tried and I'm extremely reluctant to suggest you go ahead with it. If it doesn't work, you're very likely to be in an indeterminant state that's very hard to get out of. Thus my suggestion to do it the annoying way and role back SP2. -- Charlie. http://msmvps.com/xperts64 http://mvp.support.microsoft.com/profile/charlie.russel "rondmc" <rondmc(a)discussions.microsoft.com> wrote in message news:489D2B6B-A762-43DF-9EB9-B61079C19748(a)microsoft.com... > > > "Charlie Russel - MVP" wrote: > >> I'm not sure how well slipstreaming would work, though you could try it. >> I'd >> be more inclined to roll back SP2, do the transition, then re-apply the >> Server 2k3 SP2 after the transition is complete. > > Do you think slipstreaming might break the transition pack? > > >> >> Also, FWIW, my standard suggestions on the transition pack installation: >> >> Before you run the Transition Pack there are a few steps you should take >> to >> ensure a smooth transition: >> >> 1.) Do a thorough, complete, VERIFIED backup. If it isn't verified and >> tested, it isn't a backup, IMHO. > > I agree! > >> 2.) Clean up your HD. Remove temporary files, old logs, and so forth. Run >> Disk Cleanup (cleanmgr.exe) > > Done. > >> 3.) Defragment the HD. Use the built in, or use a good third party such >> as >> PerfectDisk from Raxco. > > The built didn't do very well. Thanks for the Raxo tip! I'll give it a > try. > >> 4.) Disconnect the server from the internet completely. (Easiest way is >> just >> unplug the network from the back of the server.) > > OK > >> 5.) Stop any third party services that are running as a system account >> and >> set them to disabled or uninstall them. This includes AV, disk utilities, >> and any real-time monitoring programs. > > OK. > >> 6.) Remove Veritas BackupExec (see KB: 914990) > > I use Acronis. > > >> 7.) Run regedit and check for the presence of the key: >> HKLM\Software\Microsoft\Small Business. If it exists, remove it. > > > Its a gonner. > > >> That's it. Just make sure you have the matching TP version to your SBS >> version. (ie, SP1 for SP1 SBS, etc.) > > > Yep, except for SP 2 applied to the server. > >> Also, make sure you have media kits available for your individual server >> software packages. You shouldn't need them, but it's good to have, just >> in >> case. > > Got them. > > >> Finally, just run the transition. Expect it to take 2+ hours, and 7 or >> more >> reboots. Even if you give it the logon password, you may get prompted the >> first reboot - I did in 4 of 7 transitions I did last spring. No >> discernable >> pattern to it. Once that first one completes, though, you can go grab >> some >> lunch/dinner/whatever and it should run by itself. > > > Thanks for the tips. If I try slipstreaming I will let you know how it > works out. >
From: Merv Porter [SBS-MVP] on 22 Dec 2007 07:45 This link seems to support what you're saying Charlie. (match the service packs between the TP CD and the SBS server before you start the process). What to do before installing the Transition Pack http://blogs.technet.com/sbs/archive/2006/01/12/417350.aspx ------------------------------------------------- 7-Make sure you are using the Windows Small Business Server 2003 with SP1 Transition Pack if you have installed Windows 2003 Service Pack 1 on your SBS 2003 server. You want to make sure that the service pack matches before starting up the process. Basically, try to avoid mixing the versions. If you have Transition Pack media that does NOT include Service Pack 1, then make sure you are upgrading an SBS server that does NOT have Windows 2003 Service Pack 1 installed. ------------------------------------------------- -- Merv Porter [SBS-MVP] ============================ "Charlie Russel - MVP" <charlie(a)mvKILLALLSPAMMERSps.org> wrote in message news:26A95623-3A37-460B-9C0D-A8CE6CB1C425(a)microsoft.com... > Well, yes, actually, I'm afraid it might. It's not a scenario I ever tried > and I'm extremely reluctant to suggest you go ahead with it. If it doesn't > work, you're very likely to be in an indeterminant state that's very hard > to > get out of. Thus my suggestion to do it the annoying way and role back > SP2. > > > -- > Charlie. > http://msmvps.com/xperts64 > http://mvp.support.microsoft.com/profile/charlie.russel > > > "rondmc" <rondmc(a)discussions.microsoft.com> wrote in message > news:489D2B6B-A762-43DF-9EB9-B61079C19748(a)microsoft.com... >> >> >> "Charlie Russel - MVP" wrote: >> >>> I'm not sure how well slipstreaming would work, though you could try it. >>> I'd >>> be more inclined to roll back SP2, do the transition, then re-apply the >>> Server 2k3 SP2 after the transition is complete. >> >> Do you think slipstreaming might break the transition pack? >> >> >>> >>> Also, FWIW, my standard suggestions on the transition pack installation: >>> >>> Before you run the Transition Pack there are a few steps you should take >>> to >>> ensure a smooth transition: >>> >>> 1.) Do a thorough, complete, VERIFIED backup. If it isn't verified and >>> tested, it isn't a backup, IMHO. >> >> I agree! >> >>> 2.) Clean up your HD. Remove temporary files, old logs, and so forth. >>> Run >>> Disk Cleanup (cleanmgr.exe) >> >> Done. >> >>> 3.) Defragment the HD. Use the built in, or use a good third party such >>> as >>> PerfectDisk from Raxco. >> >> The built didn't do very well. Thanks for the Raxo tip! I'll give it a >> try. >> >>> 4.) Disconnect the server from the internet completely. (Easiest way is >>> just >>> unplug the network from the back of the server.) >> >> OK >> >>> 5.) Stop any third party services that are running as a system account >>> and >>> set them to disabled or uninstall them. This includes AV, disk >>> utilities, >>> and any real-time monitoring programs. >> >> OK. >> >>> 6.) Remove Veritas BackupExec (see KB: 914990) >> >> I use Acronis. >> >> >>> 7.) Run regedit and check for the presence of the key: >>> HKLM\Software\Microsoft\Small Business. If it exists, remove it. >> >> >> Its a gonner. >> >> >>> That's it. Just make sure you have the matching TP version to your SBS >>> version. (ie, SP1 for SP1 SBS, etc.) >> >> >> Yep, except for SP 2 applied to the server. >> >>> Also, make sure you have media kits available for your individual server >>> software packages. You shouldn't need them, but it's good to have, just >>> in >>> case. >> >> Got them. >> >> >>> Finally, just run the transition. Expect it to take 2+ hours, and 7 or >>> more >>> reboots. Even if you give it the logon password, you may get prompted >>> the >>> first reboot - I did in 4 of 7 transitions I did last spring. No >>> discernable >>> pattern to it. Once that first one completes, though, you can go grab >>> some >>> lunch/dinner/whatever and it should run by itself. >> >> >> Thanks for the tips. If I try slipstreaming I will let you know how it >> works out. >> >
|
Next
|
Last
Pages: 1 2 Prev: Remote Desktop Credentials for Vista Next: Reinstall WSUS - Missing Instance SERVER\MICROSOFT##SSEE |