Currently we move the 2x application server from Windows 2000 Server (W2K) to Windows 2003 Server R2 (W2K3), and I find the problem of the new server. When published application (with drive mapping through login script) from new server is launched in 2x client, it cannot start for the 1st time, but there is no problem as re-click the published application after a few seconds (mostly less than 10 seconds). Then I compare between W2K and W2K3 login screen procedure. In W2K, it exactly finishes the login script as shown in attached screenshot（win2k), then launch the application. However, the login suddenly disappears after the screen “Applying your personal settings” under W2K3, and it says “fail to launch application as shown in attached screenshot(win2k3). Is it 2x’s issue or our server configuration problem? The login script I mentioned is on the server side, and we can't use 2Xserver without it. Because without it, it cannot start to map the drive. Our application must reply on the mapped drive. Double backslash (\\....... \........) does not work. Current Server Configuration: Windows 2000 Server Standard w/ SP4; 2x Application and LoadBalancer – Enterprise Edition version 8.0 (Build 829); Terminal Server mode: Application Server New Server Configuration: Windows 2003 Server Standard R2 w/ SP2; 2x Application and LoadBalancer – Enterprise Edition version 8.1 (Build 875); Licensing: Per User I also attached the log file Thanks&Regards,
2X waits for the drive from where you publish the application is available but there is a timeout (Can confirm to you the exact time). If the script takes oo long to execute you might expirience this problem. Please contact support for more help I suggest you ask for a feature request to either add the mapping from the publishing app directly or to configure the timeout
