In AppDNA
In All products
Product Documentation
In AppDNA
In All products
AppDNA Current Release AppDNA 7.15
View PDF

Migrate Windows applications to App-V 5.0

Aug 14, 2017

This topic explains the steps required to use AppDNA to migrate your Microsoft Windows applications to Microsoft App-V 5.0 or from Microsoft App-V 4.6 to 5.0.

Get started

To start making decisions about the Citrix model that provides the best fit for your applications, perform each of the following steps.

Step 1

Discover your applications

To prevent unexpected delays in the migration plan, you must discover which applications are being used in your environment. Use the integration features within AppDNA to discover applications being used in your environment (Lakeside Software SysTrack) and to import your managed applications using the installation media that has been used to deploy them through Active Directory (AD) or Microsoft System Center Configuration Manager (Configuration Manager) integration.
Step 2

Perform inventory and rationalization

To perform an inventory and rationalization of the Windows applications used in your enterprise, use tools such as Lakeside SysTrack. It’s important to monitor the environment over a 6 week to 2 month period at quarter and/or year end. This will not only identify any unmanaged applications which could be critical to business, but also tells you what applications are still being used, and whether you have duplicate applications with overlapping functions.
Step 3

Prepare your AppDNA environment

Setup and configure the AppDNA environment as outlined in the next section of this topic. This includes setting up the AppDNA and configuring it for use with the AppDNA Forward Path feature and AppDNA Execution Profile scripts used for the suggested solution.

The AppDNA Forward Path feature is a powerful business decision engine that is built into AppDNA and makes it possible to model different deployment scenarios and compare their impacts.
Step 4

Locate source media

You can directly import MSI and App-V (SFT, APPV) files.

Non-MSI files require the AppDNA Install Capture feature, which uses a virtual machine to capture the application into an MSI.

The AppDNA Self-Provisioning tool can also be used to capture non-MSI files. Self-Provisioning allows the capture process to be driven by an application expert who does not have access to AppDNA. The AppDNA administrator prepares and publishes control information that enables the application expert to perform the installation. The capture takes place on a separate machine (virtual, physical, or VDI) from AppDNA.
Step 5

Import AD and/or Configuration Manager data

To import your managed applications using the installation media that has been used to deploy them through Active Directory (AD) and System Center Configuration Manager (Configuration Manager), first load your AD and Configuration Manager data into AppDNA using the Load AD and ConfigMgr Data wizard.

Decide whether to load the data directly or indirectly. You have the option to load AD and Configuration Manager data indirectly which enables the data to be extracted on the AD domain controller or Configuration Manager server separately from AppDNA. As a result, AppDNA users do not need to request administrator access to the AD and Configuration Manager data, plus the AD domain and Configuration Manager administrators do not need to install AppDNA.

Note: For best results, import both AD and Configuration Manager data. Typically AD provides rich data about organizational structure and Configuration Manager provides data about applications that are managed centrally.
Step 6

Choose the appropriate scenario

For Windows applications that are already sequenced using Microsoft App-V 4.6, follow the process using the Microsoft App-V 4.6 to App-V 5.0 Decision forward path script.

For Windows applications that are already imported into Citrix AppDNA, or applications that have not been sequenced or imported into Citrix AppDNA, follow the process using the Microsoft App-V 5.0 Decision forward path script.
Step 7

Use the AppDNA reports

Reports for migration of Windows applications to App-V 5.0, later in this section, guides you through the reports that you’ll need to help you make decisions. It also covers the Forward Path scripts, which simplify decision making by modeling your business needs, providing solutions, and enabling you to automate the desired output for compatible applications, such as App-V 5.0 sequences and MSIs.
Step 8

Manage ongoing application evolution

As new applications enter the environment and as new service packs, patches and upgrades impact the environment, use AppDNA to manage and model the changes that affect applications and end users.

AppDNA configuration

Follow these steps to configure AppDNA for the migration of Windows applications to App-V 5.0.

Step 1

Create groups to organize applications by priority

Create AppDNA groups to organize the applications accordingly. This can be by priority or business unit. Once your group is created and applications are imported and analyzed, you can use the group to determine priority within the group based on the complexity of the problems encountered.
Step 2

Request access to AppDNA scripts

Citrix has a library of non-supported Forward Path and Execution Profile scripts that are available for download. The scripts are customized to model business decisions around applications and to automate processes (such as Microsoft App-V 5.0 application sequences and MSIs).

