Install Microsoft Dynamics 365 for Outlook for desktop virtualization
This topic describes how to install Dynamics 365 for Outlook with roaming user profiles by using Windows ServerRemote Desktop Services. Remote Desktop Services, formerly Terminal Services, is a server role in Windows Server that provides technologies that enable users to access session-based desktops, virtual machine-based desktops, or applications in the data center from both within a corporate network and from the Internet.
Roaming user profiles
A roaming user profile is a copy of the local user profile that is copied to, and stored on, a server share. The advantage of roaming user profiles is that users do not have to create a profile on each computer that they use on a network. Their profile is downloaded to each computer that they log on to on a network. Changes made to a roaming user profile are synchronized with the server copy of the profile when the user logs off.
While the roaming user profile moves with the user, software applications such as Dynamics 365 for Outlook do not. Identical applications have to be installed on each computer that the user logs on to.
Windows Server Remote Desktop Services
Dynamics 365 for Outlook is supported for running on Windows Server 2012Remote Desktop Services. When users run an application on Remote Desktop Services, the application execution occurs on the server. Only keyboard, mouse, and display information are transmitted over the network. Users see only their own individual sessions, which are managed transparently by the server operating system and remain independent of any other client session.
More information: Remote Desktop Services
Deploy Dynamics 365 for Outlook to use as a Remote Desktop Services application
The following is the basic procedure required to deploy Dynamics 365 for Outlook to use as a Remote Desktop Services application.
Provide at least one Microsoft Windows Server that is running the Remote Desktop Services server role. More information: Remote Desktop Services
Install Dynamics 365 for Outlook using the /disableofflinecapability parameter on the Remote Desktop Services server. Go offline mode is not supported when Dynamics 365 for Outlook is installed for Remote Desktop Services use. More information: Install Microsoft Dynamics 365 for Outlook using a Command Prompt
The Dynamics 365 for Outlook offline database is not supported for roaming profile use.
Run the Dynamics 365 Configuration Wizard on the Remote Desktop Services server. For instructions, see Install Dynamics 365 for Outlook.
Disable the Dynamics 365 Configuration Wizard on all desktops that will be used to connect to Remote Desktop Services and run Dynamics 365 for Outlook. For details, see the section below.
Disable the Dynamics 365 for Outlook Configuration Wizard
The information in this topic applies to Dynamics 365 for Outlook deployments that use Remote Desktop Services. To remove only the Get Dynamics 365 for Outlook button for Dynamics 365 for Outlook deployments that don’t use Remote Desktop Services, see the “Set whether users see Dynamics 365 for Outlook message” setting in System Settings dialog box - Outlook tab.
The Dynamics 365 for OutlookConfiguration Wizard starts every time a roaming user connects to a Windows Server that is running Remote Desktop Services. In addition, users will see the option to configure Dynamics 365 for Outlook when they run Office Outlook.
Instead of manually creating the registry key as described here, you can use Group Policy or a logon script to create the registry key for the Remote Desktop Services users who do not use Dynamics 365 for Outlook.
Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system and Microsoft Dynamics 365. We can’t guarantee that these problems can be resolved. Modify the registry at your own risk.
To disable the Dynamics 365 for OutlookConfiguration Wizard and the option to configure Dynamics 365 for Outlook, follow these steps on the client computer.
Disable the Configuration Wizard
On the computer where Microsoft Office is installed, start Registry Editor (regedit.exe).
Locate the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins
Right-click Addins, point to New, and then click Key.
crmaddin.Addin, and then press ENTER.
Right-click crmaddin.Addin, point to New, and then click DWORD Value or DWORD (32-bit) Value.
LoadBehaviorand then press ENTER.
Right-click LoadBehavior, and then click Modify.
8in the Value Data box, click Decimal, and then click OK.
Exit Registry Editor.
Support for Citrix XenApp 6.5 and 7.0-7.18 session virtualization for Microsoft Dynamics 365 for Outlook on a single XenApp instance
Microsoft will support Citrix XenApp 6.5 and 7.0 -7.18 with session virtualization for Dynamics 365 for Outlook on a single XenApp instance.
Please note that Citrix deployment may include a complex configuration topology based on other configurations, and these are not supported. For example, these configurations are not supported:
Citrix products like XenApp (except for versions 6.5 and 7.0-7.18), XenDesktop, and XenServer and versions of these products
Application streaming modes
Modes of application deployment
Application virtualization layered on top of other virtualization technologies (such as Network and storage virtualization technologies)
Cached Exchange Mode turned off in Outlook is supported if Dynamics 365 for Outlook syncs with Customer Engagement using server-side synchronization but not supported if Dynamics 365 for Outlook syncs with Dynamics 365 for Outlook synchronization. See: Turn on Cached Exchange Mode.
Install or upgrade language packs for Microsoft Dynamics 365 for Customer Engagement apps
Planning and installing Dynamics 365 for Outlook for Microsoft Dynamics 365 for Customer Engagement apps and Dynamics 365 for Customer Engagement apps Online
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.