RE: Exchange upgrade- problem with Cached Mode setting

  • From: "Periyasamy, Raj" <Raj.Periyasamy@xxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 7 Mar 2005 15:56:55 -0500

When you upgrade to a new server, I assume you will be doing a move
mailbox method upgrade. In this case, you don't have to change the
profile manually. The profile will automatically reconfigure itself once
the mailbox is moved to the new server. Once you finish moving all
mailboxes, you can leave the old dns name in the DNS server pointing to
a DC. That will automatically resolve the correct names if any old
profiles tried to connect to Exchange. You never need any user
intervention if you use the move mailbox method for profile



-----Original Message-----
From: Jason Lehrhoff [mailto:JLehrhoff@xxxxxxxxxxxxxxxxxxxxxxxx] 
Sent: Monday, March 07, 2005 4:13 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange upgrade- problem with Cached Mode

i am doing an Exchange 2003 upgrade in a few weeks. I am having a
with an Office 2003 deployment that I pushed through the Custom
Installation Wizard/MST. The MST set users' Outlook so that cached mode
could not be chosen, and it became greyed out. I have since changed
(because I am now a fan of the cached mode)
The problem is, users that had that setting cannot change the cached
setting or the mail server (greyed out). This will be a problem when
upgrading to a new server (with new server name). My only workaround has
been to delete the user's Windows profile.
this tip was given to me but doesn't work:

if anyone overcame this obstacle, please let me know how.

thanks in advance.


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: