SESSION CODE CLI 307 When Things go Wrong

SESSION CODE: #CLI 307 When Things go Wrong… How to effectively and Efficiently Troubleshoot Application Virtualization (App-V) Deployments Justin Zarb Senior Premier Field Engineer Microsoft Corporation http: //appvguy. com http: //blogs. technet. com/virtualworld @justinzarb

Session Objectives and Takeaways What YOU will Learn about issue prevention: pre-requisites, validation Identify troubleshooting techniques for common issues Review common issues discovered in the field, their root cause, and resolution Demos: Tools to parse logs for decision making on top issues, analyzing trends “How To” for log files (Appendix) Which, where, when, how Additional issues, root cause, resolution 3

Agenda App-V Management Server troubleshooting App-V Server architecture Troubleshooting scenarios Deployment Application Provisioning Care and feeding Client troubleshooting App-V Client architecture Troubleshooting scenarios Deployment Publishing virtual applications to users Delivering virtual applications to users Ongoing use of virtual applications (runtime) 4

App-V Management Server Architecture App-V Management Server App-V Management Service 5 App-V Management Console

Scenario #1 –Server Deployment App-V Management Server log %temp%Softgrid-Server-Setup. txt Enable MSI installation logging HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoft Windows Create a new key – ‘Installer’ Create a new string – ‘Logging’, value ‘ voicewarmup!’ Install pre-requisites for server components Management Server: No pre-requisite software Management Console: No pre-requisite software Management Service IIS role with defaults, plus: ASP. NET (and dependencies) Windows Authentication IIS Management scripts and tools 6

Deployment Considerations for setup of: Secure Server (RTSPS) Request and install certificate Make sure Management Server service account has access to private key SQL Server® Confirm your IT admin has admin rights to the database (required by the installer) If no admin rights to DB - Creating a New Application Virtualization 4. 5 Database Using SQL Scripting Active Directory® (AD) Create group for App-V Server admins and users 7

Deployment Configure Windows Firewall If using RTSPS, allow connection port 322 If using RTSP, allow connection to program files sghwdsptr. exe, sghwsvr. exe Configuring port 554 not sufficient Share content directory 8

Deployment Set up for streaming virtual apps or. osd Launch IIS Manager Configure MIME type for. osd , . sft In Default Web site, add Virtual Directory, set physical path to path of shared content directory Advantages Streaming easily integrates with existing IIS infrastructure Can stream to remote clients in the cloud Better performance in high latency, low bandwidth networks Limitation Clients need to be configured to point to new. sft, perform publishing refresh to get new package versions 9

Deployment Verify App-V Management Server service is started Connect to App-V system through Management Console Add Management Service – hostname, port If successfully added – web service, database are up and running 10

Deployment Additional check for Management Service URL check: Launch URL http: //webserver_name/Soft. Grid. Management/Authorization. r em? wsdl You get “System. Nullreference. Exception: Object reference not set to an instance of an object. ” Database connection check: Search Sft. Mgmt. udl in install directory In file properties, click Connection tab or open file in OLE DB Core Services Test connection 11

Deployment – Issue #1 Issue: When installing Management Service, ‘Error 25120 unable to create the required IIS virtual directory’ 12

Deployment – Issue #2 Issue: Error 25122 when installing Management Service Root Cause: Attempted to install Management Service on a machine where ‘Default web site’ (in IIS) was renamed Resolution: Re-name to ‘Default Web Site’ in IIS Manager 13

Deployment – Issue #3 Issue: Error connecting to Management Service in management console – Error code: 0000 C 824 Investigation: Error message to user, error message in install log 14

Agenda App-V Management Server troubleshooting App-V Server architecture Troubleshooting scenarios Deployment Application Provisioning Care and feeding Client troubleshooting App-V Client architecture Troubleshooting scenarios Deployment Publishing virtual applications to users Delivering virtual applications to users Ongoing use of virtual applications (runtime) 15

Scenario #2 – Application Provisioning Copy virtual package to CONTENT folder Management Server Console: Set Content path or URL for. osd/icons in Server MMC (System Options) Create a new application group and import applications Verify HREF in. osd points to. sft in package folder (unless ASR/Policy/envt. variable is set on client) 16

