The application Neovest 5.5 has multiple issues when we virtualize it for Win7.
RegistryRoot="Software\\MarchNetworks\\Evidence Manager\\Version 2.0"
DDEAtom="MAP"
ConfigFile="<path>\\bin\\Evidence.dat"
]
In the above file
Issue Upon launching the sequenced version of Microsoft SharePoint Designer on Win7, the application repairs upon every launch
Eventviewer doesn't report back with any useful information for troubleshooting as well.
Solution
After the initial monitoring Phase, Install the SharePoint Designer to Q:\MSPD.2K7 (say)
While the monitoring phase still runs in the background,
Goto C:\Program Files\Common Files\Microsoft Shared\Office12\Office Setup Controller
Rename the existing "Setup.exe" to say "backup.setup.exe"
Copy "C:\Windows\system32\rundll32.exe" to "C:\Program Files\Common Files\Microsoft Shared\Office12\Office Setup Controller" and rename "rundll32.exe" to "Setup.exe"
Delete the below registry hive as well
HKCU\Software\Microsoft\Office\Common\UserInfo
Issue After physically installing the app, shortcut prompts for elevation when launched. This translates into an error while launching the virtualized shortcut which is "Requested Operation Requires Elevation"
Solution set the Environment variable as follows
__COMPAT_LAYER=RunAsInvoker
Issue Java is required for successful launch. Launching the shortcut on Win7 throws the following error.
Solution <WORKINGDIR> should be set to the location of the java (i.e <WORKINGDIR>T:\8.3\
If you are new to AppV, Errors which show up might sound greek and latin to you. A point in case is
After virtualizing applications, and launching them on Win7 might cause an "Requested operation requires elevation" error
Visually this is what they translate into
To solve the above problem, Add the below to the OSD File
<ENVLIST>
<ENVIRONMENT VARIABLE="__COMPAT_LAYER">RunAsInvoker</ENVIRONMENT>
</ENVLIST>
Issue Be it physical installation or virtual application, The shortcut fails to kick in on Win7. This doesn't mean the application can't be sequenced.
Solution During Sequencing process, an INI file named "Evidence.ini" ought to be located. Below shown is the content of the file
[
StartupFile="<path>\\startup.cat"
DumpPrefix="*MAPLog"
StartupFile and ConfigFile should be updated with appropriate value for successful launch of the application
While Sequencing VoloView Express 2.0 you might encounter an issue which would crash the sequencer.
Details of the error are as follows.
The Sequencer goes back to the initial phase of sequencing process upon clicking OK there by not allowing us to sequence the application successfully
Solution
The MSI(mostly) contains "RunOnce" key (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce) and registers lot of application related files.
This ought to be deleted either from the MSI before sequencing or from the registry in between the sequencing process.
These files should be manually registered for proper functionality.
About Me
- Ramesh
- A techie exploring the Microsoft Virtualization Technology In and Out