601D: From application portfolio to

application readiness: automating

application lifecycle maintenance with
Citrix AppDNA
Hands-on lab exercise guide

Table of Contents
Table of Contents .............................................................................................................................................. 2
Overview............................................................................................................................................................. 3
How to log into the lab environment ............................................................................................................. 4
Exercise 1: Installation and Configuration .................................................................................................... 5
Exercise 2: Import and Analyze Desktop Applications ............................................................................ 15
Exercise 3: Examine the Platform and Application Level Assessment Results ..................................... 27
Exercise 4: Examine the Organization Reports Architecture ................................................................... 32
Exercise 5: Remediate an Issue with an Application.................................................................................. 39
Exercise 6: Working with Web Applications .............................................................................................. 47
Exercise 7: Creating a Custom Report and Algorithm .............................................................................. 51
Exercise 8: Configuring Multi-OS ................................................................................................................ 66

Page 2

Overview
Hands-on Training Module
This training module has the following details:
Objective

Provide hands-on experience with installing and configuring Citrix AppDNA

Provide hands-on experience with common tasks in Citrix AppDNA

Audience

Primary: Citrix Partners and Citrix Customers

Lab Environment Details

This section is used to describe the virtual machines that are used.
Machine
AD.training.lab
AppDNA

Details
Windows Server 2008 R2 domain controller, DNS, web server,
etc.
Windows Server 2008 R2 with SQL Server 2008 R2

Required Lab Credentials

Below are the login credentials required to connect to the workshop system and complete the lab
exercises.
Domain
Training.lab
Training.lab

Username
Administrator
AppDNASvc

Password
Citrix123
Citrix123

*The local administrator password for each virtual machine is citrix.

Page 3

How to log into the lab environment

The student lab environment is hosted on a Citrix XenServer. Follow the directions below to access
the server.
Note: Browser support: IE, Firefox, Chrome, Opera, Safari (on MAC).

Step-by-step login instructions

Step
1.

Action
Launch your web browser and go to http://ilt.citrixsynergy.net

2.

On the website, type in the session code provided by your instructor and your business
email address. Click Get started.

3.

Once youve logged in, click the Start Lab button. This will launch your lab session.
Note: Please wait for the application to launch.

4.

Right-click XenCenter and select Add.

5.

On the Add New Server screen enter the XenServer IP address provided on the website
and in the Password field enter the password provided on the site.

Page 4

Exercise 1: Installation and Configuration

Overview
In this exercise we will install the AppDNA server, database and client components onto a Windows
Server 2008 R2 virtual machine. The required Application Server and Web Server Roles have been
previously installed as has SQL Server 2008 R2. After installation, we will proceed to perform the
initial product configuration.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 15 minutes.
Step Action
1.
Within XenCenter, select the AppDNA virtual machine and logon as
training\administrator with password Citrix123.
2.
Double-click Citrix-AppDNA-Quick-DB-Installation.msi on the Desktop

3.

NOTE: It may take a moment or two for the initial installation screen to appear as this is a
large installer file.
Click Next on the welcome screen

Page 5

Step
4.

5.

Action
Click to accept the license agreement and then click Next

Leave Complete (server + client) selected since we are installing all components. Then
click Next.

Page 6

Step
6.

7.

Action
Click Next to accept the default installation locations

Click Install to begin the installation process

Page 7

Step
8.

9.

Action
Wait a moment for the installation to complete. Then click Finish.

Click Next to begin the configuration process

NOTE: At any step of this configuration process you can click the Need help? link in the
lower left to bring up a web page with additional information.

Page 8

Step
10.

11.

Action
Click Next on the Web server step as well be using IIS which has already been installed

Leave the defaults of AppDNA for both the server name and database name. Well use the
credentials of the currently connected domain administrator. Click Next.

Page 9

Step
12.

Action
Well want to use a service account for maintaining the persistent connection to the
database (the credentials used in the previous step are for creating the database). Enter
TRAINING\AppDNASvc for the username and Citrix123 for the password and then
click Next.

NOTE: Production environments should always utilize a true service account. The
account should not be subject to password changes and should contain the bulkadmin role
on the server and db_owner permissions on the AppDNA database. Refer to the official
AppDNA documentation for additional details.

