Re: Migration
From: SuperGumby [SBS MVP] (not_at_your.nellie)
Date: 02/17/04
- Next message: SuperGumby [SBS MVP]: "Re: Setup Xerox Network Printer"
- Previous message: Dashe: "Re: OWA"
- In reply to: lion: "Re: Migration"
- Next in thread: lion: "RE: Migration"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 17 Feb 2004 22:31:19 +1100
yeah, but in a thousand years they'll all get confused when googling your
posts.
enough frivolity.
Though you intend implementing new hardware I'm gonna ask if the old box
would support upgrade to SBS2K3? WHY? Because upgrading it should be fairly
simple and IME taking the HDD's out of that system after the upgrade and
throwing them into the new box is _likely_ to be _not too complicated_. This
would retain your existing AD (domain, users, pc's) and also satisfy two
important criteria.
1) MS support upgrading SBS2K to SBS2K3.
2) MS support moving an existing SBS2K3 system to new hardware. (I think)
before attempting this you want to ensure you have a decent way of 'rolling
back' in case the upgrade or move fail.
otherwise you are looking at the MS supported (notice how that concept keeps
arising) 'migration' method where the new AD will have both a new server
NETBIOS name and a new AD name (both NETBIOS and DNS). This is likely to
result in delays during the opening of Office documents which have nothing
to do with SMB signing.
To the best of my knowledge if this scenario fails you have 14 days to fix
it or you need to rollback not only the server but all the client PC's.
Another method is the TOTALLY NON MS method of 'sparebox' migration which
results in the SBS2K3 having the same NETBIOS and AD names as the original
SBS2K. It's not easy and I don't have several days (I'm a slow typist) to
describe it, it's advantages and pitfalls. Your Office documents shouldn't
have a problem but from MS' view it is 'unsupported' (isn't that an ugly
head popping up again?).
If the final stages of this fail and you fail to connect one of the existing
client PC's to the domain you turn the new server off, turn the old one back
on and start from square one again. Googling both this and the SBS2K group
will give you a lot of the concept.
-- Mick Malloy http://www.micropol.com.au "lion" <anonymous@discussions.microsoft.com> wrote in message news:8FE29281-BC08-410A-BEF1-A36598C607D9@microsoft.com... > I know w3k is far away, but ... idont feel like typing 2003.2003.... so we will have to use our imagination. > Yes im planning to swap out the w2k with W3K.. Those 3 questions are the only doubts i have. I know the microsoft way is usually the right way but can complicate things, as usuall. What are the ways you have in mind. Iether way i have to migrate the users and exchange mailboxes...VITAL. I know exchange is extremely fussy with the DB and AD. Ive banged my head so many times with this. So migrating seems the safest way. I think. Any Ideas
- Next message: SuperGumby [SBS MVP]: "Re: Setup Xerox Network Printer"
- Previous message: Dashe: "Re: OWA"
- In reply to: lion: "Re: Migration"
- Next in thread: lion: "RE: Migration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
