XADM: Outlook Profile Is Not Updated When You Move a User Between Virtual Servers on the Same Node (322986)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q322986 SYMPTOMS
After you perform a Moveuser operation in a two-node active/active clustered environment that has both Exchange 2000 virtual servers running on the same node, the Microsoft Outlook client profile is not updated during the first logon after the move. Outlook continues to work properly even though both virtual servers are running on the same node. However, if the originating virtual server is taken offline, the Outlook client cannot log on to the Exchange 2000 virtual server.
WORKAROUND
To work around this problem, initiate a failover of the Exchange virtual server to the default active/active configuration so that each Exchange 2000 virtual server is running on a separate cluster node.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. MORE INFORMATION
The Outlook profile is not updated during the first logon after a Moveuser operation only when both Exchange 2000 virtual servers are running on the same node. In a typical active/active configuration, where each Exchange 2000 virtual server is running on a separate node, the Outlook profile is updated automatically during the first logon after the Moveuser operation. However, the Outlook profile is not updated automatically during the first logon when either of the Exchange virtual servers are running on different nodes as a result of a fail-over operation.
| Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
|---|
| Keywords: | kbbug KB322986 |
|---|
|