Quantcast
Channel: Forum Microsoft Identity Manager
Viewing all articles
Browse latest Browse all 4767

MIM creating Exchange 2010 legacy mailboxes

$
0
0

I wanted to see if anyone have ever run into this.  I have AD provisioning up and running with MIM. The AD account is created and all looks good from that perspective.  I have run into a problem however where the Exchange mailbox is created but is in a corrupted state when I query it with Powershell.  When I look in the Exchange console it states that it is a legacy mailbox.  I am using the following to provision the account and I know this has worked in other environments.  We have tried this manually from the Exchange console and it seems to work fine.

The AD environment is is functional level 2003 and Exchange 2010.  The code is as follows:

mailboxMDB = "CN=MyDB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=acme,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acme,DC=com";

CSentry = ExchangeUtils.CreateMailbox(ManagementAgent, dn, nickName, mailboxMDB);

CSentry["msExchHomeServerName"].Value = "/o=acmeou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=myServer"; // msExchangeHomeServer;

 CSentry["msExchRBACPolicyLink"].Value = "CN=Default Role Assignment Policy,CN=Policies,CN=RBAC,CN=acme,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acme,DC=com";

//Added the following line as a potential fix but no luck

CSentry["homeMTA"].Value = "CN=Microsoft MTA,CN=PDMBXDB2,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=acme,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acme,DC=com";

MIM doesn't throw any errors when exporting to AD and there is nothing else in the logs.  Does you have any idea what might be going on and why they are being created as legacy mailboxes?  


Viewing all articles
Browse latest Browse all 4767

Trending Articles



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