This solution uses an execution profile script that ships with AppDNA as well as the following scripts which are available for download:

  • [EP] Converter_App-V4.6_to_App-V5.0
  • [FP] Microsoft App-V 4.6 to App-V 5.0 Decision

  • [FP] Microsoft App-V 5.0 Decision

To access the scripts, set up a Podio account and send an email to appdnafeedback@citrix.com requesting access to the AppDNA Extensions Podio site.
Step 3

Create a VM for Install Capture (non-MSIs) and Forward Path automation

Create a Virtual Machine on supported technology to use with Install Capture and Forward Path. The VM should use the same operating system that the applications run on.

Install Capture is used as part of the import process to install and capture non-MSI applications before importing the application DNA into the AppDNA database.

Forward Path is used to determine outcomes for applications and automate processes, such as to convert Microsoft App-V 4.6 sequences to Microsoft App-V 5.0 or create Microsoft App-V 5.0 sequences using MSI/EXE source media. The virtual machine should use the operating system that you are moving to.
Step 4

Configure a VM for capturing non-MSIs and Forward Path Automation

Review the general overview of the AppDNA Install Capture setup requirements. At the end of that overview are links to each of the following virtualization technologies. The details for configuring your VM vary depending on the underlying virtualization technology:

  • XenServer
  • Hyper-V
  • Microsoft Virtual Server
  • vSphere
  • VMware Workstation
  • VMware Server

The virtualization technology topics include instructions for creating a shared output folder. Additional folder configuration is required when using the Microsoft App-V 4.6 to Microsoft App-V 5.0 Execution Profile:

  1. On the host machine, create a source folder location that the VM has full access to, such as, \\xxx.xxx.xx\AppDNA_Output\AppV_Convert (no spaces).

  2. Within the location created above, create one folder for each application, including the application’s OSD and SFT files.

    This will be your Source Folder that must be defined in the Replaceables tab of the execution profile: \\xxx.xxx.xx\AppDNA_Output\AppV_Convert.

  3. Also create a subfolder, such as v5, to be the Target Folder: \\xxx.xxx.xx\AppDNA_Output\AppV_Convert\v5.
Step 5

Install Required Software on Virtual Machine

Install the software on the virtual machine that will be used to automate converting Microsoft App-V 4.6 sequences to Microsoft App-V 5.0 and to create Microsoft App-V 5.0 sequences.

  • Microsoft App-V 5.0
  • PowerShell 3.0
Step 6

Import Microsoft App-V 5.0 Sequencer Execution Profile into AppDNA

To import the App-V 5.0 Sequencer execution profile script into AppDNA:

Note: App-V 5.0 Sequencer.xml is installed by default to C:\Program Files\Citrix\AppDNA\Client\Execution Profiles or C:\Program Files (x86)\Citrix\AppDNA\Client\Execution Profiles.
  1. Log on to AppDNA and then choose Edit > Settings.
  2. In the Settings dialog box, click Install Capture.
  3. Click the Execution Profile tab.
  4. Click Import (in the lower part of the dialog box).
  5. In the Load Profiles dialog box:
    1. Browse to the location of the execution profile file downloaded from Podio.
    2. Select the execution profile file that you want to activate and then click Open.
Step 7

Download Forward Path Scripts and Execution Profiles

From the AppDNA Extensions Podio site:

  1. Click the Extensions button at the top of the page.
  2. Click [EP] Converter_App-V4.6_to_App-V5.0.
  3. Under Files, right-click the latest version of [EP] Converter_App-V4.6_to_App-V5.0.xml, select Save target as…, and then save the file to your local machine.
  4. Go back to the list of extensions and click [FP] Microsoft App-V 5.0 Decision.
  5. Under Files, right-click the latest version of [FP] Microsoft App-V 5.0 Decision.xml, select Save target as…, and then save the file to your local machine.
Step 8

Import Microsoft App-V 4.6 to Microsoft App-V 5.0 Execution Profile into AppDNA

Import the Microsoft App-V 4.6 to App-V 5.0 Converter execution profile script downloaded from Podio into Citrix AppDNA:

  1. Log on to AppDNA and then choose Edit > Settings.
  2. In the Settings dialog box, click Install Capture.
  3. Click the Execution Profile tab.
  4. Click Import (in the lower part of the dialog box).
  5. In the Load Profiles dialog box:
    1. Browse to the location of the execution profile file downloaded from Podio.
    2. Select the execution profile file that you want to activate and then click Open.
    3. In the Execution Profiles tab, click the imported execution profile, click the Edit button, and then click the Replaceables tab.
    4. Select the SourceFolder location replaceable, click the Edit button, enter the path to the Source files (such as \\xxx.xxx.xx\AppDNA_Output\AppV_Convert), and then click OK.
    5. Select the TargetFolder location replaceable, click the Edit button, enter the path to the Target folder (such as \\xxx.xxx.xx\AppDNA_Output\AppV_Convert\v5), and the click OK.
    6. Click Save to preserve your changes and then close the Settings dialog box.
