Ugh, Exchange, lol.
It makes sense. I would recommend removing AD from one of the servers, moving and reconfiguring it, and then installing AD again. You would need to wait for (or force) replication between removing and installing. This would give you the opportunity to do whatever you needed to the server (change the IP address, rename, etc) without affecting AD.
Years ago, you weren't allowed to change the IP address on a domain controller. Then, in Server 2008 I think, Microsoft said you could. I have tried it, and most things work. But there are some things that just seem to fail. DNS records get updated, SRV records, etc., but I have had weird issues, like time sync issues, after changing a DCs IP address.
So even though Microsoft supports it, it doesn't seem like it's worth the risk to me. Especially when it is so easy to just remove AD, and then add AD once the move is complete.
The schema master role is forest-wide, meaning there is only one DC in the entire forest that holds the schema master role. If you are trying to move the DC that holds that role, you would need to move the role to another DC, (and any other roles), remove AD, move the server and reconfigure, then add AD, then move the role to the new DC.