application

Later today when I opened my blog to update a new post, I found that I already had quite some posts in drafts section. Few of them are outdated and few needed to be updated to the current date. I will be updating them and post them as soon as possible. The first post to clear from my draft bucket is how to add multiple scripts in App-V. Earlier in App-V 5.0 it wasn't possible to run multiple scripts in deploymentconfig.xml or userconfig.xml file. But in the latest App-V 5.1, it supports running multiple scripts both in deploymentconfig.xml or userconfig.xml file with the help of ScriptRunner.exe. ScriptRunner.exe comes along with the App-V 5.1 client and gets installed in the client folder. You can check how to use the ScriptRunner.exe and its parameters by opening up CMD and running ScriptRunner.exe /? You can add multiple scripts by adding them as arguments to the ScriptRunner.exe using -appvscript parameter. The scripts run in the order as how we give them. But note we need to a...

Check the official KB article to download the hotfix. https://support.microsoft.com/en-us/kb/3139245 This hotfix resolves many issues that were reported earlier like vfs folder not getting released when user logs off etc..

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.

Watch out the video about current best practices to be followed including PVAD for some applications and other useful stuffs from App-V Legend Steve Thomas Due to some issues, have updated the video to another link: http://app2pack.blogspot.com/2016/02/updated-best-practices-for-application.html

Recently I came across a post in TechNet as the scripts added in deploymentconfig.xml file is not getting triggered when using the App-V generated MSI file for publishing in App-V 5.1. I planned to do a simple test to check this case before giving out confirmation from my end. Below I have compared this scenario between App-V 5.0 SP3 and App-V 5.1 generated MSI's. App-V 5.0 SP3: Step 1- Created a virtualized package. Step 2- Added a script in deploymentconfig.xml file which would do a simple file copy. Step 3- Ran the App-V 5.0 SP3 generated MSI and found that it is using the deployment config file and triggered the script and copied the file as expected. Step 4- Reverted the machine to clean state. Step 5- Edited the deployment config file and removed / in </MachineScripts> Step 6- Ran the MSI and see the below error.  Step 7- Checked in App-V event log and see the exact reason for failure that tag is not closed properly. This proves that App-V 5.0 packages use deployment c...