UPDATED: Best Practices for Application Virtualization (App-V)
Get link
Facebook
X
Pinterest
Email
Other Apps
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.
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...
In my earlier blog, I posted about how to create a transforms file to install a registry to 64 bit location in 64 bit OS using transforms in a 32 bit vendor MSI using Installshield tool. So, in this current post I will explain how to achieve this using a simple ORCA tool. 1) Open the MSI using ORCA tool. Select Tansforms from the menu bar and click on New Transforms. This will create a new transforms where you can do the modifications. 2) Add a new row in Component table and create a new component and set the Attribute field to 256 as shown below. Component attribute 256 - Set this bit to mark the component as a 64-bit component. ( https://msdn.microsoft.com/en-us/library/aa368007(v=vs.85).aspx ) 3) Add a row in FeatureComponents table and map the newly created component to an existing Feature. 4) Go to Registry table and select the registry for which needs to be installed to 64-bit path and set the Component field to the newly created obove component. 5) After doing the changes, s...
In my previous blog I had posted about a simple registry tweak to publish packages globally/User by just right clicking and selecting the option. But in that method, it will not use the dynamic configuration file. And so I have covered how to do that in this blog. copy the below code in notepad and save it in .reg format. After saving, double click on it and register the keys. Windows Registry Editor Version 5.00 [ HKEY_CLASSES_ROOT \.appv] @ = "appvex" [ HKEY_CLASSES_ROOT \appvex] [ HKEY_CLASSES_ROOT \appvex\shell] [ HKEY_CLASSES_ROOT \appvex\shell\Publish Globally] @ = "&Publish Globally" [ HKEY_CLASSES_ROOT \appvex\shell\Publish Globally\command] @ = "cmd /c start /b /wait powershell.exe -nologo -ExecutionPolicy bypass -file \"c:\\Publish globally.ps1\" \"%1\"" [ HKEY_CLASSES_ROOT \appvex\shell\Publish to User] @ = "Publish to &User" [ HKEY_CLASSES_ROOT \appvex\shell\Publish to User\command] @ = "cmd /c start /...
Comments
Post a Comment