AppDNA Effort Calculator Report - Citrix

2y ago
26 Views
2 Downloads
768.80 KB
21 Pages
Last View : 17d ago
Last Download : 2m ago
Upload by : Aiyana Dorn
Transcription

AppDNA Effort Calculator ReportPrepared for Citrix Customer10-Dec-12 01:36:41 PM

1. Background InformationCitrix AppDNA enables enterprises to confidently discover, automate, model, and manageapplications for faster application migration, easier application virtualization and streamlinedapplication management.AppDNA was used to carry out an assessment for Citrix Customer to assess a sample set ofapplications for compatibility with the following technologies: Installations Hosted on XenApp 2008 R2The AppDNA Effort Calculator used the assessment results to estimate the time, cost and effortassociated with preparing the applications for the new platform and the results were extrapolated toprovide an equivalent estimation for the customer’s entire application portfolio. This reportsummarizes the results and explains the assumptions and methodology.Page 2

2. Executive SummaryAppDNA enables application compatibility issues to be understood in the planning stage of amigration project and facilitates the development of a targeted test and remediation strategy.AppDNA is not dependent on the creation of test environments, the deployment of interrogationtools, or the installation and running of each application on the target platform. AppDNA cantherefore provide significant efficiency gains based on definitive accurate information whilesignificantly minimizing the cost, time and risk associated with a migration project.MethodologyAppDNA interrogates an application’s installation package, files and API usage to expose theapplication’s “DNA”. This is stored in the AppDNA database. AppDNA then runs sophisticatedheuristic algorithms on the application DNA to predict issues that are likely to be exhibited when theapplications are deployed on the target platform. The individual algorithms are grouped bytechnology areas, which are described in Appendix A. Each algorithm identifies a specific issue andhas a recommended remediation process to mitigate that issue.This analysis provides an understanding of the types, prevalence and extent of potential issues withinthe sample applications. Using this understanding of the issues, known remediation actions and theeffort associated with those actions along with an understanding of the complexity of theapplications, the AppDNA Effort Calculator is able to estimate the time, effort and cost of migratingthe sample applications to the target platform, both with and without AppDNA. The Effort Calculatorthen extrapolates the results to reflect the size, cost, and scope of the compatibility challenge in theentire application portfolio.The results are configured using a variety of variables that define, for example, the number ofapplications in the entire portfolio, the currency to be used, the number of working hours in a day,the size of the testing and remediation teams, and how much they cost per day.Results summaryThe following table summarizes the results for the sample applications and the extrapolated resultsfor all the applications in the portfolio. This shows the estimated cost and the time to test andremediate the applications both with and without AppDNA.Without AppDNAWith AppDNASavings25 application Months 0.68sampleCost 237140.10.5831582055625 application Months 0.68portfolioCost 237140.10.58315820556USDUSDTable: Project cost and duration, with and without AppDNAPage 3

Without AppDNA and based on the currently available resources and best effort estimation, theeffort associated with the project can be summarized as follows: 25 applications are in scopeOn average, each application costs 948.56 USD to test and remediateOn average, each application takes 1.91 days to test and remediateThe project team has 8 peopleThe project will take 0.68 months to completeWith AppDNA, the effort associated with the project can be summarized as follows: The cost per application will reduce to 126.32 USDThe average time to test and remediate an application will reduce to 0.33 daysThe project can be completed in 0.1 months, a reduction of 0.58 months.This represents a saving of 20,556 USDFigure: Relative project durations with and without AppDNAPage 4

3. Installations Hosted on XenApp 2008 R2compatibility assessmentThe Effort Calculator uses the results from the AppDNA EstateView report view to gain an overallpicture of the compatibility of the sample applications with Installations Hosted on XenApp 2008 R2.AppDNA categorizes compatibility issues using a red, amber and green (RAG) risk rating. Eachalgorithm identifies a specific issue and has a default RAG risk rating associated with it. These arecalled the standard RAG ratings. Sometimes organizations may want to raise an amber status to redor lower it to green for a specific issue, for example. When the RAG ratings have been customized,the customized RAG risk ratings are used in this report. See Appendix D for the RAG statusdefinitions.Before remediationThe following figure provides a high-level view of the RAG risk status of the sample applications.Standard Summary DetailsRAGTotalAppsRAG Summary Chart% ofTotal832.0%624.0%1144.0%0025Figure: Installations Hosted on XenApp 2008 R2 portfolio status before remediationThe algorithms and the issues that they identify are grouped by technology areas, which aredescribed in Appendix A. The next figure shows the distribution of the compatibility issuesdiscovered in the sample portfolio according to these groupings and the prevalence, type andseverity of the issues. This view quickly highlights which types of issues are most prevalent.Page 5

