title | description | ms.date | ms.topic | author | ms.author | search.audienceType | ms.custom | tags | |
---|---|---|---|---|---|---|---|---|---|
Install, deploy, and upgrade Unified Service Desk | MicrosoftDocs |
Learn how to install, deploy, and upgrade Unified Service Desk, and also how to configure and deploy your agent application. |
06/27/2024 |
get-started |
gandhamm |
mgandham |
|
evergreen |
MigrationHO |
Before you can install and deploy [!INCLUDEpn_unified_service_desk_for_crm], you must identify the Microsoft Dataverse platform instance on which you want to build and deploy the configuration. While you can use a new Dataverse instance, [!INCLUDEpn_unified_service_desk] works best when Dataverse customization is mostly complete. [!INCLUDEpn_unified_service_desk] controls the call center agent’s view of Dataverse by manipulating windows, injecting [!INCLUDEpn_JavaScript], and so on. If major changes occur to Power Platform environment after [!INCLUDEpn_unified_service_desk] is deployed, it might cause your [!INCLUDEpn_unified_service_desk] configuration to no longer work as required. While the [!INCLUDEpn_unified_service_desk] configuration often comes later in Dataverse implementation, having [!INCLUDEpn_unified_service_desk] in mind when designing your Dataverse platform environment is useful.
[!INCLUDEpn_unified_service_desk] installation and deployment is done in phases where initially you set up a development environment to configure agent applications using one of the sample [!INCLUDEpn_unified_service_desk] applications as the base. Next, you test how your configurations appear and work using the [!INCLUDEpn_unified_service_desk] client application by connecting to Dataverse instance where you configured [!INCLUDEpn_unified_service_desk]. Next, you use the customized [!INCLUDEpn_unified_service_desk] configuration on to a Production instance of Dataverse, and the client application. The configuration includes the Customization Files package used to distribute any files and assemblies that are required to your agent’s computers.
Important
You can configure [!INCLUDEpn_unified_service_desk] to integrate with third-party line-of-business (LOB) applications. However, before deploying an integrated solution (involving [!INCLUDEpn_unified_service_desk] and LOB applications) in the production environment in your organization, you must thoroughly test your integrated solution to ensure that the performance results are aligned with your expectations. [!INCLUDEpn_unified_service_desk] might not function appropriately if integrated with LOB applications that demonstrate user interface (UI) blocking, memory leak issues, and slow response times.
Listed below is the sequence that we recommend for installing and deploying [!INCLUDEpn_unified_service_desk] in your organization. Before installing [!INCLUDEpn_unified_service_desk], ensure that you meet the system requirements: Unified Service Desk system requirements.
Identify a Dataverse server where you want to deploy [!INCLUDEpn_unified_service_desk] and a development computer that will be used for deploying [!INCLUDEpn_unified_service_desk] packages and then connecting to the packages by using the [!INCLUDEpn_unified_service_desk] client.
-
Install the [!INCLUDEpn_unified_service_desk] client on the development computer. [!INCLUDEproc_more_information] Install the Unified Service Desk Client
-
Deploy [!INCLUDEpn_unified_service_desk] packages to Dataverse instance. [!INCLUDEproc_more_information] Deploy Unified Service Desk packages using Package Deployer
-
Run the [!INCLUDEpn_unified_service_desk] client, and connect to Dataverse instance where you deployed the packages to verify that everything is working correctly. [!INCLUDEproc_more_information] Connect to a instance using the Unified Service Desk client
Set up additional development computers
To set up additional development computers for configuring your agent desktop applications using [!INCLUDEpn_unified_service_desk], install the [!INCLUDEpn_unified_service_desk] client on the computer. [!INCLUDEproc_more_information] Install Unified Service Desk Client
Use your development environment to configure your agent application by building on one of the available sample applications you deployed, and then test it by connecting to the customized package using the [!INCLUDEpn_unified_service_desk] client application. [!INCLUDEproc_more_information] Use Unified Service Desk to configure your agent application
After you have customized your agent application through configuration or custom code, you must install the [!INCLUDEpn_unified_service_desk] client application along with any files required for the custom functionality on your agent’s computers. Consider creating a [!INCLUDEpn_clickonce] application or an MSI package installer to bundle all the files together and deploy on the agent computers in your organization. [!INCLUDEproc_more_information] see MSDN: ClickOnce Security and Deployment or MSDN: Windows Installer
You might also want to migrate your [!INCLUDEpn_unified_service_desk] configuration from a development/test to a production environment. You can use the new [!INCLUDEpn_configuration_migration_tool] to migrate your [!INCLUDEpn_unified_service_desk] configuration data across Dataverse instance. [!INCLUDEproc_more_information] Migrate your Unified Service Desk configuration to another server
Unified Service Desk system requirements
Install Unified Service Desk Client
Deploy sample Unified Service Desk applications using Package Deployer
Connect to a instance using the Unified Service Desk client
[!INCLUDEfooter-include]