Application Provisioning Ensure at least one app is imported on the server Perform policy refresh on a client Launch app 17

Application Provisioning– Issue #1 Issue: Apps successfully imported on server and publishing refresh successful on client, but no apps appear in client console Investigation: Review sftlog. txt (client log file) Root cause(s): Content folder is not shared, OS Tag mismatch, user not added to correct group entitlement Resolution(s): Share content folder, add OS to OSD, add user to correct group 18

Application Provisioning– Issue #2 Issue: Error 2 A-80090322 when performing a publishing refresh or launching a virtual application or “The target principal name is incorrect. “ Root Cause: App-V Management Server service is configured to logon as a domain user instead of default Network Service Account and Service Principal Name (SPN) has not been registered Resolution: Set the SPN on the Management Server setspn -A Soft. Grid/<FQDN of your machine> <Your. DOMAIN><Your. Service. Account. Name> setspn –A Soft. Grid/<Net. BIOS name of your machine> <Your. DOMAIN><Your. Service. Account. Name> 19

Scenario #3 – Care and Feeding To narrow down an issue during debugging, reduce concurrent activity (not for perf. issues) Set the number of cores to 1 In Server MMC, select the server in the default server group, the go to properties – Advanced tab Restart the server service 20

Care and Feeding Centrally manage and review multiple servers through consolidating location where logs are generated 21

Care and Feeding – Issue #1 Issue: Management Server service stopped, gives error on restart Investigation: Review log file sft-server. txt Root cause: SQL Server service stopped Resolution: Restart the SQL Server service and restart the management server service 22

Care and Feeding Used to help make business decisions on buying software Sent to the App-V data store via publishing refresh 23

Care and Feeding – Issue #2 Issue: Virtual applications usage data is not accurate Investigation: Review refresh policy settings on the client and the server Root cause: Publishing refresh disabled on client or set to ‘Refresh publishing on user login’ Resolution: Set 1 day refresh policy on client by setting ‘Refresh publishing occurs every’ Best Practice is to deploy refresh policy setting on server (overwrites the policy set on client) versus client 24

Care and Feeding – Issue #3 Issue: After server install, cannot change database the server is pointing to Investigation: Review ‘Reset administrators’ in Server MMC Root Cause: UI does not work Resolution: 1. Edit Sft. Mgmt. udl: Data Source, Initial Catalog 2. Edit registry on server: ü HKEY_LOCAL_MACHINESOFTWARE MICROSOFTSOFTGRID4. 5SERVER ü SQLDatabase. Name, SQLServer. Name, SQLServer. Port 3. Edit database info in Default Server Group properties Logging tab->Edit SQL Database 4. Restart the management server service 25

Care and Feeding Taking Advantage of the Info in sft-server. txt http: //blogs. technet. com/virtualworl d/archive/2009/04/10/getting-to-gripwith-the-app-v-server-log-file-sftserver-log. aspx Demo

Agenda Management server troubleshooting App-V server architecture Troubleshooting scenarios Deployment Adding package, importing virtual applications Care and feeding Client troubleshooting App-V client architecture Troubleshooting scenarios Deployment Publishing virtual applications to user Delivering virtual applications to user Ongoing use of virtual applications (runtime) 27

App-V Client Architecture App-V Client Core Listener (sftlist. exe) Desktop Configuration Client (sftdcc. exe) System-Guard 28 VSA (sftvsa. exe) Front-End Component (sfttray. exe) File System Transport

Client Logging MSI Installation Log Similar to App-V Server Installation App-V Client Log File %program. Data%MicrosoftApplication Virtualization Clientsftlog. txt Transport Log Files %program. Data%MicrosoftApplication Virtualization Clientsftnta. txt %program. Data%MicrosoftApplication Virtualization Clientsftlist. txt System Event Logging 29

Scenario #4 – Client Deployment Prevention – Preparing for Client deployment Install or upgrade App-V client Setup. exe (GUI or CLI) Detects and installs pre-requisites Setup. msi (GUI or CLI) Does not detect or install pre-requisites Enable MSI logging prior to install Pre-requisites: VC++ 2005 Redistributable, VC++ 2008 Redistributable, error reporting 30