Page 10

Step
13.

Action
Click the Browse button and select the .LIC license file located on the Desktop. Then
click Next.

NOTE: It is also possible to run in the limited evaluation mode for up to 30 days and
upload a license file at a later date by running the Configure AppDNA wizard. This mode
allows analyzing up to five Windows and five Web applications.

Page 11

Step
14.

15.

Action
On the System check screen confirm that there are no errors. Then click Next.

NOTE: If certain pre-requisites are not met, AppDNA will provide you with the option of
attempting to fix the issues.
The initial setup process will now commence. This will take a few minutes as the included
standard database is restored.

Page 12

Step
16.

Action
When the process completes, click Close.

Page 13

Summary
Key
Takeaways

The key takeaways for this exercise are:

AppDNA is available in two installer varieties: a primary MSI for production

installs that takes some time to build up the OS images for import and a
QuickDB MSI version for local PoC and test installs with a standard
database that is restored during the configuration process
(we used the QuickDB version here in the interest of time)

Installing and configuring AppDNA is an easy and straightforward process

The AppDNA installer is used to install the server, database and client
components. Each one can be on a separate machine (using the primary
MSI installer) or all components can be on the same machine as we did here
(primary MSI installer or QuickDB installer)

Page 14

Exercise 2: Import and Analyze Desktop

Applications
Overview
In this exercise you will import and analyze six desktop applications in Citrix AppDNA. The first
steps in using AppDNA software are to import your applications and then analyze them against the
target platforms. Import will generate application DNA, which is stored in the AppDNA database.
Analysis uses heuristic algorithms to identify compatibility defects in the application. The separation of
import from analysis allows analysis against multiple platforms, as well as future platforms, without
having to re-import applications.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 15 minutes.
Step Action
1.
Launch AppDNA from Start > All Programs > Citrix AppDNA > AppDNA. Logon as
administrator / apps3cur3.

Page 15

Step
2.

3.

Action
The Configure Modules Wizard will load for the first login. Click Next on the Welcome
screen.

Select Windows 7 32-bit and deselect Windows 7 64-bit. Then click Next.

Page 16

Step
4.

5.

Action
Ensure Windows Server 2008 R2 is selected as the To platform and then click Next.

Leave the defaults selected on the Virtualization screen and click Next.

Page 17

Step
6.

7.

Action
Leave the defaults selected on the Web Browser screen and click Next.

Leave the defaults selected on the XenApp Hosted screen and click Finish.

Page 18

Step
8.

Action
Click Close when the process is complete.

Page 19

Step
9.

Action
Navigate to the Import Applications screen by selecting Import & Analyze and then
selecting Applications located under Import from the side navigation bar.

10.

Lets first add an application to AppDNA by manually browsing for it. Click the Browse
button, navigate to C:\Software\AppImport\Browse\BBC Ticker and select the
BBC_BBC_Ticker_1.0.1.7_P1.0.msi file. Then click Open.

11.

Now lets add in applications by searching. Click the Search button.

Page 20

Step
12.

13.

14.

Action
Click Browse and navigate to C:\Software\AppImport\Search. Then click Open and
Search.

NOTE:
You have the ability to search an entire application repository with this feature
You can search for applications in MSI, EXE, BAT and SFT formats
(though only MSI and SFT formats can be directly imported)
You can add applications to groups for better organization
Next well add in applications from an import list file. Click the Import from list button.

Click the Browse button and navigate to C:\Software\AppImport\List. Select the

importlist.csv file and click Open. Then click the Import button.

NOTE: The path to the application installers referenced from the CSV file should not
contain any spaces in order to prevent import errors.

Page 21

Step
15.

Action
Six applications should now be in your queue list. Click the Import button on the top right
to start the import process.

16.

Wait a moment for each application to show Loading Completed Successfully under the
Progress column. Then click the Analyze button on the top right side to start the analysis
wizard.

17.

The first page of the wizard allows you to select the modules you want to analyze against.
Leave all modules selected and click Next in the upper right-hand corner.

Page 22

Step
18.

Action
Analysis will take a few minutes to complete.

