Wed, Jan 11 2006 19:47
The black hole of the transition pack
SBS 2003 has a 'transition pack'. A method that you can upgrade from SBS 2003's restrictions to the full fledged products of it's big brother servers...and big brother price tag.....and as SBSers go through this transition pack, invaribly they post in the newsgroup "What's the transition like".
I swear this is a worm hole.... because they ask about it...and never post back.
Well one mortal who has survived in our SBS MVP ranks posted about it and I thought I'd capture it here...from Michael Cocanower of ITsynergy.com
OK, here's what I found.
Installed the Transition pack on SBS SP1 Premium (running SQL but not ISA). It churned for a while and rebooted twice. Note that you are warned all over the place that you'll have to reinstall all service packs after installing the transition pack. Towards the end of the install, I get a message box "Setup cannot continue because the version of Windows on your computer is newer than the version on the CD. Warning: If you decide to delete the newer version of Windows that is currently installed on your computer, the files and settings cannot be recovered. To exit, click Cancel. For more information, click Details. Clicking Details got me nowhere, so I clicked Cancel. I thought I was in trouble, and was ready to call PSS. I rebooted after clicking cancel, and much to my surprise, I get prompted that the transition pack was installed successfully. So now the box is in the "I think the transition pack is applied" state. I moved FSMO roles to another box without a problem (something you're only supposed to be able to do post transition pack). I moved Exchange and SQL each to their own box. I am also now running 2 DHCP servers in the environment, and the old SBS box seems to be stable. I'm not sure what else I can do to confirm that the transition pack is OK, but everything seems to be stable at this point.
To give more background... the transition pack was indeed applied successfully... ...the way you check is attempt to disable license logging serivce and sbscore services. If those two services will shut off and stay off, you don't have a SBS box anymore. In this "no longer a SBS box" state, Remote Web Workplace and all the SBS wizards still work, there are just no guarantees that future patches/service packs will break things.
The 'transititioned' server is now three boxes. Exchange was the snap migration process to a new box. SQL LOB app, also a piece of cake. Sharepoint was the one that needed fixing in permissions, site owners, versions of MSDE and what not. The site to this day is still chugging...OWA running fine along with Remote Web Workplace...and yes the client fully understands that technically while it still is running, [and they use it quite a bit] there are no absolute guarantees that RWW might be broken with some security patch or service pack and it's no longer supported.
If I were in charge of the Universe.. I'd steal RWW...customize it a smidge more...and stick it in Centro.
...now... to go get myself in charge of the Universe... that's the problem...
So... there we go... one 'story of someone who survived the "Black hole of the transition pack" and we've now posted his story.
P.S. For you folks that have commented with issues....can you email me at sbradcpa -at- pacbell.net as I'd love to check with you guys on some points you've raised. When you don't leave an email address, I can't email back directly.
Filed under: SBS Licensing