Deployment For successful install: Find string ‘ 1603’ or ‘value 3’ – should give no results For failed install: Find string ‘ 1603’ – indicates custom action failed Find string ‘value 3’ Indicates an install error String ‘error’ can give false positives Find string ‘SWICore. Initialize’ Indicates start of a custom action Helps identify the failed custom action Find string ‘Is. In. Bad. State()’: Error – one or more drivers was not uninstalled Find the uninstalled driver – Sc qc <driver name> Delete driver file(s) and re-install 31

Deployment – Issue #1 Issue: Error 25010. A prerequisite for installation is missing. Installation cannot continue Investigation: Error message to user – error message in MSI log Root cause: Installing using setup. msi, which does not install pre-reqs Resolution: Install using setup. exe or manually install pre-reqs prior to running setup. msi 32

Scenario #5 – Publishing Virtual Apps to Client Publishing sequence: Publishing refresh occurs on the client User authenticated by management server Server sends applist. xml file to client Client retrieves. osd files and icons Publishing provides to client: Shortcuts File type associations Package definition Content source location Recommended blog posting: http: //blogs. technet. com/softgrid/archive/2009/02/17/a-story-of-a-publishing -refresh-request. aspx 33

Publishing – Issue #1 Issue: Publishing refresh fails Investigation: Verify server is accessible (ping it) Telnet to server If still no issue found, RDP to the server box and verify Management Server service is running Root cause: Management Server service has stopped Resolution: Restart the service and do publishing refresh again 34

Publishing Virtual Apps to Client Decoding Client Error Messages 22 characters 4605 F 5 -19 D 0810 A-10000004 Characters: 1 -6 7 -12 13 -14 15 -22 Version and build File and line info where error occurred Error category code Problem code (error text in sfterr. xml) Note: Characters 1 -12 vary with each build, but 13 -22 are constant across builds. 35

Publishing Virtual Apps to Client Decoding Client Error Messages Example of decoding client error message 4605 F 5 -19 D 0810 A-10000004 Minimum of last 10 characters required for root cause analysis 460 Release number 5 F 5 Hex for Build number 1525 19 D 081 File ID and line where error occurred 0 A Error category: Net Transport Agent 10000004 Problem ID: info from sfterr. xml 00 UNK Unknown 0 D SGD System. Guard Driver 01 FEC Front-End Component 0 E INT Client Interface 02 SVR Server 0 F VSM Visual Service Manager 03 LST Listener 10 SEQ Sequencer 04 COR Client Core 11 SYN Synchronization Manager 05 XML Library 12 DCC Desktop Config Controller 06 USR User Library 13 RPC Remote Procedure Call 07 FSL Core FS Interface 14 PFM Platform Library 08 FSI FS Interface 15* DDE Launcher 09 FSD FS Driver 16* MDE Minidump Exception 0 A NTA Net Transport Agent 17* MAPI 0 B CDC Codec 18* SCR Script 0 C SGL System. Guard Library 19 -1 F Reserved

Scenario #6 – Delivering Virtual Apps to Users Streaming Scenario Delivery sequence: User double-clicks on application icon Application content is streamed to the client cache Application is started Delivery begins at message ‘checking for updates’ Delivery completes at message ‘Launching <app name> (100%)’ 37

Delivery – Issue #1 Issue: App launch fails with error 4604 EE 819 D 07 F 2 A-0000274 D Investigation: Review sftnta. txt Root Cause: Cannot contact server Management Server Service Stopped Resolution: Restart Management Server Service 38

Delivery – Issue #2 Issue: Application launch fails with error 4604 EE 81690140 A-20000194 Investigation: Check sftlog. txt (client log), sftserver. log, Management Server Console Root Cause(s): o The. sft file path or the. sft file name is invalid. o App no longer exists but shortcut still present o The Provider Policy does not exist Resolution: 39 o Set the correct path to SFT file o Delete the shortcut o Set correct Provider Policy in. osd

Client Log Parser Utility Getting to grips with app-v client-logparser utility launch times http: //blogs. technet. com/virtualworl d/archive/2009/04/20/getting-togrips-with-the-app-v-client-log-parserutility-launch-times. aspx