NOTE: AppDNA algorithms validate the suitability, interoperability, conflicts, and

performance of the applications in the target environment. Each algorithm is designed to
identify applications that would potentially have a specific issue on the target platform.
Applications that are identified as having this issue are said to trigger the algorithm. In the
interest of time, we are analyzing against specific platforms and modules as opposed to all
available platforms and modules.

Page 23

Step
19.

Action
When the analysis completes, click Finish in the upper right-hand corner.

Page 24

Step
20.

Action
You are now viewing the Overview Summary Report for these applications. Take a
moment to view the status for each application on the modules. Keep in mind that these
applications were analyzed against several technologies in just minutes.

Page 25

Summary
Key
Takeaways

The key takeaways for this exercise are:

AppDNA consists of various modules of which the applications can be

analyzed against

There are several ways to import applications into AppDNA: manually

browsing, searching a directory and using import list files

The analysis phase runs multiple algorithms against the imported

applications

Analysis takes just minutes against several different technologies

Page 26

Exercise 3: Examine the Platform and

Application Level Assessment Results
Overview
In this exercise you will use the reporting architecture to examine how AppDNA Application
Intelligence can be used throughout a migration project - from the initial planning phase, to
rationalization through to the tactical remediation of application compatibility defects.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 15 minutes.
Step Action

Page 27

Step
1.

Action
From the navigation bar, select Reports: Applications, click Windows 7 SP1 under
Desktop Compatibility Manager and then click Application Issues to load the report
focusing on the Windows 7 SP1 32-bit platform.

NOTE: The Application Issues Report is useful for visualizing the overall health of your
portfolio against the given platform, Windows 7 SP1 32-bit, as well as reviewing the
compatibility risk of each application.

Page 28

Step
2.

Action
When done reviewing the Applications Issues report, click the Application Actions
button in the top bar on the right. Spend a moment reviewing this report.

NOTE: The Application Actions Report is used for visualizing the overall health of your
portfolio after all remediations have been applied. In addition, for each application this
report gives you the complexity of the application, the current RAG status, the RAG status
after remediations have been applied and the effort needed to apply those remediations.

3.

4.

5.

This information can be used, in conjunction with business data, to make decisions on how
to move forward with an application. The flow will depend on the organization, but imagine
a scenario where an application is not compatible with Windows 7 SP1 yet is simple to
remediate. The best forward path might be to remediate this application now to defer the
upgrade/engineering expense until the next software refresh cycle.
When done reviewing the Application Actions Report, click the Issue View button in the
top bar on the right. Spend a moment reviewing this report.

NOTE: The Issue View Report shows you the list of issues and potential issues your
application portfolio could experience. Pivoting on Issues will help you to understand what
types of defects your team will encounter so that training and preparation can be tailored to
those needs.
Review the Issue View Report, and when done click the Action View button in the top
bar on the right. Spend a moment reviewing this report.

NOTE: This report is similar in value to the Issue View Report except that instead of
looking at the frequency of defects it looks at the frequency of remediations. Many defects
will have the same remediation so pivoting on Action will help you to understand what
remediation techniques your team will need to be trained on in order to successfully deliver
the migration project.
When done reviewing the Active View Report, click back to the Application Issues
Report.

Page 29

Step
6.

7.

8.

Action
After the report loads, scroll down and select one of the red applications by clicking the
name of the application (will appear as a hyperlink) to load the individual remediation report
for the application.

NOTE: This is the Application Remediation Report for this application on Windows 7
SP1. This report gives the low level, granular data needed to remediate all issues for an
application on this target environment (Windows 7 SP1).
Scroll down the report in order to read the manifestation, remediation and group definitions
for each red, amber and green issue identified by Citrix AppDNA.
NOTE: To gain an understanding of the issues identified and remediations included within
AppDNA, you can navigate through the different reporting levels for each of the target
environments including Server Based Computing (XenApp Hosted) as well as App-V,
XenApp Streamed, etc.
Explore the Applications Issues Report under the XenApp Hosted / TS, XenApp
Streamed and App-V nodes from the navigation bar on the left.

Page 30

Summary
Key
Takeaways

