We are having an annoying problem with Outlook 2010, which seems dependent on how Office 2010 Pro Plus is installed.
The problem relates to how users with existing Outlook 2010 Profiles are treated.
In all cases, Windows 7 Enterprise (32 bit) is in use, and the Office installation is customised from OCT. Also, in each case, tested with a user account who has a good/clean Windows 7 roaming profile, and previously used Outlook 2010, with cahced exchange mode enabled.
Scenario 1: Office installed as part of OSD Task sequence in SCCM 2007.
On logon, Outlook recognises profile of existing user and creats offline cache file in correct location, ie appdata\local\microsoft
Scenario 2: Office installed manually to PC using same install files as per config manager.
On logon, Outlook reports logging on for first time, then proceeds to ignore existing Outlook profile, creating a new one, and then puts the Offline cache (OST file) in the wrong location, ie Appdata\Microsoft <etc>
Scenario 3: Office installed using Dell's "imagedirect" service for Custom Factoriy Integration. Outlook behaves as per scenario 2.
Scenario 4: Manual install with modified custom MSP (from OCT), where Outlook Profile settings not configured, (instead of create profile option), results as per scenario 2.
In the scenarios where the existing outlook profile is ignored, it gets renamed and a new one created. Even then, i can't see where its picking up the settings to put the OST file in completely the wrong location. I've seen nothing in the MSP or Group Policy to indicate why its not using the default location (ie appdata\local), as putting it under appdata\microsoft means it counts against user profile quotas.
so... 1: how can we get outlook to behave as per when its installed via Config Manager OSD task sequence, 2: ensure outlook creates ost/offline cahce files in the correct location
Matt.