C
Charlie
Hi
The organization that I work for will be doing a Win2K
Active Directory upgrade/migration fairly soon. I am an
admin of a resource domain. All of the existing domains
will be collapsed down to one.
Here is my problem: Our PDC is also our main file and
print server and will continue to be when we are in an
Organizational Unit in the AD domain. Needless to say,
we have lots of data, ACL's and domain local groups on
it. For some reason, I thought that you could upgrade an
NT4 domain controller directly to a Win2K member server,
which probably would have solved the problem. Since I
can't do that, I'm wondering what my options might be.
Do any of the migration tools migrate NT4 DC's to member
servers of an AD domain? I'm guessing that the answer is
no. I could simply wipe out the OS partition after
promoting a BDC to PDC, do a clean install of W2K or W2K3
and join it to the existing NT4 domain as a member
server. I could then recreate the local groups on the
member server and use Group Copy to copy all of the local
groups from a DC. Since I have used the Printmig utility
to copy all of the printers from the PDC to a backup
print server, I could use it to copy them from the backup
print server back to the new member server.
Migrating the member server to the AD domain is well down
the road and someone else will be responible for that. I
just don't want them to show up one day and say "OK, time
to bring down your domain controllers."
Question #1: If I use the above method, what happens to
the ACL's on all of the data and printers? Will they see
the member server local groups as being the same as the
domain local groups that they originally were written
for? I have successfully used Robocopy to copy a
directory tree and its permissions from a domain
controller to a member server, but this is a little
different because the data is not being moved, the OS is
being replaced.
Question #2: Is there a better method?
Thanks
The organization that I work for will be doing a Win2K
Active Directory upgrade/migration fairly soon. I am an
admin of a resource domain. All of the existing domains
will be collapsed down to one.
Here is my problem: Our PDC is also our main file and
print server and will continue to be when we are in an
Organizational Unit in the AD domain. Needless to say,
we have lots of data, ACL's and domain local groups on
it. For some reason, I thought that you could upgrade an
NT4 domain controller directly to a Win2K member server,
which probably would have solved the problem. Since I
can't do that, I'm wondering what my options might be.
Do any of the migration tools migrate NT4 DC's to member
servers of an AD domain? I'm guessing that the answer is
no. I could simply wipe out the OS partition after
promoting a BDC to PDC, do a clean install of W2K or W2K3
and join it to the existing NT4 domain as a member
server. I could then recreate the local groups on the
member server and use Group Copy to copy all of the local
groups from a DC. Since I have used the Printmig utility
to copy all of the printers from the PDC to a backup
print server, I could use it to copy them from the backup
print server back to the new member server.
Migrating the member server to the AD domain is well down
the road and someone else will be responible for that. I
just don't want them to show up one day and say "OK, time
to bring down your domain controllers."
Question #1: If I use the above method, what happens to
the ACL's on all of the data and printers? Will they see
the member server local groups as being the same as the
domain local groups that they originally were written
for? I have successfully used Robocopy to copy a
directory tree and its permissions from a domain
controller to a member server, but this is a little
different because the data is not being moved, the OS is
being replaced.
Question #2: Is there a better method?
Thanks