The key takeaways for this exercise are:

Detailed data points about the applications are collected and provided to the
AppDNA user in an easy-to-consume format.

While this exercise focused on Windows 7 SP1 reports, all other module
reports follow the same model and provide the same value.

Page 31

Exercise 4: Examine the Organization

Reports Architecture
Overview
In this exercise you will use the organization reporting architecture to examine how AppDNA
Application Intelligence can be used from Active Directory and System Center Configuration Manager
to provide summaries of the status of managed applications that have been deployed to users and
computers in entities that are defined in Active Directory or System Center Configuration Manager
(SCCM). In this context, managed applications are applications that are deployed through Active
Directory or SCCM.
NOTE: Before you can view organization reports and see meaningful data, you need to export data
from Active Directory and/or SCCM and then import into AppDNA the applications that have been
deployed through Active Directory or SCCM. In this exercise we will import some sample data that
has been previously exported.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 15 minutes.
Step Action
1.
From the pull-down menus at the top, go to Configure > AD & SCCM > Data Import
2.
Select the Import from file tab
3.
Click Browse and navigate to ad.sgz at C:\Software\AppDNA
4.
Click Start Import towards the top right. Wait for the import to complete.
5.
Click Browse and navigate to sccm_staged.sgz at C:\Software\AppDNA
6.
Click Start Import. Wait for the import to complete which can be observed at the bottom
of the screen.
7.
From the top menu bar, select Configure > AD & SCCM > Link Packages to Apps.
8.
In the Applications box on the right, click the Application column header to sort the
applications alphabetically.

Page 32

Step
9.

Action
In the Packages box, select the plus sign beside Installation: BBC Ticker and then click
the checkbox beside the application name.

10.

In the Applications box, select the BBC Ticker line to highlight the row.

11.

In the Packages box, click the green check button to associate the selected application to
the selected package.

12.

Perform steps 9-11 for the remaining applications in the Applications box. Then click
Save Associations.

Page 33

Step
13.

14.

Action
From the side navigation bar, select Reports: Your Organisation and then click Groups.

In the Report drop-down list on the upper right-hand side, ensure Desktop Compatibility
Manager: Windows 7 SP1 is selected.

Page 34

Step
15.

Action
On the row with the Development group, click the hyperlink 3 under the Users column.

16.

You are now looking at the users within the Active Directory group named Development.

NOTE: This view gives you an application count for each user and the count is broken
down by RAG status for each application.

Page 35

Step
17.

Action
For Developer 2, click the 4 in the total column.

18.

Scroll down a little and you will be looking at the four managed applications Developer 2
has currently installed on his/her machine.

19.

From the side navigation bar, select Users.

NOTE: This gives you a list of all users imported into AppDNA. The Users Report View
provides a summary of the status of the managed applications deployed to the users.

Page 36

Step
20.

21.

Action
By selecting the drop-down list beside Report (near the top of the screen), you can view the
status of each users managed applications by different technologies. Click the drop-down
list arrow and select Virtualization Manager: App-V to view users application status
against this technology.

Continue to view the different reporting information you can access for the different
technologies.

Page 37

Summary
Key
Takeaways

The key takeaways for this exercise are:

The organization reports provide summaries of the status of the managed
applications that have been deployed to users and computers in entities that
are defined in Active Directory or SCCM.
In this context, managed applications are applications that are deployed
through Active Directory or SCCM.
The organization reports show the status of managed applications that have
been imported into AppDNA or linked with applications already imported
into AppDNA.

Page 38

Exercise 5: Remediate an Issue with an

Application
Overview
In this exercise you will create an Auto Fix or remediation for an application using the AppDNA
auto-fix capabilities. AppDNA employs an approach called Intelligent Remediation. While this
exercise walks you through automatic remediation, the AppDNA remediation reports detail the
possible remediation options.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 15 minutes.
Step Action

Page 39

Step
1.

2.

Action
From the navigation bar, select Reports: Applications and then click Windows 7 SP1 >
Application Issues.

Click the Change Selection button.

Page 40

Step
3.

Action
Double-click the checkbox beside ID to select all applications in the list.

4.
5.

