05-25-2012 05:08 AM
Hello all,
Does anyone know:
In the desktop policy, advanced, you have this setting to ' Allow script in shared folder'. I have that set to Force On.
I have reports of users having a secondary mailbox, and they cannot open items from that mailbox. When using an Outlook profile with the 2nd mailbox only, items can be opened without issues. Investigation showed that in Outlook the setting in the Trust Center did NOT have the tick.
This is on Windows 7, Outlook 2010, EVClient 9.03 (latest hotfix with fix for SSL issue)
I've synced users mailbox again, and asked him to check again.
Does anyone know if this setting is applied on W7 with OL2010? Outlook is not in cached mode.EV=9Sp2
Thanks,
Gertjan
Solved! Go to Solution.
06-06-2012 06:11 AM
The team managing the GPO's have in all their wisdom set the following policies for OL2010:
Do not allow Outlook object model scripts to run for public folders Enabled
Do not allow Outlook object model scripts to run for shared folders Enabled
This will be changed to be 'disabled', so EV can set the proper values.
05-25-2012 05:15 AM
I have Outlook 2010 and Windows XP unfortunately, but it gets set properly on mine.
I'm taking it that in the log you have the following, right?
24/05/2012 21:04:51.708[9408][H]: ALLOWSCRIPTSHAREDFOLDERS = 1
24/05/2012 21:04:52.104[9408][L]: ~DesktopCommonConfig::LoadSettingsFromHiddenMessage: 0x0
24/05/2012 21:04:52.106[9408][M]: Desktop Setting: ALLOWSCRIPTSHAREDFOLDERS
24/05/2012 21:04:52.107[9408][M]: Value: 1
24/05/2012 21:04:52.108[9408][L]: ~DesktopCommonConfig::GetSetting: 0x0
24/05/2012 21:04:52.110[9408][M]: ALLOWSCRIPTSHAREDFOLDERS = 1 [Desktop Setting]
24/05/2012 21:04:52.112[9408][L]: ~DesktopCommonConfig::GetConfigValue: 0x0
Best guess is that its UAC or something security related, you could try running a procmon, but outlook registry keys like that are notorious for having "weird" names and being obscure so it might not be too obvious what to look for
05-25-2012 06:56 AM
I am investigating. Will post result on wednesday.
05-31-2012 03:43 AM
Investigated.
On users desktop (W7 and OL2010), in Trustcenter, emailsettings, the check before "allow script in shared folder' is not ticked, and greyed out. The EV policy does have allowscriptsharedfolders set to force on.
The logfile shows:
31/05/2012 09:47:51.467[5808][H]: ALLOWSCRIPTSHAREDFOLDERS = 1
which imho means that setting is distributed to the clients. I'm checking with AD team to see if they disable this in GPO.
06-06-2012 06:11 AM
The team managing the GPO's have in all their wisdom set the following policies for OL2010:
Do not allow Outlook object model scripts to run for public folders Enabled
Do not allow Outlook object model scripts to run for shared folders Enabled
This will be changed to be 'disabled', so EV can set the proper values.