|
|
|
|
||||||
| ms.public.winnt.domain Usnet Forum about Windows NT. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 (permalink) |
|
Messages: n/a
Hébergeur: |
Hi Everybody, I was wondering if any of you could provide a detailed recap of
what would be needed in this scenario... I have a small domain - 8 workstations hooked up to a dc that's running on an old dell workstation (hence the desire to upgrade it). The dc is also my dns, dhcp, ris, gc, file and print server. Now, I have seen some excellent articles by many of you on ms.public.windowsnt when it comes to moving DCs alone. My impression is that I should add the new box as another dc, move fsmo roles, and make it a gc.... (just stop me when I stop making sense). Then I demote the old server and things magically continue running ![]() Somewhere in between I also enable DNS on the new server and if I correctly setup my zones, the replication will also happen on its own. What about dhcp? How about exporting the volume structure of my current box to continue its file and print server role without interruption? My current pdc uses 2 80gb drives in a dynamic/mirror environment, with each having about 4 partitions - system, sysvol, userfiles, applications + non-mirrored swap... To complicate matters further, after doing all of this I would like to change the name/ip address of the new pdc to what the current one is. Should this happen somewhere in between to make things easier. I have tried cloning my current pdc (i know, i know....) but it just would not work - both Symantec and Acronis products failed (my guess being the fact that I'm going from p2-500/256ram/ide drive to p4-3g/1024ram/sata2 and the h/w difference was too great). But time seemed a factor at first and well, now it doesn't. If it s, I can bring down the entire domain indefinitely. What's important is that userprofiles and shares remain the same. Thanks a million! Thomas J. |
|
![]() |
| Outils de la discussion | |
|
|