UPDATED: Best Practices for Application Virtualization (App-V)

Since previous video had some technical issues, updated the blog with the new one. This webinar is from Steve Thomas explaining current best practices for App-V.



Comments

Post a Comment

Popular posts from this blog

Solution for Error 17002 when uninstalling Office 365 (2016) when apps like word, excel, outlook are open

Image
When uninstalling office 365 silently, it is failing only when any applications like word, excel are kept open. This is because during uninstall, office checks for any running applications and prompts the user to close it which is not happening in silent uninstall. When uninstalling in UI mode, it prompts to close when any office apps are open. Since in silent mode office is not able to do this, it fails with an error code 17002. You can check in the log file for the error code 17002. To overcome this just add the property FORCEAPPSHUTDOWN with Value="True" in the uninstall config.xml file. This property will force shutdown any running office apps. Example: <Configuration>  <Remove>  <Product ID="O365ProPlusRetail" >  <Language ID="en-us" />   </Product>  </Remove> <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Display Level="None"/> <Logging Path="c:\temp\" Name...
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