Step 9

Import Forward Path Scripts into AppDNA

To import the downloaded Microsoft App-V 4.6 to App-V 5.0 Decision and/or Microsoft App-V 5.0 Decision forward path script into AppDNA:

  1. Log on to AppDNA and then choose Configure > Forward Path.
  2. In the Forward Path Logic Editor screen, click the Import button.
  3. Browse to the downloaded forward path script, select it, and click Open.
  4. Click Import.
  5. Click OK in the message that the file has been successfully imported.
Step 10

Configure Forward Path Scripts:

Microsoft App-V 4.6 to App-V 5.0 Decision

Microsoft App-V 5.0 Decision

These forward path scripts check the compatibility of applications against Microsoft App-V and Windows 7. There are 8 task scripts assigned to both Forward Path scripts taking into account options to automate the creation/conversion of App-V sequences on both Windows 7 x64 and x32.

To configure the scripts to match your AppDNA environment:

  1. Log on to AppDNA and then choose Configure > Forward Path.
  2. In the Scenarios tab, click Microsoft App-V 4.6 to App-V 5.0 Decision or Microsoft App-V 5.0 Decision.

  3. Click the Editor tab to view and edit the scripts.

    You can edit the scripts to reference a different operating system or to make other changes to meet the needs of your environment.

  4. To change the operating system referenced, use the Property Explorer tab on the right side of the window.

    Expand Applications > Modules to see a list of operating systems and how they should be referenced. Replace references to Windows7 with the desired operating system.
Step 11

Configure Task Scripts

The forward path scripts you downloaded and imported have eight task scripts assigned to them to enable you to automate the creation of Microsoft App-V 5.0 sequences or conversion of Microsoft App-V 4.6 to Microsoft 5.0 sequences. The task scripts need to be configured to reference your Citrix AppDNA virtual machine name and the execution profile that should be used to automate the process.

To configure a Forward Path Task Script:

  1. In the Scenarios tab, expand the Forward Path script node that you want to edit.

    You will see the contents of the selected task script in the Editor tab. There is a task script enabling you to automate the Microsoft App-V process for both Windows 7 32-bit and 64-bit. You can delete any task scripts you don’t plan to use.

  2. Scroll down to line 21. The task scripts are already populated with the execution profiles to be used, such as 'App-V 5.0 Sequencer' for the Microsoft App-V 5.0 Decision.

    Example:

    ProductionManager.RunExecutionProfile(controller, "Execution Profile Name", replaceables, "Default VM Configuration")

    Change to:

    ProductionManager.RunExecutionProfile(controller, "App-V 5.0 Sequencer", replaceables, "Your VM Name as shown in Install Capture Settings")

  3. To verify the name of your virtual machine, go to Edit > Settings from the AppDNA menu. In the left pane, select Install Capture. Use the name displayed in the Name column on the Virtual Machine tab.
  4. Click Save to save the changes.
  5. Repeat for each task script.

Reports for migration of Windows applications to App-V 5.0

The following table lists the reports required for the migration of Windows applications to App-V 5.0. These reports will provide the data you need to help with decision making.

To access the reports, click Reports: Applications in the side bar.

Reports Description

Forward Path

Reflects scenarios based on organizational decisions and used to run automation task scripts based on the results. Potential outcomes for the Forward Path script include deploy on Windows 7 x64 as App-V Package and retire/replace or find alternative platform.

The Forward Path report is used to reflect organizational decisions and run task scripts based on the results. There are two Forward Path reports configured for this solution:

  • Microsoft App-V 5.0 Decision - used to determine if applications are good candidates to be sequenced using Microsoft App-V 5.0. If an application is a good candidate for sequencing using Microsoft App-V 5.0 a task script will be provided that automates the sequencing process.

    App-V 5.0 Sequencer execution profile is referenced in Task Scripts to automate Microsoft App-V 5.0 sequencing for outcomes that include Microsoft App-V as a good or possible candidate for application streaming.

  • Microsoft App-V 4.6 to App-V 5.0 Decision – used to convert Microsoft App-V 4.6 sequences to App-V 5.0 for outcomes that include Microsoft App-V as a good or possible candidate for application streaming.

    [EP] Converter_App-V4.6_to_App-V5.0 is referenced in Task Scripts to automate the conversion of Microsoft App-V 4.6 to App-V 5.0 sequences for outcomes that include Microsoft App-V as a good or possible candidate for application streaming.

