We are just starting to evaluate App-v for our environment.  Likely picking the worst program to start with we are starting with an old outdated version of the Rumba terminal emulation software.  Ran through the sequence and deployed the app via SCCM 2012 SP1.  The app fails to launch referencing a NTG.dll file in the System32 directory.  If I copy that file manually to the local system32 folder the app will launch. 

The odd part is that when I edit the package and look at the Package Files I see that it has bundled in the NTG.DLL in the Systemx86 virtual file system but it appears the app is not looking into the VFS for the file.  I assume this is a common pitfall with very old apps.  Is there something I need to do to force it to look at the packaged system files, or some other workaround to this?

I was reading about the scripting hooks where I can kick off a script to copy the DLL to the local FS but that feels inelegant and I assume there is probably a better way.

Any guidance would be appreciated. 

0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Answer this question or Comment on this question for clarity