Figure: Installations Hosted on XenApp 2008 R2 issue distributionPage 6

After remediationOne of the significant benefits of AppDNA is that each compatibility issue that is identified has aremediation activity (called an action) associated with it. Each action has an associated “action RAG”,which indicates the compatibility status after the action has been performed. Some actions mayleave the application in a red state, which indicates an exception. This means that the applicationmay need to be redeveloped or decommissioned. Where an issue can be resolved through thesuggested action, the action RAG is green. Some issues may require testing before a remediation canbe decided. The action RAG is then amber, which indicates that further testing is required.After the implementation of the recommended remediation actions, the application states andtesting methodologies can be summarized as: Applications that transition from an incompatible state to a compatible state (green) can beprogressed to light user acceptance testing (UAT)Applications that have a partial remediation require additional targeted testing (these areshown as amber)Applications that have severe compatibility issues are treated as exceptions and are shown asredThe following figure provides a view of the sample application portfolio’s compatibility status as itwill be after the suggested remediation activities have been applied to the sample applications.Standard Summary DetailsRAGTotalAppsAction RAG Summary Chart% ofTotal728.0%14.0%1768.0%25Figure: Installations Hosted on XenApp 2008 R2 portfolio status after remediationThe before remediation assessment summary indicates that the sample portfolio is 44.0% green. Thiscan be transformed to 68.0% green after remediation. Applications that have issues for which thereare known remediations will shift from amber or red into the green category. The 4.0% ofapplications making up the amber category after remediation carry issues for which the remediationaction is further testing. Some issues cannot be remediated with certainty and applications withthese types of issues may require further testing before a remediation strategy can be applied. Thisamber category then has no associated remediation but is targeted for more direct analysis andtesting. The remaining 28.0% of applications classified as red indicate exceptions; these areapplications with underlying compatibility issues that will not be remediated via the current process.Applications that are defined as exceptions should be escalated to the vendor for a compatibleversion of the application or an alternative application provisioning technology should be utilized.The amount of effort required to remediate the issues identified above is determined by acombination of the following:Page 7

Application complexity - This is determined by the number of registry entries and files in theapplicationRemediation complexity – This is determined by the complexity of the issue and remediationactivityFor more information about application and remediation complexity, see Appendix C.Remediation action summaryEach action has an associated effort. The effort required to perform each action is used by EffortCalculator to estimate the time required to test and resolve each issue. The following table provides abreakdown of the remediation effort required.ActionAction DescriptionEffortApps *Action RAGRepackageApplication Repackaging RequiredEASY16XenAppXenApp steps need to be followedEASY4Additional Testing RequiredHARD6The application needs to beredeveloped to solve this issue.HARD7Change OSChange the Operating System Build MEDIUM3ShimShim description MEDIUM4AutoAuto descriptionEASY3ApplicationVirtualizationDeploy using an ApplicationVirtualization entRequired* This column may add up to a higher number than the number of applications tested becauseactions are associated with algorithms and applications may trigger more than one algorithm.Effort Calculator summaryEffort Calculator calculated the cost and duration of the migration of the application sample based ona combination of the identified issues, the complexity of the sample applications and theremediation actions, the size of the project team and their associated costs. Effort Calculator thenextrapolated these results to generate a total project cost and time for the migration of the entireapplication portfolio.The “without AppDNA” calculation is based on estimates of the number of expected issues and thecosts of the traditional testing and remediation process.Sample: 25With AppDNAWithout AppDNAFull portfolio: 25Months CostMonthsCost0.131580.131580.68237140.6823714Page 8

Savings0.58205560.5820556For information about the variables used in the calculations, see Appendix C.Page 9

Effort estimation “With AppDNA” explainedThis section explains the “with AppDNA” calculations. Some testing time is applied to all applicationsunless they are identified as exceptions. AppDNA is able to differentiate between applications thatcan be remediated and those that require further testing. Utilizing this granular knowledge ofapplications, an accurate calculation can be made in terms of the time and cost required for thestaging, testing and remediation of the application portfolio.The complexity of the applications is also taken into account in the calculations. AppDNA assessesthe complexity of the applications in terms of simple, normal and complex. For information abouthow AppDNA does this, see Appendix C.Sample applications25Staging111Testing132RemediationGreen beforeAmber afterApplications111Green afterTotal61861812271212Total days2.573.861.71hourshoursCost514772684Elapsed days0.510.770.57Portfolio esting132RemediationGreen beforeAmber afterGreen afterTotal61861812271212Total days2.573.861.71hourshoursCost514772684Elapsed days0.510.770.57Time to execute project 1.98Project manager cost1188Total Cost 3158Elapsed daysUSDUSDhourshours1.9811883158Page 10

