User settings and Connection Group in App-V 5.0

User settings from a connection group member packages will not be transferred to its Connection Groups. Similarly, once the Connection Group is disabled, user settings from the Connection Group will not be transferred to its member packages.
Example:

1.     Sequence Google chrome application using App-V 5.0.

2.     Sequence Adobe shockwave Player using App-V 5.0.

3.     Add/Publish/mount Google chrome App-V Package.

4.     Launch Google chrome shortcut and set www.google.com as homepage.This setting will be stored in user profile location.

5.     Add/Publish/mount Adobe shockwave player.

6.     Now create a connection group for Google chrome and Adobe shockwave Player packages.

7.     Open Google Chrome and now you can see google.com is not seen as home page. This is because user settings will not be transferred to the connection group.

8.     Now set www.homepage.com as the new homepage. Close the shortcut and open the Google chrome package again. You can see the www.homepage.com been set as homepage.


9.     Now disable the connection group and re-launch the Google chrome shortcut, you can see the home page will be set to www.google.com and not www.homepage.com. This is because since we have closed the connection group, the user settings that was set inside the connection group will be broken and not reflected back to its member package.

Comments

Post a Comment

Popular posts from this blog

Advanced Installer 13.3 - fixes MSI launch condition issue in Windows 10 anniversary update 1607

Image
Earlier when trying to install the Advanced Installer created virtual package through MSI format in windows 10 anniversary update 1607, it failed to install with the below error. This issue is caused because of a launch condition in MSI which has been set to check for App-V client installed as a pre-requisite. Since App-V comes inbox with windows 10 v1607, the pre-req check fails with the above error. This was a known issue even with App-V created packages and it was reported back to Microsoft. Meantime I had a chance to talk with the Advanced Installer team about this issue. They quickly reported that they will look into this issue ASAP and come back with a fix. To my wonder they released an update within a short time period. You can have a look on their release note about this bug fix. http://www.advancedinstaller.com/release-13.3.html Now using Advanced Installer 13.3 when you create a virtual package and use the MSI to install in windows 10 1607, it installs fine witho...
Read more

UAC and App-V 5.0 Demystified

Image
There are some methods through which we can suppress UAC prompts when virtualizing using App-V 5.0. You can try the below methods which ever suits your need. 1. SET __COMPAT_LAYER: Edit the sequenced shortcut and add the below command. cmd.exe /c “SET __COMPAT_LAYER=RunAsInvoker & START Appname.exe” Note: There is a space in between SET and __COMPAT_LAYER. If you didn't leave any space it will throw an error. "SET' is not recognized as an internal or external command. 2. Registry Method: Right click on the shortcut and select properties-compatibility-privilege level- run as admin-apply. This will create a registry entry in the HKCU\HKLM based upon User/Machine selection. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers (or) HKEY_Current_User\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers Export the registry key and add it in the deployment config file and register it in the local machine. NOTE: Enable script exec...
Read more

Add custom scripts in AppxManifest.xml file using App-V 5.1 Sequencer

Image
In the Package editor under advanced tab, you can see the Manifest file tab which has been introduced in App-V 5.1. This doesn't exist in earlier versions of App-V. Using this tab, you can export or import the AppxManifest.xml file. Earlier if we want to do any custom changes we have to edit the deploymentconfig or userconfig.xml file(for adding scripts, editing FTA's etc). App-V 5.1 provides advanced way to edit those changes within the AppxManifest.xml. To do so, click on export as highlighted below in the Manifest file tab. This will export the AppxManifest.xml file to the local machine. choose the destination and click on save. Open the exported AppxManifest.xml using AppVManifestEditor. You can download the tool from here AVME AVME is a simple yet powerful tool to edit the AppxManifest file.My recommendation is not to edit the AppxManifest file manually. After opening the file using AVME,you can select the checkbox on left hand side to enable the type of script you want(Ma...
Read more