It is quite easy to overlook this application as you may not face any challenges while sequencing RealPlayer 14.0
Nonetheless the challenge is File Associations don't get into the bubble.
I used the following environment
Sequencer: 4.6 x64
OS: Win7 64
1. Finish the sequencing process. Save the virtual App.
2. Open the package for upgrade
3. Add the missing file associations
4. Finish the package
DO NOT add the file associations while sequencing the application. They overwrite the default associations made by the application, effectively resulting in loss of data.
The application Neovest 5.5 has multiple issues when we virtualize it for Win7.
The same is applicable for any application which throws the above error. For Instance, Dreamweaver 2004
iPatch Manager 6.0 and
shows up the same error as well.
RegistryRoot="Software\\MarchNetworks\\Evidence Manager\\Version 2.0"
In the above file
Issue 1: Upon launching the shortcut, the below errors are seen.
Upon selecting OK, the following screen shows up
Install JRE 1.6 to T:\
Troubleshooting virtualized application could be a nightmarish experience if we don’t understand the usage of sfttray.exe
Installing an application to a folder in Mount point is considered to be an efficient way of sequencing application. A deeper look at the scanning operation performed during the sequencing operation would help us better comprehend the advantages of mount point installation.
As the application is installed to a mount point (Q:\), only required files are monitored by the sequencer. The tax on the sequencer to scan the entire C:\ is hugely removed in this case there by making it easily the efficient way to sequence an application.
Nonetheless, there are applications which refuse to install to a location other than C:\ (Virtual File System). Under these circumstances, the entire hard disk is scanned for system changes, making it much slower than mount point installation. Also, scanning the entire hard disk for changes would result in capturing files that are not actually used by the application.
From the above points, it is evidently visible that Mount point installation is the preferred method to sequence an application compared to VFS installation
The same issue is seen "Avaya Site Administrator 4.0" and can be fixed using the mechanism described above
In between the sequencing process, open the following files and update the hard coded paths in the file.
CSIDL_APPDATA\Quest Software\Toad for Oracle\SettingsLocation.ini
Sequencing "Attachmate Extra X-treme 9.0" for Windows 7 could be highly annoying without the below tip.
The Sequenced application launches with a "Server busy/retry" message every time the Extra session based application shortcut is launched.
Issue: issue is with the Vendor code which is the causative factor for the error.
Solution: Installing the service pack which is available from the vendor at the time of sequencing would fix the error.
"Attachmate Extra X-treme 9.0" is on the certified list of applications that run on Windows 7 32 as well as 64 bit OS. The earlier versions of the application DOES NOT run on Windows 7.
NOTE: Windows Compatibility list doesn't talk about requirement of the service pack. The list of Windows 7 compatible applications can be found using the below link
The below mentioned site shows up a list of software’s that are compatible with Win7 32 and 64 bit inclusive.
The URL provides ONLY the information about the compatibility of the software on Win7 platform.
A WORD OF CAUTION: This, by no means indicates whether the application can be successfully virtualized or not
For Instance, the application "Workshare Professional 5" shows a matching entry in both the categories of Win7 (32 and 64 bit). But Sequencing this application with complete functionality is next to impossible as the application has a printer driver
Off-late, i ran into a strange problem which would crash my "App-V Management console" while importing virtual applications into the console with a stereotyped Microsoft message Management console encountered a problem and needs to close down as shown below
To Fix the above problem, create the below mentioned registry key
Value: 0 (zero)
Close your console and open again. The annoying error wouldn't show up again :-)
Primary Objective of the blogs posted in this site would be to