Quantcast
Viewing all articles
Browse latest Browse all 19214

ExhangeLegacyDN weirdness...

Yesterday we started noticing some problems with our BlackBerry users which indicated to me some kind of issue with Exchange

After running:                 

get-mailboxdatabase | flmailservername,exchangelegacydn

The output lists:

ExchangeLegacyDN: /o=organization/ou=Exchange Adminitstrative Group (administrative group name)/cn=Configuration/cn=Servers/cn=WRONGSERVERNAME/cn=Microsoft Private MDB

ExchangeLegacyDN: /o=organization/ou=Exchange Administrative Group (administrative group name)/cn=Configuration/cn=Servers/cn=CORRECTSERVERNAME01/cn=Microsoft Private MDB

ExchangeLegacyDN: /o=organization/ou=Exchange Administrative Group(administrative group name)/cn=Configuration/cn=Servers/cn=CORRECTSERVERNAME02/cn=Microsoft Private MDB

So,CORRECTSERVERNAME01 and CORRECTSERVERNAME02are our two Exchange 2010 servers.

But,WRONGSERVERNAME only exists in AD as a disabled computer account, and I was told that it never served any exchange roles, although I'm not convinced (It existed before I worked here).  Either way this machine has long since gone away, but somehow its still showing up as noted above.

I need to get this incorrect server out so that nothing in AD thinks its a legacydn, what's the best way to do this?

Thanks


Viewing all articles
Browse latest Browse all 19214

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>