Microsoft App-V Team published an article about how to patch a virtualized package of Office 2010. You can find original article by J.C. Hornbeckv here. With Microsoft Office 2010 you have the Office deployment kit for the initial App-V deployment and also the activation components that are added to it. However, it is a bit different to patch the Office 2010
Microsoft has published a new KB article about Run-As considerations when used in Application Virtualization Environments. Symptoms Applications whose manifests specify automatic elevation (for example mmc.exe) may require additional steps to work correctly using run-as in App-V environments. This is a common scenario for environments that require using separate credentials from the account used to log on to the desktop.
Microsoft published a new KB article regarding error 2C-000036B1 on App-V 4.6 after applying Microsoft Security Update KB2647174. Symptoms After applying Microsoft Security Update KB2647174 Microsoft Access virtualized with Microsoft Application Virtualization (App-V) may fail to launch with an error similar to the following: Application Virtualization Error The Application Virtualization Client could not launch Microsoft Access 2010 v1. This application has
Microsoft App-V Team published an article about an error you may receive after you have updated App-V Management Server to Service Pack 2 using Automatic Updates or Windows Server Update Services (WSUS) . You may have the following happen after the update: A remoting error occurred. Make sure the Management Console is properly configured and it has the same version as
Microsoft published new Knowledge Base article that talks about an issue you might run into when trying to install the Microsoft Application Virtualization client using the MSI instead of setup.exe. Fortunately it’s an easy one to resolve: ===== Symptoms When running the Microsoft Application Virtualization 4.6 Desktop Client (App-V 4.6) by running SETUP.MSI, you may receive the following error: Error
Microsoft has published a new App-V Knowledge Base article. This one covers the %SFT_SOFTGRIDSERVER% environmental variable: ===== Symptoms After modifying the %SFT_SOFTGRIDSERVER% environment variable, Microsoft Application Virtualization (App-V) packages may fail to load or may connect to an incorrect server. In some cases, you may receive a 0A-10000002 error (“The specified Application Virtualization Server could not be accessed. Try again
Microsoft App-V Team published an article about App-V 4.6 SP1 issue when running a virtualized App-V application starting from a network location. Currently some of Microsoft customers are reporting that they are having issues running a virtualized App-V application that is started from a network location such as a UNC path or a mapped network drive. When this occurs they
Pankaj Pande published an article on RDS Microsoft blog describing how to restrict users from accessing local drives on a RD session. Currently, when a user creates an RDP session or a RemoteApp program, they can see, and in some cases transverse, drives C and D of the RD Session Host server. They can also save anything on the desktop,
Steve Bucci, Microsoft App-V Team, published an article about an incredibly powerful feature of Application Virtualization 4.5 which is the ability to control the licensing of packages. Although App-V allows you to assign applications to specific users and groups, Application Licensing can allow further control of who can use the software and for how long. It is important to make
Microsoft has released a hotfix package that contains the latest hotfixes for Microsoft Application Virtualization (App-V) 4.6 Service Pack 1 (SP1) and that is dated April 2011. Issues that are resolved by this hotfix package The initial query of the App-V Windows Management Instrumentation (WMI) provider runs slowly when more than 100 virtual applications are published. This hotfix package also
