Mark,
What Todd said is good advice.
I did my AD upgrade back in February.
I did as Todd said and was worried about the shares I had too.
However my file server was already a 2000 server when I did the AD
conversion.
This is the steps I took.
1) New server brought up as NT BDC
2) Promoted new server to PDC and let run for a few days to smooth out.
3) Day of upgrade, took an old bdc down, just in case you need to promote to
pdc if something goes wrong.
4) Upgraded NT PDC to W2K or W2K3
5) Did the AD upgrade on the upgraded server, old pdc.
6) Did the AD Upgrade on my W2K file/print server.
I did have one scare during this when I thought all the share permissions on
all my files and folders were gone, but after getting all the DNS settings
properly set, they were all there and I didn't have any issues.
DNS is a huge part of AD, make sure it works and you understand it.
I'm sure you have already been here, but just in case, read a lot here:
http://www.microsoft.com/windows2000/technologies/directory/AD/default.asp
Good Luck.
Jim Moore
-----Original Message-----
From: Todd Anderson [mailto:tanderson@...]
Sent: Friday, July 16, 2004 1:37 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] RE: AD Migration
Mark,
I'll tell you what a consultant told me a few months ago which is how I plan
on doing this in the next few weeks.
Take ANY box, desktop or otherwise, that will run NT-Server. Install JUST
NT-Server on this box and promote it to be your PDC with your existing PDC
demoted to be a BDC.
Upgrade this new stand alone box "in place" ... IF and WHEN you get it to
work then deal with your original server.
This way if something goes wrong ( never happen of course ) you can always
fall back to your current PDC and try again.
Sure does make sense to me.
Good luck
Todd Anderson
What Todd said is good advice.
I did my AD upgrade back in February.
I did as Todd said and was worried about the shares I had too.
However my file server was already a 2000 server when I did the AD
conversion.
This is the steps I took.
1) New server brought up as NT BDC
2) Promoted new server to PDC and let run for a few days to smooth out.
3) Day of upgrade, took an old bdc down, just in case you need to promote to
pdc if something goes wrong.
4) Upgraded NT PDC to W2K or W2K3
5) Did the AD upgrade on the upgraded server, old pdc.
6) Did the AD Upgrade on my W2K file/print server.
I did have one scare during this when I thought all the share permissions on
all my files and folders were gone, but after getting all the DNS settings
properly set, they were all there and I didn't have any issues.
DNS is a huge part of AD, make sure it works and you understand it.
I'm sure you have already been here, but just in case, read a lot here:
http://www.microsoft.com/windows2000/technologies/directory/AD/default.asp
Good Luck.
Jim Moore
-----Original Message-----
From: Todd Anderson [mailto:tanderson@...]
Sent: Friday, July 16, 2004 1:37 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] RE: AD Migration
Mark,
I'll tell you what a consultant told me a few months ago which is how I plan
on doing this in the next few weeks.
Take ANY box, desktop or otherwise, that will run NT-Server. Install JUST
NT-Server on this box and promote it to be your PDC with your existing PDC
demoted to be a BDC.
Upgrade this new stand alone box "in place" ... IF and WHEN you get it to
work then deal with your original server.
This way if something goes wrong ( never happen of course ) you can always
fall back to your current PDC and try again.
Sure does make sense to me.
Good luck
Todd Anderson