Virtualization

Just install like normal & not to the Q: - it may work the first time.

I must say that I'm curious too; some appliactions seem to be hardcoded to a specific directory (anyone experience with swift Alliance workstation?), you can install those the normalway, but afterwards they won't work (an executable want's to go to f.i. C:\Win32\app.exe instead of Q:\oldap.100\win32\app.exe.

There's always the possibility that it's an application you can't sequence.........

The virtual file system should be providing sufficient redirection for the application to work. Are you saying that the application is aware that it has been virtualized and is having issues being virtualized to Q:\oldap.100\VFS\Win32\App.exe?

I would like to add here that even if the application installer does not allow you to choose the installation path still it can be sequenced. You simply need to select the Asset directory on the Q: drive e.g. Q:\Myapp.100 when the sequencer asks where you installed the application after you stop monitoring. Sequencer will move the files to VFS and would generate the proper mappings to the paths in the SPRJ file. In case your application contains hard coded paths you might not be able to successfully complete the "Application Configuration Wizard" however in that case you can put everything in FB (first block), advisable only if the sequence is not of considerable size, or continue the configuration with the errors. In second case most likely your application would work 95% of the times without any issuses. The bits missed in the application configuration wizard are streamed on the fly when the application is launched on the user's machine. Only significant effect is the delay in the application launch which is neglible or unnoticable if a good network connection is in place.

We have a custom writtenn in house application (read: PITA developers who don't know how to write decent apps) and this one will ONLY run from C:\Program Files\.... We can virtualize the environment for it but the app won't execute unless it's being run from C:. To make matters worse, it checks a network share for updates as well. In order to get around this, we have to use a script during the OSD that copies the exe files to c:\program files and then executes from c: instead of %SFT_MNT%. The problem that this poses is that users don't have rights to write files there so we have to them use a TQCRunas script which elevates the copy command.

if you have an app that will only execute from a hard coded path, take the styrofoam noodle from the local pool and beat your developer until they fix their poor programming. if it's a dev out of your control, you'll have to use something like we did to get it to work through softgrid.

Hmm, the application must be aware that it has been virtualized because C:\Program Files will become Q:\<8.3 Folder Name>\VFS\CSIDL_PROGRAM_FILES\<Application Folder>.

I've never tried this but maybe the CorrectFilePaths application compatibility shim will fake things out enough to make life easier? I've never tried this either but here is a potential way to implement compatibility shims with SoftGrid / App-V.

http://blogs.msdn.com/cjacks/archive/2008/04/30/can-you-shim-applications-virtualized-in-softgrid.aspx

@AssmbLLYCoder

You are right....am able to sequence the applications which does not allow to change the install directory..

Thanks for your advice...and thanks to all for ur inputs here...sorry for late reply though...and btw is there any tips and trick menu or documents for troubleshooting..