Just saw this pass through the forums, this is good news.
Issue:
Server name properties in Outlook 2003 profiles were being changed to an Instance-{GUID} value. This resulted in multiple issues within the Outlook 2003 client. In some extreme cases, clients would lose connectivity to Exchange entirely. In other cases, the clients would experience issues opening shared folders and calendars.
Update:
This issue is going to be corrected in the next cumulative update for Outlook 2003; there is no server-side fix necessary. This update is scheduled to be released towards the end of this month (February 2011). You will be able to download the update from the Microsoft Download Center, Office Update, or Microsoft Update. You can also look for the link when it is released at the Update Center for Microsoft Office, Office Servers, and Related Products.
IMPORTANT NOTE:
This fix will not correct existing profiles, it will only prevent this behavior from occurring in the future. To correct existing profiles, simply go into the profile where the Exchange Server name is specified, backspace out the last character of the name to “un-resolve” it, then type the last character again and hit “Check Name” to re-resolve the server. This is the same workaround, you can employ when encountering this issue today.
Discussion
No comments yet.