D
Dan Williams
I'm attempting to migrate a SBS 2000 server to new hardware and am following
the procedures mentioned in
http://groups.google.com/[email protected]&rnum=1
What i've done so far is:-
1. Setup a temporary server with the full version of Windows 2000 server and
connected it to our existing network
2. Made the temp server an additional domain controller, which replicated
all our existing active directory objects (i.e. users, computers, policies,
etc) to the temp server.
3. Installed DNS server onto the temp server which replicated all the DNS
entries.
4. I then unplugged the temporary server from the existing network and
plugged it into its own hub.
5. I also connected the new server to this same hub and installed Windows
2000 server on to it, ensuring that its setup with the exact same name and
ip addresses as our old SBS server.
6. Made the new server an additional domain controller, which in turn
replicated all the AD info over again.
7. Installed DNS server onto the new server which replicated the DNS entries
from the temp server.
I'll be restoring the Exchange databases and shared folders from the backup
image.
This seems to work ok, but i'm having problems with the new server
recognising itself as the primary domain controller, etc. I get 'Naming
information cannot be located because: The specified domain either does not
exist or could not be contacted'
In the thread mentioned above, it says to transfer the FSMO roles from our
existing server to the temporary one, and then to the new one. Would this
solve my problem and by doing so will it cause additional problems on our
existing server? I'm hoping to leave the old server up and running so that
our staff can use it to logon and access email, etc. (i'll worry about
restoring email and user docs later).
What happens when i transfer the FSMO roles to the temporary server? Will my
users still be able to log on to the network and continue to work as normal?
Is there anyway i can get the new server to seize control over the domain?
Any help is much appreciated.
Thanks in advance
Dan Williams
the procedures mentioned in
http://groups.google.com/[email protected]&rnum=1
What i've done so far is:-
1. Setup a temporary server with the full version of Windows 2000 server and
connected it to our existing network
2. Made the temp server an additional domain controller, which replicated
all our existing active directory objects (i.e. users, computers, policies,
etc) to the temp server.
3. Installed DNS server onto the temp server which replicated all the DNS
entries.
4. I then unplugged the temporary server from the existing network and
plugged it into its own hub.
5. I also connected the new server to this same hub and installed Windows
2000 server on to it, ensuring that its setup with the exact same name and
ip addresses as our old SBS server.
6. Made the new server an additional domain controller, which in turn
replicated all the AD info over again.
7. Installed DNS server onto the new server which replicated the DNS entries
from the temp server.
I'll be restoring the Exchange databases and shared folders from the backup
image.
This seems to work ok, but i'm having problems with the new server
recognising itself as the primary domain controller, etc. I get 'Naming
information cannot be located because: The specified domain either does not
exist or could not be contacted'
In the thread mentioned above, it says to transfer the FSMO roles from our
existing server to the temporary one, and then to the new one. Would this
solve my problem and by doing so will it cause additional problems on our
existing server? I'm hoping to leave the old server up and running so that
our staff can use it to logon and access email, etc. (i'll worry about
restoring email and user docs later).
What happens when i transfer the FSMO roles to the temporary server? Will my
users still be able to log on to the network and continue to work as normal?
Is there anyway i can get the new server to seize control over the domain?
Any help is much appreciated.
Thanks in advance
Dan Williams