Microsoft Application Virtualization (App-V) is an application virtualization and streaming solution. With App-V, you can make applications available without installing the applications directly on end-user computers. You sequence the application so that it runs in its own self-contained virtual environment on the client computer. These applications can access data, system services, and configurations either locally or remotely.
This white paper describes how to set up the RoleTailored client and Classic client in Microsoft Dynamics NAV 2009 R2 to run as virtual applications in App-V. The App-V implementation is intended primarily for the RoleTailored client, but you may need to include the Classic client to run reports that you have not yet updated to the RDLC format.
For more information about App-V, including architecture requirements and installation and configuration instructions, see the Application Virtualization TechCenter on Microsoft TechNet.
App-V is supported for Microsoft Dynamics NAV 2009 R2 clients.
How App-V Works
App-V uses a workstation or terminal server to run an application without having to install the application on a client. Application files are not installed in the Program Files folder, and registry entries are not added. Instead, the application is loaded into an isolated virtual environment on the client.
In Microsoft Dynamics NAV 2009 R2, you can use App-V to deploy the RoleTailored client and Classic client to end users. The clients run on the end user’s computer and use that computer’s processor and memory, but they use remote systems to access data, system services, and configurations. App-V virtual applications are never installed on individual desktops, laptops, or terminal servers. Instead, virtual applications are located on a central App-V Server, and you manage them from the App-V console. Applications are deployed on demand to desktops, laptops, or terminal servers over the network when they are needed. The App-V deployment model supports running different versions of your Microsoft Dynamics NAV clients side by side, reduces the complexity of enterprise deployments, and supports transparent, dynamic client updates that require no end-user action.
The following illustration shows how client applications access data, system services, and configurations either locally or remotely.
How Administrators Deploy and Manage Microsoft Dynamics NAV with App-V
You perform the following general steps to deploy and manage Microsoft Dynamics NAV 2009 R2 with App-V.
| To | See |
|---|---|
|
Sequence the RoleTailored client and Classic client to use with App-V. |
|
|
Publish the sequenced client application so that end users can use Microsoft Dynamics NAV with App-V. |
In addition, you can also perform the following optional actions:
| To | See |
|---|---|
|
Extend functionality of the RoleTailored client with RoleTailored client control add-ins. |
How to: Add Add-ins to an App-V-Sequenced RoleTailored Client |
|
Make changes and publish the updated client application. |
|
|
Apply hotfixes to Microsoft Dynamics NAV and redeploy the sequenced application. |
How End Users Run Microsoft Dynamics NAV with App-V
You can configure App-V-packaged clients so that end users run them from either a desktop icon or the Start menu.
When end users run the RoleTailored client, the ClientUserSettings.config file is created in the user's AppData folder. Changes to this file are saved and persisted. The file is not overwritten when the user opens the package again or when an updated package is downloaded.
When end users run the Classic client, they must have access to the Microsoft SQL Server instance that hosts the Microsoft Dynamics NAV database.