During a migration project to Exchange (from Lotus Notes), we installed Outlook using Online mode (because cached mode killed some of the WAN links as an entire mailbox was downloaded).  This was good in the short term but now a lot of users still have it enabled.

I would like to try and inventory the clients using SCCM to see if Outlook is running in cached mode or not. I have seen this article but the regkeys are not present on my PC so the script doesn't work: http://learn-powershell.net/2012/08/03/finding-the-cachedmode-setting-in-outlook-2010-using-powershell/, there were other articles saying the same kind of thing but none of them returned an accurate result.

I've tried to use Sysinternals tools to try and monitor which regkeys it uses when setting up a profile but as you can imagine there's a lot and trying to find the exact one is a pain.

Any ideas or pointers (preferably tested/verified) would be greatly appreciated.

Read here :

https://social.technet.microsoft.com/Forums/exchange/en-US/c8b06311-3036-4d51-a028-3ee58ac536fd/outlook-2010-cached-mode-registry-entry

All is explain here in detail and the reason why you can`t find your key.

But honestly i don't think this is something SCCM should be doing. This will have to run in the users context for sure. Would it be possible to do something with GPO either run the script or just set the value you want ?

Thanks for the link, that is one I hadn't read.

I want to avoid a GPO because I don't know how many computers on a site has it enabled/disabled - if it's a lot of computers then their computers will spend the rest of the year caching mails (possibly).

You're right question if it should be an SCCM thing or not - I was hoping to PowerShell it using DCM/Compliance into a WMI Key and see the data in HW reports, that's the ultimate goal if it's possible to inventory it at all. A script might work but again I want to avoid setting them all at the same time.

1.Well you could do a DCM with a powershell script. that would help you gather all the data. This would be good but i don't think you could have the powershell script run as the user.

2.You could make the script that validate the key and write back to a central location and deploy it using SCCM to the users.

3.You could also do a powershell script deploy like a logon script that write the info in a central location.

4.You could try using hardware inventory to inventory the regkey using the mof files (more complicated and would not suggest that)

The 2 option i would go with are 2 and 3

Hope this help get you started

Thanks for the ideas - I had a similar thought pattern but I need help to actually get this data out so that I can see the situation before I actually enable cached mode otherwise I could create a problem on at our remote locations.

I've never posted it, but I have a data collection script for this. I'll put it up on my blog this weekend. It's actually two scripts: one to create the WMI Class that runs with admin permissions and one to gather the info that users the logged on user's permissions.

Cheers Jason - that would be perfect.  I've subscribed to your blog so I'll keep an eye out for it but in case I miss it please can you update this thread?

/T

Hi,

Any update?

Hi,

So far I've not had any progress. Hopefully when Jason has some time he'll pose the solution he has mentioned because all the other things I have tried (suggested on this and other forum's) haven't worked.

Sorry, took me a little longer than I had planned to get back to this. They scripts are up now:

http://blog.configmgrftw.com/scripts-ftw/

The zip contains a readme with basic instructions.

Hi Jason,

Thanks for posting.  I managed to get the WMI Namespace & Class created (using the first script as an Admin), however when I run the second script as the user with an Outlook profile - it doesn't record any instances.

I am going to go through the second script to find out what it's looking for and to see if I can run the command manually (as the user) to see if anything is returned.

FYI - my mailbox is in Office 365 but I'm using the Office 2010 Outlook - which I don't think should be an issue because I assume that Outlook handles the settings in the same way, but I'll test with an on-prem user too.  I'll feedback as soon as I can find a willing victim.

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.