User receive the following prompt stating that a program is trying to access e-mail addresses you have stored in Outlook. do you want to allow this?
Go to http://www.microsoft.com/office/orkarchive/2003ddl.htm and search for “ork.exe” for Office 2003 and install the same. After installation of the resource kit, you will need to run the “admpack.exe” to install the administrator pack on your computer. You can find the “admpack.exe” at c:\program files\ORK tools\ORK11\Tools\Outlook Administrator Pack.
The administrative tools for the Outlook Security features consist of four files, packaged into one self-extracting executable.
OutlookSecurity.oft is an Outlook template that enables you to customize the security settings on the Microsoft Exchange server. The template does not actually implement security — it is simply the storage location for the customized security settings
Install and Register the Trusted Code Control:
• Hashctl.dll is the file for the Trusted Code control, a tool used by the template to specify trusted COM add-ins.
• Comdlg32.ocx is a file used for the Trusted Code control. It provides a user interface for selecting the trusted COM add-in.
• Copy Hashctl.dll and Comdlg32.ocx to c:\windows\system32 on your administrator computer
• From Start and Run type… Regsvr32 hashctl.dll to register the file
• From Start and Run type… Regsvr32 Comdlg32.ocx to register the file
Creating a public folder for the security settings:
1. Before modifying the security settings, you must create a public folder named “Outlook Security Settings” on the Microsoft Exchange server on which you keep public folders. You create this folder by using one of those names exactly, in the root folder of the Public Folder tree. You must set the folder access control lists (ACLs) so that all users can read all items in the folder. However, only those users for whom you want to create or change security settings should have permission to create, edit, or delete items in the folder.
To use the Outlook Security template to modify settings on Exchange Server :
1. On a computer running Outlook 2007, open OutlookSecurity.oft from the working directory where you installed the Outlook security tools. You need to do this by going to Tools > forms > select a form .
Note: Outlook 2007 blocks *.OFT files by default
2. Once the from loads you will be prompted to select a folder, select the “Outlook Security Settings” that you created on Exchange Server. The template will then open in Compose mode.
3. On the Tools menu of the template, point to Forms, and then click Publish Form. (The folder selected should be your current folder—Outlook Security Settings.)
4. In the Form Name box, type Outlook Security Form.
5. Click the Publish button to publish the security template in the Security Settings folder.
You can now close the Outlook Security template. Do not save when prompted to save while closing the template.
6. Switch to Microsoft Outlook, click the drop-down arrow next to the New button on the toolbar, and select the Choose Form from the list.
7. Navigate to the template you just created in the previous steps then select the new template name and click the Open button.
8. Select Default Security Settings for All Users on the “Outlook Security Settings” tab.
9. Access the “Programmatic Settings” tab and set all or required options to “Automatically approve”
10. After you configure these settings, you must enable the customized settings for your users. To enable the changed settings, you may need to deploy a new registry key to the client computers.
11. Start the registry editor and expand the following subkey:
12. From the Edit menu, choose New, then click DWORD value to add a new registry key. The value name for the key must be AdminSecurityMode.
13. The value of the registry key should be set to 1.
14. Click Close on the form and if prompted, click Yes to save the form.
15. Restart the client computer and check
Also if we need to exclude user you’ll need to add them to the exception list in the Outlook security form
Once we enabled this function, all the application including AX will send email directly which may cause the security problem. Another solution is to do some programming in Dynamics AX. Please check MSDN (http://msdn.microsoft.com/en-us/library/aa851352(AX.10).aspx) for more details on the AX programming.