Re: upgrade from 2003 STD to server 2003 SBS Std

Swing It! is documentation of a process.

The basics.
You install a DC that takes a copy of the AD, this is your 'swing' server.
You then disconnect this from the original AD and install the new box into
this 'offline copy' using the name of the original server. To do so the AD
needs to have references to the original server removed. This is done
primarily to lessen work at the workstations, you recreate your UNC paths
from the old box on the new, Exchange ends up having the same name as the
original Exchange, etc... At changeover time you shut down the old server,
disconnect it from the network, plug in the new and fire it up. As the AD
(ie. the domain SID) and server name have been preserved the workstations
sortta don't recognise the server as having been changed.

The process is a compendium of MS KB articles and 'normal' AD procedures so
the end product is fully supportable as a 'normal' system.

Many suggest Jeff's support of the project, which comes as part of the kit,
alone justifies the cost.

HOWEVER, I've just quickly skimmed your original and other posts to the
thread. Swing may not be necessary in your case. I'm guessing the origin
server has Windows Server SP2, and possibly Windows Server R2 components,
installed and AFAIK the SBS media you are attempting to use for 'inplace
upgrade' is SP1, you might try removing SP2 (and R2, and any post-SP1
hotfixes) then attempt your upgrade. Also consider that though there is an
'R2' in SBS we only get some parts of it.

CAUTION: I _would_ Swing the AD, it's a much cleaner way of doing what you
want. I offer the suggestion only because it is a viable option, or at least
worth trying. You would also be performing a 'swing to same hardware' which
in best manner requires formatting the OS partition, and therefore
reinstallation of your apps that you indicate took substantial time. I
cannot guess as to what the apps are and probably couldn't comment on the
effect 'inplace upgrade' is going to have even if you named them.

"Bernard Parrett" <bernard@xxxxxxxxxxxxxx> wrote in message
news:ezwAsMwOIHA.4752@xxxxxxxxxxxxxxxxxxxxxxx
Justin Brown - SYNACS wrote:
On Dec 9, 10:35 pm, Bernard Si-Tech <Bernard Si-
T...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
As soon as I start the upgrade, I get "unable to access active
directory",
if I demote the directory service I loose the users and their settings.
I am trying to upgrade as I only have 1 server (HP proliant server )
if I remove the directory and users the upgrade process tells me that my
Os
is newer than the CD I am using.
This is a new CD just purchased

I believe that Server 2003 Standard -> SBS 2003 Standard (R2 or not)
is not a supported upgrade path. Technically you're not upgrading the
OS, what you're doing is along the lines of a migration. Assuming
you've done your homework and you're in good shape on the licensing
end (I definitely recommend a consultation on that), it is certainly
possible to migrate your existing domain to SBS. However it's not as
easy as you're probably thinking it is.

Here is some very worthy guidance you might consider to protect your
existing infrastructure, along with your recent purchase:

Jeff Middleton's "Swing It!! Technician Kit"
http://www.sbsmigration.com/pages/96/

Is this swingit a Product (software) or documentation.

Regards
Bernard


.

Relevant Pages

  • Defect in installer for Antivirus Corp Ed 9.0.1.1000 when upgrading from 9.0.0.x
    ... antivirus solution and have Windows XP desktops you'd like to upgrade to XP ... SP2 and wish to have the most recent build of SAV 9 that is XP SP2 compatible. ... to install to servers & PCs to provide XP SP 2 compatibility. ... Once you upgrade your Primary Server to 9.0.1.1000 and attempt to ...
    (NT-Bugtraq)
  • Re: 2008 or 2003
    ... To install a 2008 DC in a 2003 domain the schema has to be upgraded to version 44. ... The schema is the same in your complete domain, the schema upgrade will add additional AD objects which are needed for 2008. ... 2008 ad schema instead of setting it up as a 2003 AD server I need all ...
    (microsoft.public.windows.server.setup)
  • RE: DNS Question on NT4 to AD upgrade
    ... With the dell you can install NT4.0 it is just is not supported by dell. ... Then perform your upgrade on the NT 4.0 Machine although this ... pointing to the new WINS server on the first dhcp scope. ...
    (microsoft.public.win2000.active_directory)
  • Re: Exchange SP1 stopped all smtp traffic
    ... Cannot upgrade virtual server http://stargate:80. ... al server to a new virtual server extended with Windows SharePoint Services. ... Installation fails and mail flow stops when you install Exchange Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003/NT4 migration - Trust issue?
    ... Introduced SBS into the existing AD. ... I am having a problem with an SBS 2003 upgrade. ... Install temporary NT4 server on spare hardware, ...
    (microsoft.public.windows.server.sbs)