For example, if you are publishing Explorer, then Explorer will not launch unless LogoffCheckerStartupDelayInSeconds is set to 10 seconds (hexadecimal) or higher. There are a couple registry values that can be tweaked to give the application more time to launch. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved.
WARNING! Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Taking a snapshot of the VDA is not a bad idea. You need to perform these changes on one VDA first, put the rest of the machine on the maintenance mode to test and verify the results. If you see any of the above issues then the following setting should fix the session load VDA end issues. If you see Remote Desktop took too long to load then it means your session is not getting enough time to load the app and it needs more time to successfully load profile/session before projecting to the client machines. Also, check the XenApp/XenDesktop server to view the event log.Check Profile Manager, Folder Redirection configuration if any which could also contribute to such issues. Go to Delivery Controllers and view the application status: If you see the session at the pre-login status and then it vanishes then that means that Session is successfully trying to load but something is not letting is keeping it from the successful load.Go to StoreFront and try to load the application from the StoreFront web host web URL, if the slowness is still there then it eliminates the possibility of any client-side network slowness issues posed between Netscalers and Studio.Here are the additional troubleshooting steps.
0 kommentar(er)