To access the Forward Path report click Reports: Applications > Forward Path. Click the Change Scenario button and then click the drop-down list to select the Microsoft App-V 5.0 Decision or Microsoft App-V 4.6 to App-V 5.0 Decision report.

Note: You can further customize the Forward Path script to tailor it to your environment and business decisions.

Overview Summary

Provides a high-level dashboard view of the state of your application portfolio across all active reports. For each of the selected applications, it shows the overall RAG (red, amber, green) status for each of the active reports. On the rows that relate to an application, you can click the RAG icons to access the Remediation report views for that application. These provide the remediation details required for the application to work using the selected platform.

Microsoft App-V 5.0

Tests desktop applications for suitability with Microsoft Application Virtualization (App-V) 4.5, 4.6 SP1, or 5.0.

Microsoft Windows 8/7

Determines compatibility of the application on the target OS by going directly to the specific OS report. Drill down to the specific issues, download automated fixes, and get more information on how the application can be remediated.

Windows applications to App-V 5.0 migration steps

This section details the recommended process for migrating Microsoft Windows applications to Microsoft App-V 5.0, including the stages involved in assessing the application for compatibility against App-V 5.0, Windows 8/7, and Server 2012/2008 R2, 64-Bit. It also covers how to automate the conversion of App-V 4.6 sequences to App-V 5.0 and how to create App-V 5.0 sequences.

The flowchart shows you how to engage AppDNA into your migration and business-as-usual process.

Windows applications to App-V 5.0 migration flowchart

Step 1

Import application DNA

For applications in an MSI format, select Import & Analyze > Applications > Direct Import.

For application in a Non-MSI format, select Import & Analyze > Applications > Install Capture.
Step 2

Analyze the application

Analyze the application against Microsoft Windows8/7, x64 and App-V. Include Server 2012/2008 R2 if the application will be hosted on a Microsoft server platform.
Step 3

Run Forward Path script

Run the forward path script Microsoft App-V 4.6 to App-V 5.0 Decision to check the compatibility of applications sequenced using Microsoft App-V 4.6 against Microsoft Windows 8/7, x64, and App-V 5.0 and get a review of the applications that are good or potential candidates for App-V 5.0.

Run the forward path script Microsoft App-V 5.0 Decision to check the compatibility of applications against Microsoft Windows 8/7 and App-V 5.0 and get a review of the applications that are good or potential candidates for App-V 5.0.

  1. To access the Forward Path reports: Choose Reports: Applications > Forward Path. Click Change Scenario and then click the drop-down list to select the Microsoft App-V 4.6 to App-V 5.0 Decision or Microsoft App-V 5.0 Decision report.
  2. To run task scripts, click Evaluate Tasks.
Step 4

Remediate

Review the Forward Path report data and prioritize applications based on RAG status:

  • Green – Run task scripts (if one is available) and proceed to User Acceptance Testing (UAT).
  • Amber – Check the detailed remediation report to determine what has been flagged and if it needs remediation or functional testing. Run task script (if available) and proceed to UAT.
  • Red – Check the detailed remediation report to determine if the component flagged can/should be remediated and the action you want to take (that is, re-development, local installation on Windows 7/8, deploy on legacy platform, or retire and replace). Check the Overview report for the best fit platform.
Note: Click the application name within the Forward Path report to go directly to the detailed remediation data for an application.
Step 5

Run Task Script

Run the task script for applications that are suitable for App-V 5.0. These will be indicated by a Yes in the Automated Task Script column.

Click the Start button to run automated task scripts and either convert Microsoft App-V 4.6 sequences to Microsoft App-V 5.0 sequences or create Microsoft App-V 5.0 sequences.
Step 6

Test output for applications compatible for App-V 5.0

Locate the output files created and perform functionality testing.
Step 7

Submit to User Acceptance Testing

Submit the applications to UAT, ensuring that the expert users are involved in the process.

Tap into the extendable features of AppDNA by using the Forward Path script to send an email to the group performing UAT when an App-V 5.0 sequence is ready to be deployed and tested.
Step 8

Find alternatives for applications not compatible with a given solution

For applications that are not compatible (cannot be remediated or remediation is deemed too costly) use AppDNA to determine if a legacy deployment option is more cost effective. Otherwise, consider retiring and replacing the application.

Use the Overview Summary report to get a quick look at the best possible platform for your application.