NBF
asked on
Update office 2007 configuration with new .msp not working. Cached Exchange mode/profile creation issues
1ST PROBLEM...
We deployed office 2007 using an .MSP file. We did not disable cached exchange mode. We edited the .msp file and changed it so that it sets the default behavior for cached exchange mode to disabled. We did this by selecting, "Configure Cached Exchange Mode" and unchecking "Use Cached Exchange Mode."
It is my understanding that this will disable cached exchange mode by default so that it would need to be manually turned on in the profile.
If I just double click the new .msp file and run it and check the event log it shows as completed successfully but afterwards if I try to create a new mail profile manually cached exchange mode is turned on by default. I have to manually go in to the profile and turn it off after creation.
It does not appear that rerunning the edited .msp resolves the issue.
ALSO, 2ND Problem....
I also have "Configure an Exchange Server Connection for new or existing profiles" selected and have set %username% as the username and the exchange server name for the server. I also checked "Overwrite Existing Excahnge settings if an exchange connection exists." I also have Modify Profile selected to modify the default profile with these settings.
For some reason when I try to create a new profile or it tries to autocreate if none exists it gets stuck on the server name and cannot make a connection. The MS Exchange Server name field gets populated with this: /O=xxxxxx xx/OU=MIL/cn=Configuration
We deployed office 2007 using an .MSP file. We did not disable cached exchange mode. We edited the .msp file and changed it so that it sets the default behavior for cached exchange mode to disabled. We did this by selecting, "Configure Cached Exchange Mode" and unchecking "Use Cached Exchange Mode."
It is my understanding that this will disable cached exchange mode by default so that it would need to be manually turned on in the profile.
If I just double click the new .msp file and run it and check the event log it shows as completed successfully but afterwards if I try to create a new mail profile manually cached exchange mode is turned on by default. I have to manually go in to the profile and turn it off after creation.
It does not appear that rerunning the edited .msp resolves the issue.
ALSO, 2ND Problem....
I also have "Configure an Exchange Server Connection for new or existing profiles" selected and have set %username% as the username and the exchange server name for the server. I also checked "Overwrite Existing Excahnge settings if an exchange connection exists." I also have Modify Profile selected to modify the default profile with these settings.
For some reason when I try to create a new profile or it tries to autocreate if none exists it gets stuck on the server name and cannot make a connection. The MS Exchange Server name field gets populated with this: /O=xxxxxx xx/OU=MIL/cn=Configuration
ASKER
There is no GPO to configure cached exchange mode only customer experience program disable.
According to technet the following setting disables cached exchange mode in the .msp editor.
Select the Use Cached Exchange Mode check box to enable Cached Exchange Mode for users. By default, Cached Exchange Mode is disabled if you do not select the check box but you do select Configure Cached Exchange Mode.
I have UNCHECKED the use cached excahgne mode check box and selected CONFIGURE CACHED EXCHANGE MODE just as suggested. It just does not flat out work.
I tested on a brand new installation. I even tried with SP2 slipstreamed in to the installation. I have also tried to rerun the .MSP file after the install and no matter what I do, when I create a new outlook profile for an exchange mailbox, I have to go back in to the profile and manually uncheck the cached mode setting because it is on by default.
Any other suggestions?
According to technet the following setting disables cached exchange mode in the .msp editor.
Select the Use Cached Exchange Mode check box to enable Cached Exchange Mode for users. By default, Cached Exchange Mode is disabled if you do not select the check box but you do select Configure Cached Exchange Mode.
I have UNCHECKED the use cached excahgne mode check box and selected CONFIGURE CACHED EXCHANGE MODE just as suggested. It just does not flat out work.
I tested on a brand new installation. I even tried with SP2 slipstreamed in to the installation. I have also tried to rerun the .MSP file after the install and no matter what I do, when I create a new outlook profile for an exchange mailbox, I have to go back in to the profile and manually uncheck the cached mode setting because it is on by default.
Any other suggestions?
ASKER
By there is no GPO I mean we have no Office 2007 GPOS configured other than disabling RSS and Cust Imp Program.
ASKER
I have further information that is promising but I still cannot figure out the issue.
If I use a fresh AD account with no existing profile on the PC and attempt to launch Outlook it automatically creates the profile propery by connecting to exchange and it sets cached exchange mode to disabled.
HOWEVER, If i then go and delete the profile so that there are no mail profiles and try to launch Outlook again it does NOT autoconnect to the exchange server and create the profile. It gets hung up and displays the following string in the exchange server connection box: /O=xxxxxx xx/OU=MIL/cn=Configuration
So it appears my two issues are related. If a user is able to automatically create a profile without any issues then cached exchange mode is turned off. However if the user needs a 2nd profile for a different account or we need to delete the profile for some reason it won't automatically generate a new profile.
Something appears to be left in the users profile after creating an outlook profile even after deleting it that prevents further successful automatic exchange profile creations.
If I use a fresh AD account with no existing profile on the PC and attempt to launch Outlook it automatically creates the profile propery by connecting to exchange and it sets cached exchange mode to disabled.
HOWEVER, If i then go and delete the profile so that there are no mail profiles and try to launch Outlook again it does NOT autoconnect to the exchange server and create the profile. It gets hung up and displays the following string in the exchange server connection box: /O=xxxxxx xx/OU=MIL/cn=Configuration
So it appears my two issues are related. If a user is able to automatically create a profile without any issues then cached exchange mode is turned off. However if the user needs a 2nd profile for a different account or we need to delete the profile for some reason it won't automatically generate a new profile.
Something appears to be left in the users profile after creating an outlook profile even after deleting it that prevents further successful automatic exchange profile creations.
Copy your MSP file and remove the Configure an Exchange Server Connection for new or existing profiles" portion of the Admin setup for the MSP.
Don't specify exchange server settings, Add accounts, Remove Account and export settings, specify send/ receive groups.
Then test your MSP with " use existing profile" settings.
*** If I recall correctly, this was an issue with the tool and when creating the profile, it would automatically put the profile into cachemode.
Don't specify exchange server settings, Add accounts, Remove Account and export settings, specify send/ receive groups.
Then test your MSP with " use existing profile" settings.
*** If I recall correctly, this was an issue with the tool and when creating the profile, it would automatically put the profile into cachemode.
ASKER
Thank you for the suggestion. I will let you know my testing results this afternoon.
ASKER
Thats actually no good. If I do that then new users would have to manually create a profile for themself. That exchange configuration section is very important for that functionality.
If you are running Exchange 2007, it will auto create it. If you are running exchange 2003, it will prompt to auto create it with two clicks.
Wdat is your configuration and have you tried it yet?
If you are 03, I can probably provide you with some reg keys or ADM files you can GPO outlook into Online mode and not cache mode.
Wdat is your configuration and have you tried it yet?
If you are 03, I can probably provide you with some reg keys or ADM files you can GPO outlook into Online mode and not cache mode.
ASKER
We have 2003 Exchange. We will be moving to 07 later this year. its not a huge problem just an annoyance at this point that will probably go away with the implementation of exchange 07 and autodiscover.
I am about to test your suggestion with a modified .msp.
I am about to test your suggestion with a modified .msp.
OK - let me know if you need more tricks to work around 2003.
ASKER
I did as you suggested and completely disabled the settings for profiles and exchange. I fully removed office and reinstalled using the .msp.
Same behavior.
The first time a profile is created automatically it finds the exchange server and connects automatically and leaves cached mode off. If I then delete the mail profile and open outlook again it gets stuck trying to communicate with the exchange server to create a profile. If I clear out the string in the connection box and just type in the name of the exchange server it works but it still sets up the profile with caching turned on.
Cached exchange mode is still being turned on by default when creating a new profile after one has already been created even if you delete it. Using MAIL in control panel produces the same behavior.
Stumped again...
I am seeing the same behavior on both vista and xp with office 2007. Its like running the new .MSP does not make the configuration changes even though the event log says it runs successfully. Even a new fresh installation has the same behavior...
Same behavior.
The first time a profile is created automatically it finds the exchange server and connects automatically and leaves cached mode off. If I then delete the mail profile and open outlook again it gets stuck trying to communicate with the exchange server to create a profile. If I clear out the string in the connection box and just type in the name of the exchange server it works but it still sets up the profile with caching turned on.
Cached exchange mode is still being turned on by default when creating a new profile after one has already been created even if you delete it. Using MAIL in control panel produces the same behavior.
Stumped again...
I am seeing the same behavior on both vista and xp with office 2007. Its like running the new .MSP does not make the configuration changes even though the event log says it runs successfully. Even a new fresh installation has the same behavior...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Will it turn cache mode off for all profiles of all users currently on the machine?
What is the reg key I need to change/add? I am comfortable applying it via the .msp(if that even works, kind of disappointed right now) or GPOs.
What is the reg key I need to change/add? I am comfortable applying it via the .msp(if that even works, kind of disappointed right now) or GPOs.
Let me gather those for you, in the meantime, I would suggest this autodiscovery configuration while you remain under Exchange 2003:
ADM settings for a GPO:
CATEGORY "[HKEY_CURRENT_USER\Softwa
KEYNAME "Software\Microsoft\Office
POLICY "ZeroConfigExchange"
PART "ZeroConfigExchange"
NUMERIC
VALUENAME "ZeroConfigExchange"
END PART
END POLICY
END CATEGORY
ADM settings for a GPO:
CATEGORY "[HKEY_CURRENT_USER\Softwa
KEYNAME "Software\Microsoft\Office
POLICY "ZeroConfigExchange"
PART "ZeroConfigExchange"
NUMERIC
VALUENAME "ZeroConfigExchange"
END PART
END POLICY
END CATEGORY
Take a peek at this as well:
http://www.experts-exchang
http://www.experts-exchang
ASKER
GW do you have a way to reverse that GPO that disables autodiscovery for when we do move to exchange 07?
All you need to do is just change the value when you move to Ex07
Do you have a group policy enabled which could be tatooing the registry for cachemode?