Scenario #7 – Ongoing Use of Virtual Application (Runtime) Failures during regular use of virtual apps (after launch completes) Isolate runtime issue Launch when app is 100% loaded in client cache Eliminate issues related to publishing and delivery of app Error message dialog box does not indicate App-V error 41

Ongoing Use of Virtual Application Best to have full dump (including kernel and user) Must dump Kernel if entire system is deadlocked Most useful info for CSS to troubleshoot 42

App-V Resource Kit Tools New kit released Feb 2010 Tools App-V Application Listing Tool App-V SFT Parser Tool App-V Client Log Parser Utility App-V Cache Resizing Tool App-V Dynamic Suite Composition Tool New tools added Application Virtualization SFT View Tool Application Virtualization MSI Compat Transform 43

Session Objectives and Takeaways What YOU will Learn about issue prevention: pre-requisites, validation Identify troubleshooting techniques for common issues Review common issues discovered in the field, their root cause, and resolution Demos: Tools to parse logs for decision making on top issues, analyzing trends “How To” for log files (Appendix) Which, where, when, how Additional issues, root cause, resolution 44

Troubleshooting App-V Client Log Files Client Installation Log, in %temp% starts with „msi“ SFTLOG. TXT, log levels Critical Error Warning Information Verbose Sftlist. exe /resetlog or /verboselog or in Registry 46

App-V Client Log Files cont. App-V Client Network Transport Agent (NTA) log file HKLMSOFTWARE. . . Soft. Grid4. 5ClientConfigu ration REG_DWORD Nta. Log. Mask 47

NTA Log Levels 48 Level Description 0 x. FFFF All logging 0 x 0000 No logging 0 x 0000 FFFF All errors 0 x 00000001 Socket errors 0 x 00000002 General errors and control flow 0 x 00000004 RTP errors 0 x 00000008 RTCP errors 0 x 00010000 Information 0 x 00020000 NTA interface 0 x 00040000 Session creation and deletion 0 x 00080000 RTSP connection creation and deletion 0 x 00100000 RTP packets received 0 x 00200000 RTCP packets received

App-V Client Log Files cont. SFTLDR. Log Can be used to see if a virtualised Service or virtual com is problematic Be carefull it grows very quickly In the Systemguard Key set „Unhandled. Exception. Filter. Location“ REG_SZ and the location where you would like to write the log 49

ETL Tracing All Filesystem Information will be logged here %Allusersprofile%documentsSoftgrid Client There are two Files SFTFS. ETL. OLD Service restart, recycles the files 50

Client Dumps When the App-V Client crashes , it write a Dump File Location: %Alluserprofile%DocumentsSoftgrid ClientDumps Can be configured via Registry 51

App-V Server Log Files Located in the Installtion Dir Logs SFT-Server. log Change logging In the Start Parameter box for the Service add the – d switch with the Loglevel you want to use 0: Transactions 1: Fatal Errors 2: Errors 3: Warnings 4: Informational 5: Debug (Verbose) 6: Trace 52

App-V Server Log Files cont. Server Setup Log File Created during Installation Located in %Temp% MMC Log File In the Install Dir SFTmmc. log Set in Registry HKLM…Softgrid4. 5Management Console, add Log. Level Dword and set to 1 Default is only errors will be logged 53

Sequencer Log Files Logs are stored in Insall Dir logs SFT-Seq-log. txt Majority of logging goes in this file Everything that the seuqencer does goes in here (Uploads, downloads, Service starts / stops etc. ) SFTrbt. txt Reboot Log File Records actions during the reboot processing SFTCall. Back. txt Logs all Process starts and stops as seen by Systemguard 54

Sequencer Log Files cont. Filter. log Recorded by Systemguard when any file activity occurs Must be dumped with Dumplog. exe SFTrpc. txt Created by SFTRPC. EXE Contains Process starup and shutdown Verbose diag Info about each monitored shortcut 55

SCCM Log Files Virtual. App. log Tracks virtual application registration and publishing VApp. Launcher. log Tracks virtual application launch by user. 56

