Guest Post by Niron Koren, ControlUp CTO team
This blog post is a short follow-up to my previous entry on slow logons troubleshooting. These updated script contains new registration phase and now covers the entire registration process Citrix XenDesktop, see below for details.
HDX connection phase
Since my last post about registration duration analysis we have a lot of great feedback, including some interesting inquiries receive and suggestions. One of them, more than any other was repeated the XenDesktop HDX director of compound phase was book (which is a phase which takes place before Windows will play its part) to the script.
The updated script now covers the entire registration process, clicks from the moment the user clicks on the published resource until the desktop is available. The new module works with the XenDesktop Monitor service via OData API query. The Windows session id is translated to a XenDesktop SessionKey used in the OData API query.
Logon phases
The following table lists the updated "Logon phases" table showing a summary of the registration phase that the script includes is. The new phase includes HDX connection and session Init:
Logon Phase Name | Logon Phase Description | start event | end event |
HDX connection | , the time steps when setting up the HDX client to VM. taken [1] | complete requiredBased on OData query HdxStartDate column. | Based on OData query HdxEndDate column. |
Session Init | When a user on the system, the initial Session Manager, a new instance of itself creates the new session to configure. The new Smss.exe process starts a Windows subsystem process and Windows login for the new session [2] | Log Name :. Security Event ID: 4688 (smss.exe Start) | Log Name: Security Event ID: 4689 (smss.exe end) |
operator | a network provider is a DLL which notify for a particular type of connection protocol [3] each time you log Winlogon this network operator is responsible, so that they can collect credentials and the user for authenticate their network [4]. Citrix PnSson is a joint on XenApp and XenDesktop VM found network operators | Log Name :. Security Event ID: 4688 (Mpnotify.exe Start) | Name Log: Security Event ID: 4689 (Mpnotify.exe end) |
Citrix Profile management | During sign copies Citrix UPM the 'user registry entries and files from the user memory on the local profile folder. If a local profile cache is available, the two sets are synchronized. [5] | Log Name: Application Event ID: 10 (User X Path to user store is ...) | Log Name: user Profile service event ID: 1 (Received user login notification to meeting X.) |
Profile | During the application, the system is loading the user's profile, and then configure other system components the user's environment in accordance with the information in the profile [6] | log name: user Profile service event ID: 1 (Received user Login notification session X.) | log name: user Profile service event ID: 2 (finishing the user registration notification on session X.) |
GPO also | , the domain policy and the settings for the user session, to force in a case of synchronous processing, the user will see their desktop in the application not see until the user is finished editing GP. [7] | Log Name: Group Policy Event ID: 4001 (processing of user login policies vary according to X) | Log Name: Group Policy event ID: 8001 (user logon policy processing for X Completed) |
GP scripts | [1945016dieAnmeldeskripts] running in the configured relevant GPO, in a case of synchronous logon scripts Windows Explorer does not start until the logon scripts have finished running. [8] Log Name: Group Policy Event ID: 4018 (startup script Logon for X) | Log Name: Group Policy event id : 5018 (Completed Logon script for X) | |
Pre-Shell (UserInit) | Winlogon runs Userinit.exe that running logon scripts, reestablishes network connections and then starts Explorer.exe, the Windows interface. [9] In RDSH meetings Userinit.exe leads the Appsetup [10] entries as Cmstart.exe the calls in-turn wfshell.exe | Log Name :. Security Event ID: 4688 (userinit.exe Start) | Log Name: Security Desktop Session: Event ID: 4688 (explorer.exe Start) Published Apps: event ID: 4688 (icast.exe Start) |
Shell * * (available only if the script ControlUp runs) | , the interval between the onset of desktop initialization and the time of the desktop was available for the user also includes the Active setup phase. [11] | Log Name: Security Event ID: 4688 (explorer.exe Start) | ControlUp argument - "Desktop Load Time" |
script download link
run the script
requirements:
- Windows PowerShell 3.0 and higher
- local administrator rights (query required for the local event logs)
- read -only administrator role in each XenDesktop site (even if full admin rights are present, it is recommended to read-only rights, but also to add)
- Activate the monitoring of process tracking via GPO or local security policy (secpol.msc) to support all target XenDesktop VDA
- to "older" user sessions is recommended to increase the security log size to 50 MB or 100 MB.
- supply target user session ID as a script parameter
- Updated Citrix Receiver (on the physical endpoint that initiates the target HDX session)
, it is worth noting that it may take a few seconds to fill for XenDesktop HDX connection times in the monitor service database.
Lead the following steps to run the script via PowerShell: Import
- the script to the shell to "Import-Module" command. (For example, "Import-Module C: Scripts AnalyzeXDLogonDurationAnalysis.ps1")
- You can import After the module call the function from the shell-Get-LogonDurationAnalysis, the function takes 4 parameters:
- -UserName:
- -UserDomain:
- -HDXSessionId:
- -CUDesktopLoadTime:
[optional]
- -UserName:
- example - Get-LogonDurationAnalysis -Username MyUser -UserDomain MyDomain -HDXSessionId 3
0 Komentar