Re: Upgrade Win 2003 Std to Win SBS 2003 Std same box?

Tech-Archive recommends: Fix windows errors by optimizing your registry

I was thinking of the VM not as a migration path but as a continuing
process.

But is OK, you don't like, is OK.

image it, throw SBS CD1 at it.

If the existing server is not yet R2, that's best, do not throw R2 at it
before the upgrade. SBS R2 does not implement all Win2003 R2 features.

"Leythos" <void@xxxxxxxxxxx> wrote in message
news:MPG.214bc65c9563db099898f3@xxxxxxxxxxxxxxxxxxxx
In article <O5QsFRb8HHA.2208@xxxxxxxxxxxxxxxxxxxx>, not@xxxxxxxxxxx
says...
PIFFLE

throw SBS CD1 at it, go for your life.

Leythos knows the conditions of the AD so there's no problem there. SBS
setup will recognise the existing AD. AFAIK the existing AD _could_ even
be
at R2 level without causing issue.

SP level _may_ be a problem. If the server is currrently SP2 you need to
consider that current SBS media is SP1 (AFAIK, no 'slip' SP2 yet). Yeah,
clone it but try to go on top of SP2, if it fails go back to image and
remove SP2, try again.

Also related to R2 is R2 functions implemeneted on the existing server,
if
it is R2. SBS R2 does not support (include?) certain R2 functionality, if
the current server is R2 _and_ has these functions implemented they
_will_
be broken by SBS setup.

The server is Win 2003 Std with all SP and updates, not R2, but, I can
install R2 if needed from the R2 CD. The new SBS 2003 Standard will be
R2, assuming it comes with all SP current as we're buying it next week.

The existing licence being/not OEM is a significant factor in how I would
approach the problem. IF NOT OEM I would probably want to use that
licence
on another box as TS. There is no financial compensation or 'upgrade
path'
in the move so in all cases the licence (as long as it's not OEM) becomes
available for use elsewhere, the _process_ may be an upgrade but no
license
upgrade is performed, the existing Win2003 licence on the server is
_replaced_ by the SBS licence. With this in mind I _may_ be tempted to
move
the licence to another box (VM) through migration and decomission the
existing box, then do SBS as an 'add to existing AD' clean install.

The old server is an OEM (not with server) install of Win 2003, it's
going to be abandoned, along with the CALs and SBS CAL's are being
ordered. This was cheaper than purchasing Exchange 2003 Std and CAL's,
not to mention the Wizards and RWW they get.

Leythos also puts together decent hardware (unless this client argued a
lot). I'd possibly consider using the existing licence (whether OEM or
not)
to run up a 2nd DC in Virtual Server on the existing box, move the AD to
it,
move the real hardware out of a DC state, format it, SBS Setup
interrupted
by VS install to get access to the AD, then 'add SBS to existing AD'.

I actually have 4 Spare Dual Xeon servers we keep for this type of
thing, with large 500GB arrays and 4GB RAM - just for testing/swing.

or HEY, Leythos, this box got enough grunt to run SBS in VS? Leave the
current box intact, 'add SBS to existing AD' in a VM. The process moves
the
FSMO roles, you may or may not want to kep it as a DC, you may or may not
want to use it as a TS while it also hosts SBS in a VM.

If I'm going to swing it, I'll use the spare servers we keep because I
don't like VM at all. I was just wondering if it was possible to insert
the CD's and run an upgrade without going through all of that other
work.


--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)


.

Relevant Pages

  • Re: From NT4 to SBS 2003 - 6 users
    ... do...provided you have an NT 4.0 Server media to use. ... Swing Migration also works around blocks that might affect projects with SBS ... controller to upgrade an NT domain without in-place upgrading an existing NT ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading from NT4 to SBS2003 Premium
    ... we cannot upgrade to SBS Server 2003 from the ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading from NT4 to SBS2003 Premium
    ... > install SBS 2003 on a new hardware; refer to the following white paper to ... > do a migration of the user and computer accounts. ... Migrating from Small Business Server 4.5 or Windows NT ... > an In-Place upgrade. ...
    (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)
  • Re: Upgrading from NT4 to SBS2003 Premium
    ... perform an in-place upgrade to w2k3 Standard Server from the NT4. ... This newsgroup only focuses on SBS technical issues. ... possible to do an In-Place upgrade to w2k3 Standard and then an In-Place ... |> do a migration of the user and computer accounts. ...
    (microsoft.public.windows.server.sbs)