Click the Select button at the bottom of the Select Applications window.
Hide the navigation bar by clicking the arrow beside Reports: Applications. This is
located on the left, just below the top menu bar.

6.

Scroll down in the report and select the StyleWriter application by clicking the application
name.

7.

Scroll down to the issues list and review the results in the Issue View.

NOTE: Automated remediations for any issues are denoted with a checkmark in the MST
column next to the issue which can be automatically remediated.

Page 41

Step
8.

9.

Action
After reviewing the automated remediations (there are two), scroll up and click the Get
MST Fixes button.

Save the MST to the same location as the original MSI package at
C:\Software\AppDNA\TestApps\StyleWriter. Click OK in the dialog generated after
the MST has been saved.
NOTE: There are two ways to update AppDNA so that the RAG status reflects the
remediated state of the application. You can reimport the application with the fixes applied
or use Journaling to mark an application as remediated. For this example, you will reimport
the StyleWriter application using the AutoFix MST file created by AppDNA.

Page 42

Step
10.

Action
Expand the navigation bar by clicking the arrow. Then select Import & Analyze and click
Applications under Import.

11.

Click the Delete button to clear the application import queue.

12.

Click the Browse button and navigate to C:\Software\AppDNA\TestApps\Stylewriter.

13.

Select the ORG_StyleWriter_3.90_P1.0 Global.msi file and click Open.

Page 43

Step
14.

Action
Select the Expand all MSTs checkbox to show that AppDNA recognized the MST
transform file associated with this application. Choose the Select all MSTs checkbox to
select the MST file.

15.

Click the Import button on the upper right-hand side.

16.

After the import is complete, select the Analyze button on the upper right-hand side.

17.

All modules should be selected at this point. Click Next on the upper right-hand side to
begin the analysis process.

18.

19.

NOTE: Analysis will take a few minutes.

After analysis is complete, click Finish.

You are now looking at the Overview Summary Report for StyleWriter. Notice under
the Desktop Compatibility Manager Windows 7 SP1 column, the status of the
application is now green (it was previously red).

Page 44

Step
20.

Action
Click the green G status for StyleWriter under Desktop Compatibility Manager
Windows 7 SP1 to show the detailed remediation report.
NOTE: The two red issues for this application have now been remediated by the transform
file that was generated by AppDNA.

Page 45

Summary
Key
Takeaways

The key takeaways for this exercise are:

The right remediation will depend on the application as well as the

organization.

Sometimes the best solution is not to remediate an application but to

upgrade or replace it. AppDNA makes this information available in a variety
of tailored formats.

Autofix remediations within AppDNA are voluntary. You are not forced
into accepting an automatic fix that does not fit into your packaging best
practices.

Page 46

Exercise 6: Working with Web Applications

Overview
Aside from providing detailed reports on Windows applications, AppDNA can also analyze and report
on Web applications including their level of browser compatibility.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 15 minutes.
Step Action
1.
From the navigation bar, click Import & Analyze and then Web Applications.

Page 47

Step
2.
3.
4.
5.

6.

7.
8.

Action
Click the Add button.
Enter Litmus Web Source in the Name field.
Click the search button (magnifying glass) beside the Source Folder text box.
Browse to C:\Software\AppImport\Web and click OK. Then click OK to queue up the
web application.

NOTE: This process is used when the web sites source files are available.
Now we will import a web site via a browser to capture and analyze the rendered HTML
pages. This process is necessary when analyzing a web site where you cannot directly access
the source files. Click the Add button again.
Enter Sample Store in the Name field.
Enter http://shop.training.lab in the Url field. Then click OK.

Page 48

Step
9.

Action
Select the Use Manual Browser Navigation checkbox. This will allow us to only capture
the specific pages that we browse to for the Sample Store Web Application as opposed to
attempting to crawl the entire site.

10.

Click the Import button to begin the process.

11.

An instance of Internet Explorer will launch. Click on several links within the Sample
Store Web Application to visit 10 or more pages.
After traversing several pages, close Internet Explorer.

12.

13.

14.
15.
16.

