Citrix Session Remote Start
FAQ
Response 404 - UPNNotFound
It may not really be caused by UPNNotFound, but most caused by StoreFront authentication for various reasons:
- Communication error between Session Remote Start and StoreFront:
- Open
Web.config, double confirm the StoreFrontServer option. A recommended practice is to set StoreFrontServer by copy from Receiver from Web Sites in StoreFront UI. Please note that the StoreFront store name is case-sensitive. - Try to open StoreFrontServer by browser, check if there is a connection or certificate error. (Do not need to login, just check if the web page can be visited normally.)
- Open CDF trace tool or enable Session Remote Start log file, check if there is any error detail.
- Open
- StoreFront issue: Open Event Viewer > Applications and Services Logs > Citrix Delivery Services to check StoreFront log
- FAS issue: For step 2, the error may be related to FAS, please refer to the FAS section of the checklist above.
Request Timeout
- Session Remote Start has a RequestTimeoutSeconds option in
Web.config. When request duration reaches the timeout, Session Remote Start will respond with status code 408 and body content. - Session Remote Start will never terminate http connection without response. Please check if there is any timeout related setting in the caller.
- For the LaunchResource API, there is an optional parameter
WaitForLogonNotificationrecognized astrueby default. For the VDAs really take a long time for launching,WaitForLogonNotificationcan be set to false. API will respond immediately and execute the launching process in the backend.
Remain in ‘Connected’ State
If a session remains in the Connected state, there may be an authentication issue.
- Please review the FAS configuration and check the Session Remote Start logs.
- In the DaaS environment, please check if the Cloud Connector is working properly. Pay special attention to whether the firewall is configured correctly and does not block traffic from StoreFront.
Remain in ‘Active’ State
If a session remains in the Active state, the logon script configured in the Group Policy on AD may have failed to trigger the disconnect operation. Verify the Group Policy configuration, especially whether it has been successfully applied to the VDA.
Copied!
Failed!