Thanks for the quick reply… I was leaning that direction too. A bit of information I left off the original post is that the homeMDB of existing users is the same as what I am flowing so that substantiates what our instincts are telling us… Do you know of a permissions document for a forest/child domain setup? The architecture is like this:

Root (forest) Domain (abcd.com)
(Exchange)
|
| (disjointed namespace)
|
Child (tree) Domain (wxyz.com)
(ILM)

Again, thanks for the help… Your site has provided awesome guidance and been a tremendous help to me on my project. I will definitly update you to the resolution when I find it.

I haven’t had to flow those three attributes seperately. The error you’ve seen running set-mailbox is most likely the same problem being experienced by ILM, so you should focus your efforts there. I have seen a similar error once before, and it was due to a permissions error in the Configuration part of AD – but we were seeing other Exchange problems as well, so I don’t think that’s your exact problem, however I do think permissions is the most likely cause.

Background
ILM 2007 FP1 Exchange 2007 provisioning. Single forest with multiple trees (disjointed namespace). ILM service account has Replicate Directory Changes (at my domain level), rights to create, delete and modify objects (at my domain level) and is a memeber of the Exchange Recipeint Administrators group (at the forest domain level). The Exchange environment was upgraded from EXchange 2003 to Exchange 2007. I have Exchange 2007 SP2 Management Tools and PowerShell v 1.0 installed on my ILM server.

Situation
Exchange 2007 provisioning works kinda. I can create mailboxes, contacts and mail enabled users. ILM Exchange provisioning when creating mailboxes is creating “Legacy Mailboxes” instead of “User Mailboxes”. Looking into what constitutes a Legacy Mailbox in Exchange 2007 I find that 3 attributes are not being set during provisioning. The 3 attributes are msExchVersion, msExchRecipientDisplayType and msExchRecipientTypeDetails. Manually setting these attributes does change the mailbox from Legacy Mailbox to User Mailbox. User Mailbox is desired state because of the version of OWA. I did not experience this in my testing environment and my test environment is not replica of production because of the size of production, however same versions of software were used.

Additional Information
I attempted running the following command: set-mailbox test.account02 -ApplyMandatoryProperties from Exchange Powershell on my ILM server. Running the command resulted in the following error: “Set-Mailbox : Could not find the default Administrative Group ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’.”

Questions
Do you think this is a permissions issue?
Do you think this is a software compatibility issue?
Have you ever had to flow the 3 attributes identified above via ILM?

Environment:

ILM FP1, powershell 1.0, exchange management console, exchange rollup 4

Reading from AD and writing to other AD management agent

My error:

The extensible extension returned an unsupported error in MIIS.

The stack trace is:

“Microsoft.MetadirectoryServices.ExtensionException: Could not find the default Administrative Group ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’.

at Exch2007Extension.Exch2007ExtensionClass.AfterExportEntryToCd(Byte[] origAnchor, String origDN, String origDeltaEntryXml, Byte[] newAnchor, String newDN, String failedDeltaEntryXml, String errorMessage)

Microsoft Identity Integration Server 3.3.0118.0″

For more information, see Help and Support Center at

HomeMDB is correct but when ilm try to update recipient is raised that error..

Before the proviosu error there is this error in event viewer :

Event Type: Error
Event Source: MIIServer
Event Category: None
Event ID: 0
Date: 15/10/2008
Time: 15.45.32
User: N/A
Computer: D1ILM
Description:
The description for Event ID ( 0 ) in Source ( MIIServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:

There is an error in Exch2007Extension AfterExportEntryToCd() function when exporting an object with DN CN=ProvaILM11,OU=ILM,…(hidden)…

Type: Microsoft.Exchange.Configuration.Tasks.ThrowTerminatingErrorException

Message: Could not find the default Administrative Group ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’.

Stack Trace: at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessUnhandledException(Exception e)
at Microsoft.Exchange.Configuration.Tasks.Task.BeginProcessing()
at System.Management.Automation.Cmdlet.DoBeginProcessing()
at System.Management.Automation.CommandProcessorBase.DoBegin().

The user become mailbox linked correctly if launch update recipient manually….I can’t understand why with ilm fp1 don’t work while manually work…(homeMDB is set by Exchange.CreateMailbox()) and even when launching update from powershell i use the same attribute

Thx for help.
Regards Luka.