|
Autor: Roberto Data: 2013-03-08 15:10:50 |
Hi, When the working directory of an app is a mapped drive, execution fails, logging the error: [GTE v3520 |W32] 2013.03.08 08:51:03: Admin: 111c :Error 53: Cannot start application. Loc [GTeInitializeCommunication] Info [SRV: invalid working directory,777,0] SysErr [0] For instance: * Full application path: C:\keyfinder.exe * Application working directory: T:\ Where T:\ is a mapped drive. Hope you can enable this functionality. Thanks, Bar.
|
|
Autor: Mirek (staff) Data: 2013-03-08 16:14:08 |
Hi, If you use Windows AD authentication, the drive may not be mapped on the user the application tries to log on (even if it is mapped on the user running Winflector server). If you use Winflector authentication, try to map your drives as Administrator. On Vista and Windows 7 (or server 2008) applications run as Administrator have access to drives mapped as Administrator only. Mirek |
|
Autor: Roberto Data: 2013-03-08 21:18:38 |
Hi, I'm using Windows AD authentication and the drive is automatically mapped on startup via GPO to every local and domain account. Nevertheless, to check both scenarios, I switched to Winflector authentication. Drive was mapped as Administrator with full access, but same error. Server is Windows Server Standard 2008 R2 64-bit. What else could it be? Thanks, Bar. |
|
Autor: Mirek (staff) Data: 2013-03-09 11:10:34 |
We will check it in our environment and inform you as soon as we get results. Thanks, Mirek |
|
Autor: Bob Data: 2013-03-10 16:12:58 |
Winflector does not load a full user session when a client connects -- it only launches the selected app and any child processes. In particular there is no explorer.exe started which means there are no mapped drives. I have been testing using the full UNC path of the .exe (rather than a mapped drive) and it works fine -- but in your case you are launching a local program and want the working directory to be their home drive. There are probably ways around this such as building a new custom .exe that will map the drive (maybe by querying the AD user account for the location or running the login script) and then launch the program (you would want the custom program to stay open until the child closes). I am not sure how this will work without testing but that seems to be the best bet. |
