OS Server 2012 R2 Domain Name Change (not as simple as add and remove)

Single DC? It could be a DNS issue. There's an MS-based post floating around somewhere, I'll dig it out.

This is based on the MS FAQ I was thinking of:

https://mizitechinfo.wordpress.com/2013/06/10/simple-guide-how-to-rename-domain-name-in-windows-server-2012/

Two DC's

Plus it only happens on this one server (it's an app server and up until the end of last year had multiple NIC interfaces).

DNS looks fine tbh, there's only one forward and reverse zone and there are no spurious entries/aliases etc

So the one with the error is not and has never been a DC?

I would remove it, do metadata cleanup on AD and try running it on the app server too although you'll have to install it first probably.

Could also try running ccleaner on the app server to see if anything is revealed.

You did force a replication after removal, raise the priority and give it time to settle?

Him Her said:

So the one with the error is not and has never been a DC?

I would remove it, do metadata cleanup on AD and try running it on the app server too although you'll have to install it first probably.

Could also try running ccleaner on the app server to see if anything is revealed.

You did force a replication after removal, raise the priority and give it time to settle?

Click to expand...

The problem isn't with a DC, its with a member server. It's never once been a DC, however it is the only server in the domain i did an upgrade from 2008 R2, but it only seems to have happened recently. Can't say when as I only noticed it last night (did a memory upgrade so had to power down my ESXi host)

It's a bit of a weird issue, its almost like the same problem you get with multiple NIC's and when you drop back to one, the #1 #2 still remain in the registry and treat it like a third card.

I have ccleaner running as standard.

I was suggesting the fault could lie with the domain you connect it to? Is the errant 3 still there when it's removed?

Him Her said:

I was suggesting the fault could lie with the domain you connect it to? Is the errant 3 still there when it's removed?

Click to expand...

Well no, because there is no domain lol as it just drops back to workgroup.

Its just bugging me at the moment HH, not causing me any issue but I'm a pedantic bugger.

I'm still looking, but I'm trying to do about ten things at once (need to rebuild my VC Server, plus some other minor irritations). Not to mention my missus had a hissy fit yesterday because I spent the first three hours of the morning glue to my office chair...

Lol, oops! When you get back to it I would just give it a quick ntdsutil, its cleared up a few odd issues for me.