georgecooldude
asked on
Migration vs Upgrade from NT to 2003? Pros + Cons - Did i make the right decision
I have migrated my user accounts and computers from my NT domain to a 2003 domain.
I managed to keep the same Netbios domain name but i still require rejoining my computers back to the domain as they are looking for a NT4 domain controller. Had I upgraded the domain to 2003 would those clients still need rejoining to the domain?
What are the pros and cons of migrating vs upgrading. Require expert opinions. =) Thanks.
I managed to keep the same Netbios domain name but i still require rejoining my computers back to the domain as they are looking for a NT4 domain controller. Had I upgraded the domain to 2003 would those clients still need rejoining to the domain?
What are the pros and cons of migrating vs upgrading. Require expert opinions. =) Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok, i just found out about the PDC emulator by rightclicking on my domain in active directory users and computers and selecting the operations master bit.
Now as I created this domain from scratch and migrated the GUID for the domain (think its called GUID) will be different. Now I dont mind re-connecting the 2000 and XP machines. But is there a way to "import" settings from the NT machine so I dont have to reconnect each machine. Surely there must be a way when u use the migration tool...
I need some advice on this one =)
Now as I created this domain from scratch and migrated the GUID for the domain (think its called GUID) will be different. Now I dont mind re-connecting the 2000 and XP machines. But is there a way to "import" settings from the NT machine so I dont have to reconnect each machine. Surely there must be a way when u use the migration tool...
I need some advice on this one =)
I think the problem here is keeping the same domain name. As leew said, you have experience some real problems, especially with DNS. As far as upgrading vs migrating, I would upgrade instead and then change the domain name (new feature in 2003). You can also change the name of your domain controller. If you migrate, you have to worry about a lot of issues such as sid history and things like that.
ASKER
ive found migrating fairly easy and moved the sids. My main problem has been having to rejoin the computers to the domain.
This is something I dont want to do.
I will look at upgrading and then replicating the changes to my other domain controller.
This is something I dont want to do.
I will look at upgrading and then replicating the changes to my other domain controller.
Sounds like a good plan.
I did an upgrade a couple of months ago and I did not have to rejoin the computers, so it must be something with the domains being the same name. Please keep us updated on your findings.
Thanks,
cfairley
I did an upgrade a couple of months ago and I did not have to rejoin the computers, so it must be something with the domains being the same name. Please keep us updated on your findings.
Thanks,
cfairley
ASKER
leew, If I have an NT box upgrade that to 2003. Lets call this computer A. Then I setup Computer B and replicate the changes to them. I disonnect computer A and promte computer B. Will the NT4 emulator stay intact this way?
I need a definate answer yes or no =)
I need a definate answer yes or no =)
Hello George,
From the way this one is phrased, as long as you transfer the FSMO roles from computer A to Computer B, the PDC emulator will stay in tact.
Thanks,
cfairley
From the way this one is phrased, as long as you transfer the FSMO roles from computer A to Computer B, the PDC emulator will stay in tact.
Thanks,
cfairley
ASKER
cfairley, you mentioned about moving FSMO roles.
Could you just go over what these are, where they are located and how they affect me.
How could i transfer these using the migration tool?
I think ive been told the answer but my brain has forgotten. whoops.
Could you just go over what these are, where they are located and how they affect me.
How could i transfer these using the migration tool?
I think ive been told the answer but my brain has forgotten. whoops.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok thanks for the links. I will have a look at them after my lunch break.
One thing I don't understand. Why do micrsoft make a migration tool suggest you use it and leave out an option to migrate the FSMO roles. I just dont understand their reasoning for this.
Was the ADMTv2 tool designed for large or small companys?
---
I just found a command line tool called "ntdsutil" - Apparently this can move the roles? Anyway i will go for lunch then =)
One thing I don't understand. Why do micrsoft make a migration tool suggest you use it and leave out an option to migrate the FSMO roles. I just dont understand their reasoning for this.
Was the ADMTv2 tool designed for large or small companys?
---
I just found a command line tool called "ntdsutil" - Apparently this can move the roles? Anyway i will go for lunch then =)
I would think that they would want you to do that manually. From my experience, that's the best way to transfer roles. Usually, after you transfer one role, you do a manual replication and wait about 30 minutes before the next transfer. Also, there are other configs to factor, like the Infractructure Master can't be on a Global Catalog unless you have only one controller or all your controllers are global catalogs.
ASKER
ok, I am going to setup a new PDC and upgrade it to windows 2003. At this point I want to change the domain to <ourdomain.local> (with a .local extention) I hope this wont affect the NT4 domain emulator for the clients to connect to.
Then I will make it the very top permissions it can get. A new domain in a new forest I think.
Then with my other 2003 machine I hope to create an additional domain controller for it.
How can this be done? I gave up on this option last time as it was too hard but I think in the long run its going to make things alot easyier if we dont have to manually change the domain. I dont mind visiting the computer to update the DNS or WINS settings but changing the domain is gonig to be almost impossilbe as we need to keep profiles and some users have very little space left on their harddrives for this along with the service pack upgrade
Then I will make it the very top permissions it can get. A new domain in a new forest I think.
Then with my other 2003 machine I hope to create an additional domain controller for it.
How can this be done? I gave up on this option last time as it was too hard but I think in the long run its going to make things alot easyier if we dont have to manually change the domain. I dont mind visiting the computer to update the DNS or WINS settings but changing the domain is gonig to be almost impossilbe as we need to keep profiles and some users have very little space left on their harddrives for this along with the service pack upgrade
George,
In order to change the domain name, all your DCs will have to be 2003.
In order to change the domain name, all your DCs will have to be 2003.
ASKER
thats ok. We only have 1 NT server, which we are going to replace with 1 2003 server.
Excellent, pls keep us posted.
Thanks,
cfairley
Thanks,
cfairley
ASKER
Thanks!
The upgrade has been postponed until Christmas now but I have learn't from this post. =)
The upgrade has been postponed until Christmas now but I have learn't from this post. =)
Thanks for the update!
All will be waiting to assist if needed.
All will be waiting to assist if needed.
ASKER
The NT server is going to come off the the network so they wont conflict. Is it still going to be a problem?
Can you clarify. If I were to upgrade and then replicate the changes to another 2003 server. Would all the client machines still need to rejoin the network?