VeeamON 2024 | #BounceForwardThrowback (Win Custom Shoes!)
While I appreciate very much your problem-solving skills and imagination, the operation the promote/demote approach is enough, even with a re-use of the original IP. When the old one is back as a member server, and optionally had its IP changed if not powered off. Go on the new DC, execute locally or even from another DC ‘ntltest /server:targetdc /dsderegdns. Change your IP, reboot your DC and voilà! Each time a DC is started, ADDS DNS records are refreshed or created. Note: check your local DNS if you don’t have temporary IP left overs. Thanks, sure, the problem was that on the domain controllers was installed a custom app (chilling I know), and the client didn't know how to reinstall it, replicating the DCs solved the problem of reinstalling and reconfiguring this custom web app to the customer... Now the picture is complete! Thanks for sharing! Oli
While I appreciate very much your problem-solving skills and imagination, the operation the promote/demote approach is enough, even with a re-use of the original IP. When the old one is back as a member server, and optionally had its IP changed if not powered off. Go on the new DC, execute locally or even from another DC ‘ntltest /server:targetdc /dsderegdns. Change your IP, reboot your DC and voilà! Each time a DC is started, ADDS DNS records are refreshed or created. Note: check your local DNS if you don’t have temporary IP left overs.
I am a bit curious here, was there anything preventing you from doing a simple vMotion of the domain controllers to the new hosts? Yes, VMware HCL, vCenter 6.7 can’t pilot 5.5 hosts. Cross-vCenter started with 6.5 but it is a pain to setup. Starting 6.7 requirements got easier and better, more scenarios (shared or non-shared storage) appeared also.Regards,Oli
We had an upgrade case lately which went sideways. We discovered the backup was falling and the engineer was unable to restart from the Veeam backup. The FTP helped to deploy a fresh versionAs a side note, VMware allows only certain upgrade path even you are using the same branch (https://interopmatrix.vmware.com/#/Interoperability ). e.g. express patch on vCentre isn’t allowed/supported to upgrade to major. You can also have differences in the DB version, schema, and the FTP,FTPS, etc.. stays the easiest way to quickly identify it since it is part of the filename scheme. Image restore isn’t reliable enough.Oli
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.