Tools and Techniques Client Log Parser App-V Resource Kit Parses Log files and enable a comfortable way of anlysis Examples: 01 App-VClient. Log. Parser. exe /P: c: logs /O: c: temperrors. txt /LF /N: 5 02 App-VClient. Log. Parser /P: C: logs /N: 5 /M: 2 /R /O: C: resultserror. txt 57

Pivot Tables With the Parsed Log Files you can create Pivot Tables Examples: 58

Virtual Services Three ways to disable virtual Services On the Sequencer, Tools – Options uncheck „Allow Virtualization of Service“ Machine Wide (debugging only) set „Disable. Virtual. Services“ dword 00000042 under HKLM. . . Softgrid4. 5SystemguardOverrides Per Virtual Environment – add the following Tag to the OSD: 59 <VIRTUALENV> <POLICIES> <VIRTUAL_SERVICES_DISABLED>TRUE</VIRTUAL_SERVICES_DISABLED> </POLICIES>

Virtual Services cont. Check SFTLDR. Log to verify that Virtual Services are disabled You see On. Sft. Ldr. Start: -- Virtual Services Disabled – 60

Virtual File System Two ways to disable it Machine Wide set „ Disable. VFS“ dword to 1 under HKLM. . . Softgrid4. 5SystemguardOverrides OSD <POLICIES> <VIRTUAL_FILE_SYSTEM_DISABLED>TRUE </VIRTUAL_FILE_SYSTEM_DISABLED> </POLICIES> 61

Virtual Registry Two Ways to disable it Machine Wide set „ Disable. VREG“ dword to 1 under HKLM. . . Softgrid4. 5SystemguardOverrides OSD <POLICIES> <VIRTUAL_REGISTRY_DISABLED>TRUE </VIRTUAL_REGISTRY_DISABLED> </POLICIES> 62

Local Interaction Set in the OSD <POLICIES> <LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED> </POLICIES> Places COM Objects out of the Bubble into the OS It‘s active for the whole Package You see a not in the SFTLDR. log if it‘s enabled 63

Process Monitor / Explorer Process Monitor can look inside the Bubble With 4. 5 the Procmon Driver was modified Get input directly from the App-V Driver To enable it use /externalcapture Captures also Stack information Process Explorer don‘t need a view in the Bubble Shows Tree View of start‘s and dependencies Also shows Handle information Stack Informations 64

App-V Error Codes

Additional Resources 66

Additional Resources - Blogs Official App-V Blog http: //blogs. technet. com/softgrid Virtualworld Blog http: //blogs. technet. com/virtualworld/ German App-V Blog http: //blogs. msdn. com/sgern/ 67

Additional Resources - Groups App-V Guru (App. Virt) http: //appvirtguru. com/ German Soft. Grid and App-V User Group http: //www. dsgug. de/ 68

Additional Resources - Technet App-V Tech Center http: //technet. microsoft. com/enus/appvirtualization/default. aspx Whitepapers http: //technet. microsoft. com/enus/appvirtualization/cc 843994. aspx 69

Appendix Log Files: Which to use Where to find When to use How to enable and change log level 70

Scenario 1 – Deployment (Server) Which: Server install log files Soft. Grid-server-setup. txt MSI<random string>. txt (MSI*. txt) Where: %TEMP% When: Issues/messages during server install Server installed using setup. exe Soft. Grid-server-setup. txt, MSI*. txt Server installed using setup. msi MSI*. txt How: Generated by default (error logging only) For debugging, enable MSI logging (more MSI*. txt) 71

Scenario 2 – Adding Package, Importing Apps Scenario 3 – Caring and Feeding Which: Sft-server. txt Where: %Program. Files%Microsoft System Center App Virt Management Serverlogs When: For any issues/messages after server is installed How: Generated by default (log level 3) For debugging, change log level here: HKEY_LOCAL_MACHINESOFTWAREMICROSOFTSOFTGRID4. 5SERVERSOFTGRID_LOG_L EVEL Log level range is 0 -5 for Transactions, Fatal Errors, Warnings, Informational, and Verbose Restart the Management Server service for the new log level to take effect Reset to default after troubleshooting to avoid overhead 72

