Hi, Looking at the following scenario, can FIM assist? A user currently resides in an OU Chicago (based on their geographical location) and their mailbox is in the Chicago Exchange server. Assuming they are then moved to the Dallas office (so HR initiates the move and changes their location value in the HR application). Now I see that FIM can move the AD user object by simply changing the DN attribute. BUT how do we at the same time perform a move-mailbox routine from the Chicago server to the Dallas exchange server? Do we need to invoke some code? or is it as simple as changing the mailbox database DN ? thank you.

you need some code. changing attribute is not enough the simplest solution is to run powershell cmdlet from your custom WF-activity (as move-mailbox routine is asynchronous in exch10 for example)

thanks the customer currently has Exchange 2007 deployed - so custom code & powershell is the way to go. I hope it will not change much when they move to Exchange 2010.

it will, its different in exch2007 and exch10. one is synchronous and the other is not. even cmdlets are different.

you need some code. changing attribute is not enough the simplest solution is to run powershell cmdlet from your custom WF-activity (as move-mailbox routine is asynchronous in exch10 for example)

it will, its different in exch2007 and exch10. one is synchronous and the other is not. even cmdlets are different.

Hi S.Kwan, I believe Omada have a move mailbox MA, although I haven't used it. Cheers, MMS_guruIdentity & Metadirectory, Hewlett-Packard UK

it will, its different in exch2007 and exch10. one is synchronous and the other is not. even cmdlets are different. This is going to seriously back things up with Exchange 2007 doing this in a workflow. If I were you I'd think about exporting mailbox expected state to a SQL table using an MA and then have a Windows service monitor that table for changes and kick off mailbox moves in background threads.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

there's much more simple solution - send an email to exchange administrator that a user was transfered to another location and his mailbox requires attention :) ps. for the exch10 you don't need such a table - the process runs in the background and you can query for this request status from the powershell

there's much more simple solution - send an email to exchange administrator that a user was transfered to another location and his mailbox requires attention :) ps. for the exch10 you don't need such a table - the process runs in the background and you can query for this request status from the powershell

that is ridiculous oviously it would be very usefull to have FIM move the mailbox when a user moves from one location to another without the need to involve an exchange admin.

you can create a custom workflow that invoke powershell commands asynchronously. Dim runspace As Runspace = RunspaceFactory.CreateRunspace() runspace.Open() Dim pipeline As Pipeline = runspace.CreatePipeline() AddHandler pipeline.StateChanged, handler ..... pipeline.InvokeAsync() .... runspace.Close() in the statechanged handler check the pipeline state http://msdn.microsoft.com/en-us/library/system.management.automation.runspaces.pipelinestate%28v=vs.85%29.aspx