Emerson Exchange 365

In reply to Nick Mason:

Okay, thanks. I've already changed the domain name once.. I'll find the youtube video to change it again. !! Seems it should have been easier, but appears to have worked, so i'll stick to the method.

In reply to TreyB:

Before changing the domain name (Or reinstalling the IDDC’s), I would suggest unjoining all the domain members and deleting them from the Active Directory.

In reply to Nick Mason:

The only members are the 2 IDDCs.. noted.

In reply to Nick Mason:

Okay, so this is becoming a bigger problem..wish i would have known not to use this right away.. you'd think the KBA for actually setting up the IDDC would mention it rather than finding it in release notes for v15.. Anyways. I'm having a lot of trouble with this. I got into a problem with changing the domain name the way i did before. Probably because I now have to controllers on the domain. Before i did it when i only had the one setup so far. Well, it's failing at the point of running
rendom /upload.

So, i figure I'll just go ahead and run the installation again. Hoped it would prompt me to create a new forest like it did original. Nope. So then I'm thinking okay, i'll demote the controller first, set it to workgroup and start from there. But i can't remove AD DS roles because of the remote shell access error. I then Try to edit group policy to allow remote shell access. Nope that doesn't help.

I'm stuck. I wish i could just wipe this whole dang machine and pretend i just received the servers. I'm wondering what the state of these come as and if I can just reinstall Server 2022 and go from there. It'd give me some peace of mind that there aren't any remnants of the old domain left over since I've kind of probably made a mess of things at this point.

Including "deltav" as a label in your top level domain name seems to be acceptable, so I assume this requirement refers specifically to the domain name rather than other labels in the top level domain. I believe Emerson deployments will typically use the FQDN format "[site].deltav.[company].local" so you'd have to call it a bug if systems started breaking due to use of "deltav" in the top level domain.

In reply to TreyB:

The presence of controllers won’t affect your situation.

Sounds like you have physical servers for your IDDC’s. If this was a virtual environment I’d suggest just building new. However, since I’m assuming you don’t have image disks for the servers, I’d keep working toward getting the machines back to a base 2022 install. Then you could simply rerun the IDDC installers which sounds like what you’re working towards.

If you’re having issues removing the existing AD/DS, GSC could most likely get you past that step. I was thinking there was a powershell cmdlet to perform the remote shell access setting, but I can’t seem to find it.