Cost per appDuration per app126.320.33Effort estimation “Without AppDNA” explainedThis section provides more information about the “without AppDNA” calculations. Without priorknowledge of the application portfolio in terms of compatibility, complexity, potential resolutionsand targeted testing, it is not possible to create an accurate estimation of project time and cost.In order to create a reasonable estimate, the variables defined in Appendix C were used. Thecalculation assumes that all applications will be staged and tested and that a percentage ofapplications will require some form of remediation identification and actions.StagingTestingIdentify andfixDaysCostSample nd fix30120003.5771414.292858Indentifyand fix3012000Time to execute project 13.57Project manager cost8142Total Cost 23714Cost per applicationTime per applicationElapsed daysUSDUSDHours2510013.57814223714948.561.91Page 11

Appendix A: Installations Hosted on XenApp 2008R2 algorithm groupsAnomolous BehavioursUnusual aspects of an application that may result in unexpected behaviour.Best Practice ViolationsThe detection and reporting of applications that violate some established best practices.Applications co-existence issuesApplications that may not work well on the same machine in a TS environment due to resourceclashes.Unsuitable Terminal Services applicationsApplications with potential Terminal Services / Citrix PS compatibility issues.Deprecated ComponentsSpecific technologies present in previous releases of Windows have been deprecated from WindowsServer 2008 R2. These technologies represent a varied risk of incompatibility.DriversNew releases of Windows are provided with new driver specification. As a result certain driver typesare no longer compatible and represent a varied risk of incompatibility.Environment SettingsImprovements to security can result in components that previously worked in protected locations nolonger working.Hardcoded pathsPage 12

Hardcoded paths can result in failure on Windows Server 2008 R2 given the change in the pathsin the environment. It is also highly likely that a migration could result in a change in theenvironment and as such would require a change.Hard-coded paths are detected in vairous msi tables, file contents and registry keys. Thealgorithms look for hard coded UNC paths, drive letters and certain Windows XP folder paths.Obsolete ComponentsImprovements to native operating system technologies inevitably result in components previouslyavailable becoming obsolete. The absence of these obsolete components represents a significant riskto compatibility.Operating System VersioningTechnologies checking the operating system version may react in an undesirable way. These reactionsrepresent a varied risk of incompatibility.Performance considerationsApplications that may affect performance on a terminal server.Applications permission errorsApplications that may not be correctly installed for all users or applications that may not functionwell for standard users in a TS environmentApplications runtime errorsApplications that may not run correctly for all users in a TS environmentSession 0 IsolationThe attack surface of Windows has been reduced by initiatives such as Session 0 Isolation.Technologies unaware of this change represent a significant risk of incompatibility.Server Core ConsiderationsServer Core is a scaled down version of Windows Server 2008 and as a consequence certainapplications may not work on a core server build.Server ConsiderationsServer Considerations.Page 13

Windows shell compatibilityCertain applications may have shell extentions that are not 64bit compatible.Terminal ServicesThe reporting of applications that are Terminal services awareUser Account ControlMicrosoft have improved their adoption of the principal of least privilege. As a direct resultapplications are at varying degrees of risk, if they are not developed to operate according to thisprincipal.Windows Resource ProtectionMicrosoft have extended Windows File Protection to include registry keys and integrated theWindows Installer Service. These changes represent a medium to low risk of incompatibilities.x16 Bit ApplicationsPotential 16bit COM ReferencesPage 14

Appendix B: AppDNA product overviewAppDNA can interrogate large portfolios of applications to identify potential installation and runtimecompatibility issues. This is achieved by interrogating both the installer and the associated binaries togather key information about the behavior of the application. This gathered data or “applicationDNA” is loaded into the AppDNA database. AppDNA then runs sophisticated heuristic algorithms onthe application DNA to predict issues that are likely to be exhibited when the applications aredeployed on the target platform or technology.The algorithms take a number of data sets into consideration over and above the application’sinternal state, including external data from application compatibility lists, the Windows ProgramCompatibility Assistant (PCA) database and, when relevant, the operating systems you are migratingfrom and to, and other applications and their dependencies. In this way AppDNA produces a multidimensional view of the application and how it interacts with the target platform and siblingapplications.In terms of the AppDNA process, all Windows application types (internally developed or ISVapplications) and all formts (MSI or any installable format) can be processed. In addition, AppDNAcan capture Web applications, by importing their static Web source files or capturing their run-timeWeb pages (or both). AppDNA directly analyses the application and its files and does not requireagent-based data collection from the live network environment. This “light touch” approach makesAppDNA easy to adopt and makes for rapid analysis of large volumes of applications.Depending on which stage the project is at and how much detail is required, AppDNA producesreporting with the appropriate level of detail to facilitate planning, estimation or actual remediationactivity.AppDNA can integrate application and operating system DNA data with infrastructure anddeployment information from Microsoft System Centre Configuration Manager (SCCM) and ActiveDirectory. AppDNA also integrates with Lakeside SysTrack, which audits and tracks actual applicationuse within the enterprise. This enables AppDNA to provide information about which applications areused across your enterprise and by how many users and on how many machines.AppDNA covers a wide spectrum of operating systems and technology platforms in a modulararchitecture: Desktop Compatibility Manager – Compatibility for Windows client operating systemsServer Compatibility manager – Compatibility for Windows server operating systems64bit Manager – Compatibility for x64 operating system platformsVirtualisation Manager – Suitability for Microsoft App-V or Citrix XenApp streamingServer Based Computing (SBC) Manager – Compatibility for Citrix XenApp hostedQuality manager – Identification of application-to-application interoperability conflictsWebApp Compatibility Manager – Compatibility with Internet Explorer and FirefoxPage 15

