It was hard to find a Heading for this question.
I have a running SQL server / Windows 2019 Standard. We are changing domains (from a .local to our proper domain name.
I will clone the running SQL server before doing anything.
Joining the new domain is not an issue, the question is, if after doing this, if SQL doesn't work as needed, and we need to go backwards.
If I fire up the clone that was made prior to joining SQL server to the new domain, will the old domain recognize the restored clone and move on as if nothing ever happened.
Kind of an Active Directory questions as well as VMware question I guess.
Thanks for any insight.
G.T.
Not really a VMware question at all since it either deals with AD and Windows or SQL server and the changes thereto.
I know , I was hoping to draw on someones experience. Since its a VMware process, SQL and AD people say the same thing on that side I presume.
Moderator: Thread moved to the Windows guest area. Your question is for Microsoft rather than VMware.
Totally not a VMware question at all, that being said:
Joining the new domain is not an issue, the question is, if after doing this, if SQL doesn't work as needed, and we need to go backwards.
If I fire up the clone that was made prior to joining SQL server to the new domain, will the old domain recognize the restored clone and move on as if nothing ever happened.
what i would do is this: before cloning the VM make sure to log in with a local admin (domain account) so those credentials are cached and in case you need to restore the VM.
Restore it with the nic disconnected and make sure to log in with the last domain account that you have logged so it can log in.
After that you can safely reconnect it's nic.