Good afternoon. We have an exchange 2010 server that was configured at head office (mailbox, hub transport, cas) and has been running here for roughly 6 months without an issue with the intent to move it to a new large branch we were opening up. The short story is after moving this machine to the new location, which in turn put it into a new AD site, the submission queue was filling up complaining about users mailboxes not being in the same site as their AD user object (I apologize I never got the exact error message, but I can get it if need be). To remedy this situation temporarily I "tricked" the server into thinking it was still in the head office AD site by adding the SiteName registry key to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters. After a reboot the queue cleared and things have been working fine. I tried restarting the hub transport services on the head office exchange servers and removing the registry entry, but the issue persisted. Searching on this has been rather dry, so im hoping some experts here might have an idea what the problem is. Thanks in advance for any suggestions.

Can you post the exact errors in the event logs? I would run ExBpa against the server as well. I assume the mailboxes its trying to deliver to are also homed on that server? Any anti-virus or other 3rd party software running on the server?

Hi Derek_M Per your description, how do you do the mirgration, you can post the detailed the information about your scenario here. As we know, there is a attribute named site membership of the exchange server, and will be used when the message was delivered, please refer to below: http://technet.microsoft.com/en-us/library/aa996299.aspx Some related discussion: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/5c8f62bd-01ac-407a-bd76-874c2eb4bbf4 http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/5c8f62bd-01ac-407a-bd76-874c2eb4bbf4 Regards! Gavin