Outlook 2010 Security patch seems to kill vbscript on Enterprise Level

DAVID POWELL

Senior Member
Outlook version
Outlook 2010 32 bit
Email Account
Exchange Server
Diane,
The security patch(s)(KB3203467, KB4011196), OFFICE 2010, on vbscript behind outlook custom forms, seems like a killer for any application in place. with out the"hack" fixes"Unistalling", "Manual Registry Fixes"...

Is microsoft truly aware of what this is doing ?
Maybe i'm being a little to generic, but unless a company just simply ignores the patch, its kills the ability to run any code "vbscript" behind the form.
Just looking for an opinion.

Thanks
David Powell
 

Diane Poremsky

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
Yes, they are fully aware of what they did. If you set the registry keys, you can run forms... Custom Form Security Changes

i have a powershell script to add to the page that MS wrote to collect custom form names (for orgs that have a lot of forms).
 

DAVID POWELL

Senior Member
Outlook version
Outlook 2010 32 bit
Email Account
Exchange Server
Diane,
Thanks, but
That is my concern, I cant ask a multi-billion company to set "registry keys" on 7,000 machines.
and respectfully they will not install "powershell scripts".

Is Microsoft specifically, going to fix the issue.

Thanks
David Powell
 

Diane Poremsky

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
As far as I know, no they are not going to do anything to change the behavior. Developers whose products install custom forms can set the keys during installation.
 
Top