Re: SBS 2003 R2 Install
- From: "nordberg" <nordberg_73@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 Nov 2006 10:38:40 -0000
What Gav is describing sounds a lot like Swing Migration. You will find many
many disciples of this process on this newsgroup.
www.swingmigration.com
"ChrisW" <ChrisW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DDE2DC93-E816-4521-B349-590BCA0E2FA8@xxxxxxxxxxxxxxxx
Many thanks Gav, wow it does look like a long process. Plus I don't have a
spare 3rd machine. I only have 5 clients who only use the old sbs box for
mail, so what I'd planned was to set up the new sbs box exactly the same
as
the old one, take each clients e-mail and put it into personal folders on
each client, then log off each client, then just remove the old sbs box
from
the lan and replace it with the new box. Trouble is my new box wants to be
connected to the lan to continue the install! Any other ideas?
"GavG" wrote:
Sorry Chris, forgot to mention you need to finish the normal sbs setup on
the
new machine after you have replicated with and removed the temp DC. If
you
end up doing it this way don't start without getting some further
instructions on the step by step processes as it would be fairly easy to
get
one step wrong and have to start again or worse still mess something up
on
your production environment. Let me know if you need any more info.
"GavG" wrote:
Chris, I have done something similar with a migration from sbs2000 to
sbs2003
which works well, the only problem being you need a spare 3rd machine
to add
into the existing domain, replicate ad and then take off the production
lan.
Once this is done you need to tidy up AD and take out all references to
the
original SBS box (ntdsutil), sieze all fsmo roles and make sure that
the temp
dc thinks its in charge, the final step is to do a base build on your
final
new server but do not install sbs fully, interrupt at the end of the
windows
2003 server setup, ensure it is named exactly the same as your original
box,
same IP etc, then add it to the test lan containing your tempdc, then
follow
the same procedure as before, promote to a dc, replicate and once your
happy
all ad info is there and replicated, remove the temp dc. Seize all fsmo
roles
on the replacement, cleanup ad again, removing references to the temp
dc.
Then is all you have left to do is migrate data and exchange, which I
did by
tape as per a normal offline restore of exchange. Take a client off the
production lan and boot it onto a test lan to ensure it logs on OK and
brings
up exchange. Sounds a long process I know but if done properly it will
allow
you to retain all ad info, computer accounts, use the same name for
your
server so unc paths are retained etc. Hope that helps.
"ChrisW" wrote:
I am installing R2 onto a brand new server, which is currently not
connected
to our network which already has a a SBS 2003 SP1 server running DHCP
on it.
I want to set up the new server exactly as the existing one (same
server
name, same domain etc and then just turn off the old one, use the new
one),
but the install wants me to connect the new server to the network so
that it
can continue.... Isnt this going to create problems on the network?
Is there
an easy way around this? Thanks in anticipation.
.
- Follow-Ups:
- Re: SBS 2003 R2 Install
- From: GavG
- Re: SBS 2003 R2 Install
- Prev by Date: RE: Lost Email with Pop3 Connector
- Next by Date: Re: SBS 2003 R2 Install
- Previous by thread: Re: EFS Recovery Agent certificates
- Next by thread: Re: SBS 2003 R2 Install
- Index(es):
Relevant Pages
|