Custom Reports Manager – Enables you to define new algorithms and algorithm groupseither based on existing algorithms and algorithm groups or new ones you write yourselfPage 16

Appendix C: AssumptionsApplication complexityThe internal complexity of an application affects the time it takes to remediate and test changesmade to it. Generally, the more complex an application, the longer it takes to test and ensure thatthe original functionality is not impaired.AppDNA categorizes application complexity as simple, normal, or complex. AppDNA assesses thecomplexity of an application by comparing its number of files and registry entries with configurablethresholds. In this report the following application values were used.Application complexityRegistry entriesFilesSimpleLess than 200Less than 100NormalBetween 200 and 5000Between 100 and 400ComplexMore than 5000More than 400The following figure provides a high-level view of the complexity of the sample applications. Notethat the proportion of applications in

The Effort Calculator uses the results from the AppDNA EstateView report view to gain an overall picture of the compatibility of the sample applications with Installations Hosted on XenApp 2008 R2. AppDNA categorizes compatibility issues using a red, amber and green (RAG) risk rating.

Related Documents:

Effort Calculator Forward Path Organization reports Export Reporting settings . Application dependency mapping — AppDNA 7.6 report algorithms analyze whether the applications, application . Contact Citrix support before upgrading AppDNA if the removal of families and suites will cause issues.

There is no Citrix Client after update push for upgrade from Citrix Plug-in 11.2 to Citrix Receiver 3.3. Issue. SCCM successfully uninstalled Citrix Plug-in 11.2, but the install of Citrix Receiver 3.3 did not process. Resolution. Run the "Citrix Receiver 3.3 Up

Citrix Receiver 3.3 correctly, all older version of the Citrix Client must be uninstalled. The following steps should be taken to make sure The all old Citrix Clients are uninstalled, and then install the new Citrix Receiver 3.3. . Once you uninstall a

Verify Citrix Workspace version a. Click on the desktop to bring up Finder and then click "Applications" under the "Go" menu. b. Locate and click on "Citrix Workspace" and verify the version is at least 18.9.0. The Citrix client was recently renamed from Citrix Receiver to Citrix Workspace. If Citrix Receiver is currently installed

Citrix Receiver 使得圖示可置於 Windows � 開啟 Citrix Receiver︰ 在「開始」畫面,輸入 Citrix,然後選取搜尋結果中的 Citrix Receiver。 針對 Citrix Receiver 啟用單一登入 1. 解除安裝預先安裝的 Citrix Receiver。 2. 從 HP 支援網站下載 Citrix .

Citrix Online Division 6500 Hollister Avenue Goleta, CA 93117, USA T 1 805 690 6400 www.citrix.com About Citrix Citrix Systems, Inc. (NASDAQ:CTXS) is a leading provider of virtual computing solutions that help people work and play from anywhere on any device. More than 230,000 enterprises rely on Citrix to create better ways for people, IT and .

Citrix Online Division 6500 Hollister Avenue Goleta, CA 93117, USA T 1 805 690 6400 About Citrix Citrix Systems, Inc. (NASDAQ:CTXS) is the leading provider of virtualization, networking and software as a service technologies for more than 230,000 organizations worldwide. Its Citrix Delivery Center, Citrix Cloud Center (C3) and Citrix Online .

sigurime, financë-kontabilitet, lidership dhe menaxhim burimesh njerëzore, administrim publik, lidership, e drejta publike, e drejta e biznesit, komunikim publik dhe gazetari ekonomike). Me VKM nr. 564 datë 28.05.2009 “Për hapjen e programeve të reja të studimit “Master i Nivelit të