1Y0-201 · Question #66
Scenario: Session Prelaunch is configured for all users in an environment. A new user complains about slow logon. A Citrix Administrator finds that Session Prelaunch is NOT working as expected for the
The correct answer is C. The Citrix Receiver is installed without the /includeSSON switch.. Session Prelaunch requires Single Sign-On (SSO) to pre-authenticate the session before the user fully logs on. If Citrix Receiver is installed without the /includeSSON switch, SSO is not enabled and Session Prelaunch cannot function.
Question
Scenario: Session Prelaunch is configured for all users in an environment. A new user complains about slow logon. A Citrix Administrator finds that Session Prelaunch is NOT working as expected for the new user and is working as expected for all other users. What is the likely cause of this issue?
Options
- AThe user is NOT using the HTML5 Receiver.
- BThe NetScaler Gateway plug-in is NOT installed.
- CThe Citrix Receiver is installed without the /includeSSON switch.
- DThe user certificate is NOT installed on the endpoint client device.
How the community answered
(38 responses)- A11% (4)
- B18% (7)
- C66% (25)
- D5% (2)
Why each option
Session Prelaunch requires Single Sign-On (SSO) to pre-authenticate the session before the user fully logs on. If Citrix Receiver is installed without the /includeSSON switch, SSO is not enabled and Session Prelaunch cannot function.
HTML5 Receiver does not support Session Prelaunch, but the symptom here is that prelaunch is failing rather than being unsupported, and the question does not indicate the user is on HTML5 Receiver.
The NetScaler Gateway plug-in is required for remote/VPN access scenarios but is not a dependency for Session Prelaunch functioning on an internal network.
The /includeSSON switch during Citrix Receiver installation enables the Single Sign-On component, which Session Prelaunch depends on to silently authenticate and start a session in the background before logon completes. Without this switch, the SSON component is absent on that endpoint, so the prelaunch session cannot be authenticated, causing the slow logon the user experiences. Because all other users have Receiver installed correctly, only the new user - whose Receiver lacks /includeSSON - is affected.
A missing user certificate would cause authentication failures at a certificate validation stage, not specifically break Session Prelaunch while leaving all other users unaffected.
Concept tested: Session Prelaunch dependency on Citrix Receiver SSON installation
Source: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/sessions/logon-prelaunch.html
Topics
Community Discussion
No community discussion yet for this question.