Re: Upgrade Windows 2000 server to SBS 2003
From: Jeff Middleton [SBS-MVP] (jeff_at_cfisolutions.com)
Date: 02/10/05
- Next message: Dodge: "Re: Patches & updates best practices"
- Previous message: Dirk-Thomas Brown: "Re: cant see domain locally"
- In reply to: SuperGumby [SBS MVP]: "Re: Upgrade Windows 2000 server to SBS 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 10 Feb 2005 14:51:08 -0600
I heard the discussion in the hallway. ;-)
The generic answer is that if the same versions of all the server apps are
already on the server running Windows 2000, and you decided to do an
in-place upgrade to SBS 2003 it would work. The restrictions would be the
normal ones specified by MS for in-place upgrade as blocked conditions.
Those would be for things like Trusts, or if you are running Enterprise
Exchange, or whatever. If all the versions are the same as the SBS 2000
versions, and you don't have any stray connectors to Exchange, then the
in-place would produce the same results as an SBS would. All those products
would be upgraded automatically, except SQL which you have to request to
upgrade or replace or parallel install against.
If you didn't want to in-place upgrade, rather you would prefer a clean
installation, that's where the swing migration process explained at my
website comes in. You could reconstruct a new machine on new hardware, or
redeploy on the same hardware with the SBS 2003 installed clean, but keeping
the same domain, IP, server name, and information store.
The upgrades of the SQL would be handled as a documented, standard SQL
install and then a restore from Enterprise Backup as the most likely answer.
Exchange would allow you to do a forklift of the Information Store if you
follow the guidelines in my documentation in the Swing It!! Kit.
If you have versions of the products that are actually blocked by in-place
upgrades, then the Swing Migration will solve that headache and allow you to
keep the existing domain and accounts, but install the correct SBS version
of the OS that normally can't be addressed by the MS supported upgrade
methods. For instance, if this was an BackOffice 2000 server, MS doesn't
provide a way to do this, but Swing works with a legal method, but it's just
not one of the supported methods MS documents.
If you have any more questions, feel free to post them here.
Jeff Middleton SBS-MVP
YCST@SBSmigration.com
"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:eUKim16DFHA.1936@TK2MSFTNGP14.phx.gbl...
> I've not attempted your scenario but would _expect_ it to be fairly
> painless.
>
> A cautious man could contact Jeff at www.sbsmigration.com and perform a
> Swing It style migration. This would involve 'holding' the AD on a
temporary
> box and doing a clean install of SBS to your existing hardware. The kit
> includes information about maintaining your existing Exchange store but I
> don't think Jeff has put much into SQL (which shouldn't be too complex).
>
>
> "Stelios S" <s_saliaris(-at-)yahoo.gr> wrote in message
> news:ewB9h15DFHA.2632@TK2MSFTNGP12.phx.gbl...
> > Hello,
> > We have a server with windows 2000 server OS(NOT SBS 2000)which we would
> > like to upgrade to SBS 2003.
> > Although, we have found some info about the steps of upgrade, i would
like
> > to ask if there will be a problem with stand-alone exchange 2000, active
> > directory and SQL Server 2000 which are installed in the server at this
> > moment.
> > At this point i would like to mention that server does not have SBS 2000
> > but
> > every software (sql server, exchange) has installed seperately.
> >
> > Have a nice day,
> > Steve
> >
> >
> >
>
>
- Next message: Dodge: "Re: Patches & updates best practices"
- Previous message: Dirk-Thomas Brown: "Re: cant see domain locally"
- In reply to: SuperGumby [SBS MVP]: "Re: Upgrade Windows 2000 server to SBS 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
