The Name Could Not Be Resolved - Adding additional Mailbox - Exchange 2010

Having an issue within my entire exchange organization when trying to add an additional mailbox. When we click the Add button, it returns
"The Name Could Not Be Resolved. The Application cannot Complete"

Note, this is before attempting to enter a name (no, not hidden from the GAL).

But yes, Autodiscovery is working. I used used the Test Email AutoConfiguration, and everything looks A-OK. OWA works no problem, and I can browse to the OAB.xml via the web.

I was looking at OAB as an issue. When I started there were issues downloading it, and running a get-Mailboxdatabase "xxx" |fl OfflineAddressbook kicked back a public folder database that existed on my old 2003 server (offline for about a year now).

I was able to fix that, but still the issue remains. Other things I note is in ADSI, I still see my old Administrative Group (and sub-keys) from my 2003 server....

Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Offline address book IS working, I had to do some work (more than above, I had to make some changes to hierarchy attributes in ADSI)

Simon - RE: 2003. That's what my current concern is, the 2003 has been removed, but it seems there are some items left orphaned (the OAB and Public folders was one). Nothing in Exchange sees the 2003 server, but in ADSI I do have an entry for the old Administrative group. That contains all the sub folders you'd expect from a active server.

Here's the rub, the 2003 server is long one, over a year. I had gone through the last 2003 removal process (this wasn't the first migration I have done). The really odd part is that this issue is somewhat new, in the last month or so.

So I realized I have a VM that was a copy of my physical machine, right before it went offline. Only problem is I can't access the ESM, and system attendant won't start. Is there any way ti use this box? Or should i just spin up a new image and install the ESM?

Just to clarify, looking through ADSI, I see that my Public Folders do look to be in the correct Administrative group. I double checked my Folder Hierarchy and it does look to point in the right place.

I checked to ensure that under my new Administrative group, I have the "Folder Hierarchy", with a CN=Public Folders. Under the same (correct) Administrative Group, under Databases, Public Folder Database, the msExchOwningPFTree attribute does point to the public folders in the correct administrative group.

Featured Post

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!

To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it.
The vast majority of email clients display l…

Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…