NOTE: After closing the browser, AppDNA will start the importation of the web site to
the database. Importation of both web applications happens simultaneously.
Wait a few minutes for the progress indicators to show Loading Completed Successfully
for both web applications. Then click the Analyze button.

Click Next to start the analysis of the web applications. This will take a few minutes.
Once analysis is complete, select Finish to view the Overview Summary Report for the
applications.
Click the given RAG status under the IE or Firefox columns to review the issues identified
by AppDNA.

Page 49

Summary
Key
Takeaways

The key takeaways for this exercise are:

AppDNA can analyze web applications and provide detailed browser

compatibility information

Web applications may be imported into AppDNA by browsing for source

files or browsing/crawling the actual web site

Page 50

Exercise 7: Creating a Custom Report and

Algorithm
Overview
In this exercise you will use the Custom Reports Manager to create and manage custom reports. These
are reports that you define yourself. You can base custom reports on existing algorithms and algorithm
groups or new ones that you write yourself. You can also create new algorithms based on your own
specialized knowledge of your environment.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 20 minutes.
Step Action
1.
From the top menu bar, select Configure > Custom Reports.

2.

On the toolbar, click New. This opens the New Custom Report dialog.

Page 51

Step
3.

4.

Action
Leave the default Name and Description for the new custom report and click OK.

In the tree view on the right side of the Custom Reports Manager screen, click the plus
sign beside Windows 7 SP1 to show the algorithms.

Page 52

Step
5.

6.

Action
Click the first algorithm named Anomalous application aspects to highlight it. Hold
down the shift key and click the last algorithm of Windows Resource Protection. All
associated algorithms with Windows 7 SP1 should now be highlighted.

Left-click the selected algorithm set and then drag-and-drop these algorithms to the name
of your new custom report on the left.

Page 53

Step
7.

8.

Action
Collapse the Windows 7 SP1 node on the right side of the screen and click the plus sign
beside App-V to show the associated algorithms.

Click the top algorithm and then shift-click the bottom algorithm for App-V to select them
all just as you did for Windows 7 SP1.

Page 54

Step
9.

10.

Action
Left-click the selected algorithm set and then drag-and-drop these algorithms to your new
custom report on the left. All associated algorithms added to your new custom report
should now be seen under the report name.

Click the Save button just above your custom report.

NOTE: You have just created a new custom report which combines all algorithms for
Windows 7 and App-V and will show as one single report.

Page 55

Step
11.

12.
13.

Action
To enable reporting for your new report, on the navigation bar choose Select > All
Applications.

Click No when prompted to analyze. Then click All Applications again.

Make sure all applications are selected and then click the Analyze button in the upper righthand corner.

Page 56

Step
14.

Action
Deselect all technologies except My New Custom Report.

15.

Click Next in the upper right-hand corner.

16.

NOTE: The analysis will take several minutes to complete.

Once analysis is complete, click Finish in the upper right-hand corner.

17.

NOTE: You will now see a new column (third from the right) titled Custom Reports My
New Custom Report. This new report shows application compliance with both Windows 7
SP1 and App-V. You can now view complete reporting for these two technologies from
one, combined report. Take note that the application BBC Ticker is green under your
custom report column. We will be modifying that status a few steps down.
Under the Custom Reports column, click the red R for ActiveSync to view the
combined Windows 7/App-V report.

Page 57

Step
18.

Action
You can also create custom algorithms to test for specific issues within your environment.
To start creation of a new algorithm, from the top menu bar select Configure > Custom
Reports.

19.

Right-click My New Custom Report and select New Group.

20.

Leave the default name and identifier information and click OK to create the new algorithm
group.

Page 58

Step
21.

22.

Action
Right-click My New Algorithm Group under the My New Custom Report node and
select New Algorithm from the shortcut menu.

Leave the Identifier and Name as the default and click Next.

Page 59

Step
23.

Action
Under Manifestation, delete the default text and type This algorithm searches for the file
BBCTicker.exe. Under Remediation, delete the default text and type This file must be
removed from the application package. Then click Next.

Page 60

Step
24.

Action
Select the radio button beside the red R labeled The Application will fail if this
Algorithm is triggered. Then click Next.

Page 61

Step
25.

26.