Scenario 2 – Adding Package, Importing Apps Scenario 3 – Care and Feeding Which log file: sftlog. txt (client log) Where: C: Program. DataMicrosoftApplication Virtualization Client (or look for location in registry) When: Validating server deployment through client interaction 73

Scenario 4 – Deployment (Client) Which: MSI<random string>. txt New log file for every install or upgrade Where: %TEMP% When: Issues/messages during client install/upgrade How: Generated by default (error logging only) For debugging, enable MSI logging (more MSI*. txt) Date stamp on start and end of log Information on product version, name, and install outcome at very end of log 74

Scenario 5 – Publishing Virtual Apps to Client Which: sftlog. txt (client log) Where: C: Program. DataMicrosoftApplication Virtualization Client (or look for location in registry) When: For any client error/message How: Default log level: informational Log location can be configured in registry Log level can be reset in Client MMC 75

Deployment Default MSI log v/s log with MSI logging enabled 76

Publishing Virtual Apps to Client Sftlog v/s Event log Sftlog At information log level, both provide similar details Verbose sftlog level required to troubleshoot complex issues 77

Scenario 6 – Delivery of Virtual Apps to the Client Which: Sftlist. log if streaming protocol is HTTP/S Sftnta. txt if streaming protocol is RTSP/S Where: Not generated by default, need to enable Generated in client install path Log file location cannot be changed When: For errors/messages after launch starts and before it completes 100% 78

Scenario 6 – Delivery of Virtual Apps to the Client (contd. ) How: Enable/update log level for sftlist. log HKEY_LOCAL_MACHINESOFTWARESoft. Grid4. 5ClientConfiguration Create Value Name: "TRAN" (dword) Value data: 0 to 6 Log level: 0 -6: NEVER, 1; ALWAYS, 2; FATAL, 3; ERROR, 4; WARN, 5; INFO: VERBOSE Enable/update log level for sftnta. txt HKEY_LOCAL_MACHINESOFTWARESoft. Grid4. 5ClientConfiguration Create Value Name: " Nta. Log. Mask " (dword) Value data: Verbose level: FFFF, Info: 00030002, Error: 0002, Off: 0 Restart the Application Virtualization Client Service (sftlist) for changes (enable/update) to take effect 79

Deployment – Issue #4 Issue: Error connecting to Management Service in management console - Error code: 0000 C 800 and 0000 C 824 Investigation: Error message to user Root Cause: Management Service we are attempting to connect to is not installed on the host machine; more info on root causes for C 800 error at http: //go. microsoft. com/fwlink/? Link. Id=114648 Resolution: Install management service on host machine

Scenario 1 – Server Deployment – Issue #5 Issue: Error code 0000 C 801 connecting to Management Service in management console Investigation: Error message to user Root Cause: Windows Authentication Service not found Resolution: Add role service in Server Manager for Windows Authentication 81

Scenario 1 – Deployment – Issue #6 Issue: Error code 0000 C 81 B connecting to Management Service in management console Investigation: Error message to user Root Cause: ASP. net, which is used to load the Management web service, is not installed Resolution: Add role service in Server Manager for ASP. net 82

Deployment – Summary of C 800 Errors Discussed error code: 0000 C 81 B 0000 C 801 0000 C 824 0000 C 800 It is strongly recommended you visit the following links: Error code: 0000 C 800 http: //go. microsoft. com/fwlink/? Link. Id=114648 Error code: 0000 C 806 http: //go. microsoft. com/fwlink/? Link. Id=114647 83

Scenario 2 – Adding Package, Importing Apps Demo Review Adding Package, Importing Apps If you add a package first, then you also need to import apps If you import apps first, then package is added automatically 84

Adding Package, Importing Apps – Issue #2 Issue: Apps successfully imported on server, publishing refresh successful on client, but some apps do not appear in client console Investigation: Review sftlog. txt Root cause: . osd path not set correctly Note: During importing of app, OSD path set in this location on server gets inserted into the path to fetch. osd files; if. osd files do not exist in this location, apps will not get published to the client Resolution: Ensure. osd path set in server ‘system options’ correctly represents the location of. osd files

