G
gbrdevsi
Currently we use an Outlook Security Form from the Microsoft Office Resource Kit to change the registry to allow/disallow certain files to be sent in Outlook - i.e. .exe .lnk files. This was sufficient in OL2000. However, in OL2003, when a .lnk file is received and selected, a message appears asking if the user would like to Open or Save the attachment.
If the user selects Open, the following message appears:
"Windows cannot open this program because it has been prevented by a software restriction policy. For more information, open Event Viewer or contact your system adminsitrator."
The only option is to select Save from the original message to save the shortcut, and then open it from that location.
It appears that a registry key specifies the temporary location to save the shortcut attachment for viewing. This registry key is as follows:
HKEY_Current_User/Software/Microsoft/Office/11.0/Outlook/Security/OutlookSecureTempFolder
The data of this key shows as: C:\Documents and Settings\ebodington\Local Settings\Temporary Internet Files\OLK4\
When this path is amended to another folder that the user has access to, for example C:\Temp, the problem is resolved. Obviously if this fix is the only one available, it implies we will have to amend the registry for each machine in our network
If the user selects Open, the following message appears:
"Windows cannot open this program because it has been prevented by a software restriction policy. For more information, open Event Viewer or contact your system adminsitrator."
The only option is to select Save from the original message to save the shortcut, and then open it from that location.
It appears that a registry key specifies the temporary location to save the shortcut attachment for viewing. This registry key is as follows:
HKEY_Current_User/Software/Microsoft/Office/11.0/Outlook/Security/OutlookSecureTempFolder
The data of this key shows as: C:\Documents and Settings\ebodington\Local Settings\Temporary Internet Files\OLK4\
When this path is amended to another folder that the user has access to, for example C:\Temp, the problem is resolved. Obviously if this fix is the only one available, it implies we will have to amend the registry for each machine in our network