Action
In the Action drop-down list, select Redevelopment Required. Then click Next.

In the File Name text box type %BBCTicker.exe% (include the percent signs).

Page 62

Step
27.

Action
Click the Save button.
NOTE: By clicking the plus sign beside My New Algorithm Group, you can see the
newly added algorithm.

28.

Click the Save button located just above your report name.

29.

NOTE: You need to reanalyze your applications against your custom report in order for
the new algorithm to run.
On the navigation bar, choose Select > All Applications.

Page 63

Step
30.
31.

Action
Choose No when prompted to analyze and then click All Applications again.
Deselect all applications by clicking the checkbox beside ID.

32.

Select the checkbox by the BBC Ticker application in the list.

33.

Click the Analyze button.

34.

Ensure only My New Custom Report is selected and then click Next.

Page 64

Step
35.

Action
Once analysis completes, click Finish.

36.

On the Overview Summary Report, notice under the Custom Reports column that the
application is now red.

37.

Click the red R in the Custom Reports column to view the individual remediation report
for BBC Ticker.
NOTE: The Results Summary Table shows your algorithm on top of the list. Spend a few
minutes reviewing the report.

Summary
Key
Takeaways

The key takeaways for this exercise are:

Use the Custom Reports Manager screen to create and manage custom
reports.

These are reports that you define yourself and you can base custom reports
on existing algorithms.

Custom Reports combine differing technologies for ease of remediation

reporting.

AppDNA comes with a number of templates for creating new algorithms in

custom reports.

You can create new algorithms based on your own specialized knowledge of
your environment.

Page 65

Exercise 8: Configuring Multi-OS

Overview
In this exercise you will import a unique Windows 7 64-bit operating system image into the AppDNA
database. This OS has been captured using the snapshotmanager.exe utility provided with AppDNA.

Step-by-step guidance
Follow the steps below to complete the task.
Estimated time to complete this lab: 20 minutes.
Step Action
1.
On the navigation bar, select Import & Analyze > Operating Systems.

Page 66

Step
2.

Action
Click Import from MSI on the toolbar. This opens an import screen.

3.

Click the folder button and navigate to C:\Software\AppDNA\OS Snapshot. Select the
ossnapshot.msi file.

4.

Under OS Image Name, give it the name Windows 7 64 bit

5.

NOTE: Names cannot contain certain special characters such as hyphens.

Under OS image description, type 64-bit Image for Windows 7 and then click Next.

Page 67

Step
6.

Action
On the Image relationships screen, check the box next to Default Image for Windows
XP and then click Next.

7.

Wait a few minutes for the import process to complete. Then click Back to Operating
Systems.

8.

Verify that the OS image has been imported.

NOTE: Analysis of the application portfolio would now be necessary to show any
differences between the two operating systems. Due to time constraints, we will not
reanalyze the portfolio.

Page 68

Summary
Key
Takeaways

The key takeaways for this exercise are:

Multiple versions of the same operating system can be imported into

AppDNA.

More information is available at:

http://blogs.citrix.com/2012/03/21/streamline-application-compatibility-formultiple-os-configurations/

Please complete the survey

We value your feedback! Please take a moment to let us know about your self-paced
lab experience by completing a brief survey on the web portal before you logout.

Page 69

Revision History
Revision
1.0

Change Description

Updated By

Original Version

Allen Furmanski

Date
10/2012

About Citrix
Citrix Systems, Inc. designs, develops and markets technology solutions that enable information technology
(IT) services. The Enterprise division and the Online Services division constitute its two segments. Its
revenues are derived from sales of Enterprise division products, which include its Desktop Solutions,
Datacenter and Cloud Solutions, Cloud-based Data Solutions and related technical services and from its
Online Services division's Web collaboration, remote access and support services. It markets and licenses its
products directly to enterprise customers, over the Web, and through systems integrators (Sis) in addition to
indirectly through value-added resellers (VARs), value-added distributors (VADs) and original equipment
manufacturers (OEMs). In July 2012, the Company acquired Bytemobile, provider of data and video
optimization solutions for mobile network operators.
http://www.citrix.com

2012 Citrix Systems, Inc. All rights reserved.

Page 70