Documente Academic
Documente Profesional
Documente Cultură
Rick Berry, Escalation Engineer Mark Callahan, Escalation Engineer May 24th, 2011
Agenda
Case study for UPM issue on XenApp 6 Case study on XenApp 6 filtered policy issue
Problem Definition
Customer was experiencing hung sessions at logon
Symptoms
Black Hole User Profile Manager process still running
XenApp Servers
XenDesktop
Streamed/Delivered Desktops
My Settings
File Servers
Active Directory
Functional Details
GPO\User Configuration\Windows Settings\Folder Redirection\My Documents
File Server
\profiles\UserName\
File Server
\\server\UserHome\
My Documents
Troubleshooting Methodology
Complete System Dump PerfMon
Troubleshooting Methodology
Complete System Memory Dump
Troubleshooting Methodology
Performance Monitor
Troubleshooting Methodology
User Profile Manager Logs
[PID];WaitUntilChangeJournalIsProcessed: Waiting to finish change journal processing of partition: C Ah Ha! A suspicious log entry!
NTFS Journaling
Event Initial write operation NTFS file system action
The NTFS file system writes a new USN record with the USN_REASON_DATA_OVERWRITE reason flag set. For more information on possible reason flags, see the USN_RECORD structure. The NTFS file system writes a new USN record with the flag setting USN_REASON_DATA_OVERWRITE | USN_REASON_BASIC_INFO_CHANGE. The NTFS file system does not write a new USN record. Because USN_REASON_DATA_OVERWRITE is already set for the existing record, no changes are made to the record. The NTFS file system writes a new USN record with the flag setting USN_REASON_DATA_OVERWRITE | USN_REASON_BASIC_INFO_CHANGE | USN_REASON_DATA_TRUNCATION. If the user making changes is the only user of the file, the NTFS file system writes a new USN record with the following flag setting: USN_REASON_DATA_OVERWRITE | USN_REASON_BASIC_INFO_CHANGE | USN_REASON_DATA_TRUNCATION | USN_REASON_CLOSE.
File truncation
Close operation
Troubleshooting Methodology
NTFS change journal was showing an increased size of the identification field.
SCREENSHOT
Resolution
Based on the data learned from the NTFS change journal examination, a code change was made to handle changes to the size of the Update Sequence Number record and a hotfix was developed.
Resources discussed
Problem definition
Customer had a new XenApp 6 farm in place XenApp 6 Citrix policies (both computer and user settings) were being applied via Active Directory Group Policy Objects (GPOs) Some of the Citrix policy settings were filtered for Access Gateway connections and others were filtered by client IP When end users connect to the XenApp 6 server from an Access Gateway site, the filtered policy settings were not applying to the session
You can assign published applications and Citrix policies to worker groups Servers added to worker groups inherit settings
Automatic configuration of new XenApp servers by placing them in an existing worker group
Unfiltered policy
Applies to all servers or users Used when filters or granular control isnt necessary Use case: Specifying the license server that all farm servers will use
Adds a Citrix node in the Group Policy Management Console and Group Policy Object Editor Installed with Delivery Services Console
Must be installed on the same machine where Group Policy Objects are administered Can be installed on a standalone machine used for administrative purposes
User policies
Enables or disables specific features for user sessions Registry location: 32-bit components: HKLM\Software\Policies\Citrix\<SessionID> 64-bit components: HKLM\Software\Wow6432Node\Policies\Citrix\<SessionID>
Troubleshooting Methodology
Identify how the policies are being applied (e.g. Active Directory, DSC, both)? Are they pulling down properly?
What does output from Group Policy Results Wizard show? Keep in mind GPMC has to be run from XenApp 6 server.
Troubleshooting Methodology
Identify how the policies are being applied (e.g. Active Directory, DSC, both)? Are they pulling down properly?
What does out from Group Policy Results Wizard show? Keep in mind GPMC has to be run from XenApp 6 server.
Enable Citrix policy debugging (see CTX128413)
Setting these values to 0xFFFFFFFF writes the debug information to a log file: %SYSTEMROOT%\Temp\CitrixCseEngine.log Setting these values to 0x0000FFFF writes the debug information to a debugger such as DebugView NOTE: The same values have to be written to HKLM\SOFTWARE\Wow6432Node\Citrix\GroupPolicy
Next we search on the display name of our policy so we can get the GUID since the GUID is referenced more in the log
Name={52243C73-ED52-4539-B484-02098F5A88F4}, DisplayName=Test Policies, Link=LDAP://OU=RickBe,DC=REDGETLAB,DC=CTX
Citrix.Policy.Templates:WildcardMatch("*"
Citrix.Policy.Templates:AGTags.value,"*",true
"LastUpdate"="2011-03-27 04:12:12Z
Resolution
The investigation into this issue resulted in code change for the Delivery Services Console which was tested successfully by the customer This code change is currently being packaged into a hotfix for the Delivery Services Console
Resources discussed
Questions?
Download presentations starting Friday, June 3, from your My Organizer Tool located in your My Synergy Microsite event account