Article ID: 2479719 - View products that this article applies to.
An Active Directory administrator deploys the Microsoft Outlook 2010 or Microsoft Outlook 2013 policy Prevent copying or moving items between accounts. However, although the policy is applied to Microsoft Windows workstations, Outlook does not restrict users from copying or moving organization email messages to an Outlook Data (.pst) file or other email account.
The Outlook 2010 and Outlook 2013 Administrative Template files (ADM/ADMX/ADML) set the DisableCrossAccountCopy registry value by using the REG_EXPAND_SZ (expandable data string) data type. However, the DisableCrossAccountCopy registry value must be a REG_MULTI_SZ (multiple string) data type.
The organization's AD administrator can use the following information to deploy the DisableCrossAccountCopy registry value by using Group Policy:
Set Value data to one of the following three strings:
In Windows Server 2008 and Windows Server 2012 environments, you can use the Group Policy Registry preference extension to deploy registry settings. For more information about how to use the Registry preference extension to deploy the DisableCrossAccountCopy registry value, visit the following Microsoft TechNet website:
Note In a Windows Server 2003 environment, the registry change can be distributed by using a logon script. For more information about using a logon script to deploy a registry setting, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about the DisableCrossAccountCopy setting, visit the following Microsoft TechNet website:
Important If you are an Outlook user and are experiencing the behavior that is mentioned in the "Symptoms" section, contact the administrator for your organization. Any change that you make to the Policies hive of the registry will be overwritten by the organization's policy settings. Therefore, you must contact your administrator to have the necessary changes applied.
Article ID: 2479719 - Last Review: January 14, 2013 - Revision: 6.0
Contact us for more help