Resara Migration - COMPLETE!
Post #1
Posted:
MAKE SURE YOU HAVE A BACKUP PRIOR TO ATTEMPTING A MIGRATION!
RAZDC CANNOT BE HELD LIABLE FOR A MIGRATION FAILURE OR LOSS OF DATA.
THIS INFORMATION IS PROVIDED AS-IS WITHOUT WARRANTY. USE AT YOUR OWN RISK!
Setup RazDC to have a unique hostname but the same domain as Resara server. Then use Resara IP as the primary DNS.Once the network is configured, you can login again to begin provision. use the "Join" method.
On the preview screen, use Resara IP as the "Primary Domain Controller IP", and use the Resara server domain administrator password.
In the latest update, to accomodate Resara migrations, select "Samba Internal" for DNS backend.
BEFORE PROVISION: RazDC dos not speak Resara so you will need to manually create the DNS 'A' record for the RazDC server in Resara. Once this is done, you can click the "Setup Secondary DC" button in RazDC.
Once the provision is complete, you will need to login to RazDC and check the DNS configurations for Internal resolution, forwarders, and transfers. make sure Resara is configured as the primary IP for resolving the domain, then add RazDC as the secondary.
Perform full diagnostics and review the Replication log. You should be resolving internal/external DNS and have a successful replication.
STOP
At this point, you should update all of your clients to use RazDC as a SECONDARY DNS. This will vary in each network, check your devices with static IP addresses as well!
At minimum, wait for the duration of your DHCP lease time for clients to pickup the new DNS server via DHCP. As an alternative, on small networks you can also run "ipconfig /renew" on each client.
CONTINUE
Once RazDC is appearing as a secondary DNS, you can launch the services windows and FSMO roles window on RazDC. You will see DNS roles and services will be missing/stopped.
Now we need to upgrade the samba internal database in RazDC to use the Bind9_DLZ backend.
In te RazDC console, run the 'raz' command, and run 'dnsmig' to perform the upgrade.
In the RazDC GUI, refresh the FSMO window and the servics window. RazDC should hold the roles for Domain DNS and Forest DNS. The DNS service should also be running.
If not, click start for DNS service and refresh the winow until it appears as running.
Next, open the internal resolution under DNS sub menu and make set RazDC IP as the primary/Only IP avaialble for lookups.
In the FSMO Roles window, you can begin transfering each role.
Click one transfer at a time and wait for a response until each role has been moved to RazDC.
Power down Resara.
At this point, you should confirm your workstation are still able to login to the domain.
If everything appears to be working, you can remove Resara IPs from DHCP/DNS and delete the associated users and machine.
Once Resara is delete and resara user accounts are removed: Congratulations on your Resara to RazDC migration!
Bryan King
Sorry, this topic is not accepting new posts.