Moving initial duties to different server with AD
OK, to begin with I am talking about a home server test setup, which I use for teaching myself before inflicting my limited knowledge on others π At any rate, I set up two WIN2K servers with AD, and that is working fine.
OK, to begin with I am talking about a home server test setup, which I use for teaching myself before inflicting my limited knowledge on others
At any rate, I set up two WIN2K servers with AD, and that is working fine. Now I want to retire the original server. The question is:
If I run DCPROMO to demote the first one, will the second one take up the slack or do I need to move services over manually? Any good readme howto articles on this?
Thanks
At any rate, I set up two WIN2K servers with AD, and that is working fine. Now I want to retire the original server. The question is:
If I run DCPROMO to demote the first one, will the second one take up the slack or do I need to move services over manually? Any good readme howto articles on this?
Thanks
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
To be safe
Transfer the 5 fmso roles from dc1 to dc2 and make dc2 a GC
ADUC can do 3 of the roles
ADSS can do the GC under NTDS
ADDT can do 1 role.
and you will have to load the schema snapin to transfer the final role.
If you prefer to do this through CLI, then use ntdsutil.exe.
Unless DC1 provided DNS, DHCP, WINS, DFS Root, then that should do it, otherwise transfer those services and/or correct IP configs to DC2.
HTH
Transfer the 5 fmso roles from dc1 to dc2 and make dc2 a GC
ADUC can do 3 of the roles
ADSS can do the GC under NTDS
ADDT can do 1 role.
and you will have to load the schema snapin to transfer the final role.
If you prefer to do this through CLI, then use ntdsutil.exe.
Unless DC1 provided DNS, DHCP, WINS, DFS Root, then that should do it, otherwise transfer those services and/or correct IP configs to DC2.
HTH
Quote:Posted: 16th February 2003 10:34 Post subject:
--------------------------------------------------------------------------------
To be safe
Transfer the 5 fmso roles from dc1 to dc2 and make dc2 a GC
ADUC can do 3 of the roles
ADSS can do the GC under NTDS
ADDT can do 1 role.
and you will have to load the schema snapin to transfer the final role.
If you prefer to do this through CLI, then use ntdsutil.exe.
Unless DC1 provided DNS, DHCP, WINS, DFS Root, then that should do it, otherwise transfer those services and/or correct IP configs to DC2.
OK, I understand some but not all of your FLA & TLA's.
GC=Global Catalog
DC1=Domain Controller 1
DNS, DHCP,WINS I know.
Could you explain the others, or point me to a good primer.
--------------------------------------------------------------------------------
To be safe
Transfer the 5 fmso roles from dc1 to dc2 and make dc2 a GC
ADUC can do 3 of the roles
ADSS can do the GC under NTDS
ADDT can do 1 role.
and you will have to load the schema snapin to transfer the final role.
If you prefer to do this through CLI, then use ntdsutil.exe.
Unless DC1 provided DNS, DHCP, WINS, DFS Root, then that should do it, otherwise transfer those services and/or correct IP configs to DC2.
OK, I understand some but not all of your FLA & TLA's.
GC=Global Catalog
DC1=Domain Controller 1
DNS, DHCP,WINS I know.
Could you explain the others, or point me to a good primer.
Sorry, I am just used to typing out acronyms ...
ADUC - Active directory users and computers
ADSS - Active directory sites and services
ADDT - Active directory domains and trusts
NTDS - NT Directory services
CLI - command line interface, as oppossed to GUI
FSMO - flexible single master operations
DFS - distributed file system.
www.labmice.net for a further explanation of what each is, or if you have more specific questions, feel free to inquire.
ADUC - Active directory users and computers
ADSS - Active directory sites and services
ADDT - Active directory domains and trusts
NTDS - NT Directory services
CLI - command line interface, as oppossed to GUI
FSMO - flexible single master operations
DFS - distributed file system.
www.labmice.net for a further explanation of what each is, or if you have more specific questions, feel free to inquire.