Hi

How about the solution on this kb

http://support.microsoft.com/kb/826210/en-us

• Click Start, and then click Control Panel.
• Double-click Administrative Tools, and then double-click Internet Information Services Manager.
• Expand Web Sites, right-click Default Web Site (or the site where your MCMS Web application is installed), and then click Properties.
• Click the Web Site tab.
• In the Connections section, in the Connection timeout box, increase the seconds to a value that is sufficient for the length of the import.
• Click OK.

Cheers

If you have any feedback on our support, please click here

Hi,
Since the source server is Exchange 2007, you need to run a RemoteLegacy moverequest.

Example:
New-Moverequest -id alias@souredomain.com -RemoteGlobalCatalog GC.souredomain.com -RemoteCredential (Get-Credential) -RemoteLegacy -TargetDeliveryDomain targetdomain.com

Thanks Martina

Using the RemoteLegacy option solved the issue.

However, Im running into another problem.

After the move, we can see the contact has been changed to a mailbox, so the move was OK.

Afterwards, I executed the command to add the remote forest user full access to the moved mailbox, using the Add-mailboxPermission command. ACLs are changed, and set to the correct remote user, according to the command output. But when using OWA or outlook, the remote user isnt able to use the mailbox. OWA says: something went wrong. Outlook says it cannot connect to the exchange server.

Thanks for the support.
Regards.
Peter

Hi Peter,
I don't understand why you ran add-mailboxpermission. Are you trying to give the source account permission to the target mailbox?

Prepare-moverequest.ps1 creates a disabled MailUser in Target without a password that is converted to a mailbox after the migration. It needs to be enabled and assigned a password. Did yo

Yes, youre right, the prepare-mailboxmove.ps1 creates a new disabled account. But we do not want to move the accounts. We want to grant the original user from the source forest access to his moved mailbox in the Exchange forest. If I enable the account in the Exchange forest and give it a password, the user in the user forest must than logon with his account of the Exchange forest, something we dont want.

thanks

Then I think that Linked Mailboxes will be something for you.
Add the parameter -LinkedMailUser when you run prepare-moverequest.

Thanks !!! It works !

Peter

Dear

Everything is working now. I executed  Export-AutoDiscoverConfig and the autodiscovery is now working fine for user in the user forest and their mailbox in the Exchange forest.

However, when a not yet migrated user test the autodiscovery, its also pointing to the exchange servers in the exchange forest and not to the local forest old Exchange servers.

Something else: although everything seems to work, when open the outlook profile settings from a migrated user, the server name has been replaced by a kind of GUID@aaa.be ??

Thanks for the feedback.
Regards.
Peter