Scenario 3 – Caring and Feeding – Issue #4 Issue: After server install, create a new App-V data store Investigation/Root Cause: No out-of-box capability Resolution: Uninstall and re-install server to create a new data store, or Follow manual steps using the white paper, ‘Creating a New Application Virtualization 4. 5 Database Using SQL Scripting, ’ found at http: //technet. microsoft. com/en-us/appvirtualization/ cc 843994. aspx 86

Caring and Feeding – Issue #5 Issue: Server performance seems to be slow, or client requests are timing out Investigation: Review sft-server. txt, sftlog. txt Look at memory cap in Server MMC for server core Compare memory cap with memory consumption by each server core (sghwsvr. exe) Root Cause: Server file cache may have exceeded the maximum memory set Resolution: Increase the Maximum Memory Allocation, restart service 87

Scenario 4: Deployment – Issue #2 Issue: Want to upgrade from App-V 4. 5 using setup. msi, but don’t know what the pre-reqs are for App-V 4. 6 Resolution: 1. Launch setup. exe (in sandbox environment) – it will show the pre-reqs 2. Install the listed pre-reqs on client machine Note: The Microsoft application error reporting pre-req can be found in Supportwatson directory of media. 88

Scenario 6 – Delivery – Issue #3 Issue: Deleting an app from the client MMC does not remove it from the cache – the appears to be removed from cache, but launching the app loads it from the cache v/s stream Root cause: Misleading error message – delete does not remove app from cache, unload does Resolution: Unload the app Unload will not remove app from the cache if there are other loaded apps in the package 89

Delivery – Issue #4 Issue: Unloading a package does not reduce the used cache size Investigation (example): Current cache size (reserved cache size in client) – 5 GB Unload a package 3 GB in size Check Reserved cache size – same as 5 GB, will not reduce Load a package 1 GB in size Check Reserved cache size – same as 5 GB, will not increase Root Cause: Cache size cannot be reduced if you unload package, available cache can be reused by other virtual packages but it cannot be reclaimed by the client Resolution: To reclaim the reserved cache: HKEY_LOCAL_MACHINESOFTWARESoft. Grid4. 5ClientApp. FS Set State (dword)= 0, Reboot machine Drawback – All apps will be removed from cache and Reserved cache size will become ~0 90

Delivery – Issue #5 Issue: Error when changing (reducing) maximum cache size Root Cause: Once set, maximum cache size cannot be reduced Resolution: Reduce the set Maximum cache size: HKEY_LOCAL_MACHINESOFTWARESoft. Grid4. 5ClientApp. FS Set File Size = new maximum cache size, State (dword)= 0 Reboot 91

Delivery – Issue #6 Issue: ‘Could not connect to stream URL’ error to user Investigation: Error message in sftlog – need to update log level to verbose The package could not be locked in cache due to lack of unallocated space Could not set lock status to TRUE, could not load app Not enough space in the Application Virtualization cache Report the following error code to your System Administrator – error code 4504 B 4 -16 D 10 E 0 A-0000 E 029 Root cause: Could not load app, as client cache is full Incorrect error message to user, correct error code in sftlog Resolution: Remove apps from cache – unload in client MMC Increase cache size – properties of 'Application Virtualization‘ in client MMC 92

Delivery – Issue #7 Issue: Cannot find/see available space in App-V client cache Resolution: 2 options: 1. (Max size – Reserved Cache size) 2. In Performance Monitor tool, add performance counter “App Virt Client Cache” Create new data collector set Add perf counters Select log format ‘comma separated’ 93

Delivery – Issue #2 (cont) Issue: Cannot stream app Investigation: Review sftnta. txt/sftlist. txt, sftlog. txt Root Cause: Invalid HREF for sft in. osd file %SFT_softgridserver% not set as an environment variable or policy ASR set incorrectly Resolution: For an app that fails to launch, ensure Package URL and Source are accurate in app properties

Resources www. msteched. com/Australia www. microsoft. com/australia/learning Sessions On-Demand & Community Microsoft Certification & Training Resources http: // technet. microsoft. com/en-au http: //msdn. microsoft. com/en-au Resources for IT Professionals Resources for Developers 95

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U. S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.