We appear to have the same issue in the same context (windows shell replacement with View). We've used the approach for years, but this is unreliable with 3.2 and 3.5 on 64-bit Windows 7. On "cancel" from the opening dialog, the client will often become invisible to the user (but the script and view client are in fact running). I think we want --hideClientAfterLaunchSession=true for these direct-to-view machines, but I'd be thrilled to use whatever works. The goal is to protect login credentials from subsequent users in lab scenarios.
↧