Comments on: Adding Exchange 2003 Mailboxes to Existing Accounts

By: Carol

Carol — Thu, 03 Jul 2008 06:10:54 +0000

Hi there.

According to the error message you’re using a reference DN attribute in the metaverse as one of the source attributes for your flow rule. You can’t do that.

By: wkuang

wkuang — Wed, 02 Jul 2008 20:32:55 +0000

Hi, Carol,

I have an exact problem trying to create mailboxes for existing AD users by exporting the homeMDB as a reference attribute. When I tried to use the advance attribute flow, I got the following error message from MIIS.

Metaverse reference attributes can not be defined as source attributes for rules extension export flow.

How did you resolve this problem?
My environment is quite simple with W2K3 domain controllers and Exchange2003.
The following are my codes,

Public Sub MapAttributesForExport(ByVal FlowRuleName As String, ByVal mventry As MVEntry, ByVal csentry As CSEntry) Implements IMASynchronization.MapAttributesForExport
‘ TODO: Add export attribute flow code here

Select Case FlowRuleName
Case “homeMDB”
If Not mventry(“homeMDB”).IsPresent Then
csentry(“homeMDB”).Value = “CN=Mailbox Store (BINHRAEXCT001),CN=First Storage Group,CN=InformationStore,CN=BINHRAEXCT001,CN=Servers,CN=Highlands Ranch,CN=Administrative Groups,CN=CBI,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rbiustest,DC=net”
End If
End Select

‘Throw New EntryPointNotImplementedException
End Sub

By: Carol

Carol — Fri, 23 May 2008 18:55:05 +0000

Ron,

This may well be tricky to do properly as there isn’t even a powershell cmdlet that will remove just the mailbox (remove-mailbox deletes the user account as well – very strange). Try taking a snapshot of a user’s attributes using an ldap browser, then disable the mailbox in Exchange Mgmt Console, and then take an after snapshot. You should be aqble to work out what you need to change from ILM to achieve the same effect.

By: Ron

Ron — Fri, 23 May 2008 15:06:40 +0000

Carol,

I have another question. Similar to adding an Exchange account to an existing A.D. user, would you know how to go about removing an existing Exchange account, leaving the A.D. account enabled? (My environment is Exchange 2007 and ILM 2007)

Thanks.

By: Carol

Carol — Thu, 22 May 2008 06:49:04 +0000

Sounds like a great solution! Glad to hear you worked it out.

By: fordware

fordware — Wed, 21 May 2008 14:02:24 +0000

Not sure what the deal was. Since I have to come up with a solution that appropriately assigns the mailbox to one of a hundred available stores, I came up with a different solution involving identifying each store to a business unit, looking at the store size and then provisioning the mailbox to the smallest store available for that business unit. All this is done using a custom view and a SQL MA. I then float the homemdb and mailnickname back to my users, and I’m all set.

Thanks for your posts. It’s tough to find good MIIS resources out there, and I’ve gotten a lot of good info from yours.

By: Carol

Carol — Tue, 20 May 2008 18:35:41 +0000

Then you should be able to get it working. Have you followed through the code in debug mode and see what’s happening? The “not applied” makes me think that the export flow rule is not actually running. Check that all the metaverse attributes you’ve selected for the flow rule are actually populated, and also do full syncs rather than deltas.

By: fordware

fordware — Tue, 20 May 2008 16:09:16 +0000

Exchange 2003.

By: Carol

Carol — Tue, 20 May 2008 16:03:03 +0000

This post was written for Exch 2003, but I haven’t tried it with 2007. Which version of Exchange do you have?

By: fordware

fordware — Tue, 20 May 2008 15:23:25 +0000

Hey Carol,

Question for you, how is it that you’re able to flow this back to a reference attribute? I assume that’s my problem as I’ve yet to get this to work. I’ve followed your example, and even explicitly stated the full DN of the homemdb in the MAextension as a last resort. When previewing the object that should be getting the update, I just get a status of not applied.

Thoughts?