Last Friday Microsoft has released a hotfix package that contains the latest hotfixes for Microsoft App-V 4.6 All Languages and that is dated February 2011. As always, Microsoft recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new hotfix release contains all fixes that were included with the previous update
Microsoft App-v team published an article explaining error 29-000010FE when you redirect user data to a network share. ===== Environment configuration: Microsoft App-V desktop clients has their App-V User Data redirected to a network share. This folder is configured to be always available using Offline Folders/CSC (Client Side Caching). The issue is one where an application launch failure is displayed
Microsoft App-V Team published an article describing error code 0000C800 when trying to import a package on the App-V Management Server. Symptoms When you try to import a Microsoft App-V (SoftGrid) package on the App-V Management Console, you receive the following error message: Unexpected error occurred. Please report the following error code to your system administrator. Error code: 0000C800 Cause
Microsoft published a new App-V Knowledge Base article about Office 2010 issues on App-V . If you currently run a virtualized version of Microsoft Office or plan to do so in the future then this makes a great reference: ===== Summary This article discusses known issues and limitations when using virtualized Microsoft Office 2010 applications on Microsoft Application Virtualization (App-V)
Microsoft App-v Team published an interisting guide that explains how to configure Microsoft Application Virtualization (App-V) to both publish and stream applications using HTTP. For the purpose of this document Microsoft has configured a brand new Windows 2008 R2 server to offer these functions and utilize a Windows 7 App-V client. When choosing HTTP as your choice for streaming, we
Microsoft App-V Team published another quick tip on an issue you might run into where an application virtualized with Microsoft App-V may disappear and no longer become streamable after enabling drive encryption on App-V clients. This is due to the drive encryption locking the associated OSD files. If this happens and if the OSD files are not available after several
Symptoms The Microsoft Application Virtualization (App-V) 4.5 Management Server may appear to run out of available licenses and clients may receive the following error: You are not authorized to access this resource. Error code: 0A-20000193 Cause The stored procedure sp_SFTclosesessions in the management server database is used to close orphaned sessions, license sessions, application usage and licenses assignments that are
Symptoms A virtualized application on an App-V client fails to launch with the following error: The Application Virtualization Client could not launch application name. No connection could be made because the target machine actively refused it. Error code: xxxxxxx-xxxxxx2A-0000274D Cause This issue can occur if the HREF attribute in the application .osd file is configured to use the RTSPS protocol
One advantage of the Microsoft Application Virtualization (App-V) Sequencer is the capability of running via the command line. This allows for automating the sequencing of applications which do not require any special customizations in their guidelines or “recipes” for sequencing. The upgrading of a package can also be automated using the command line sequencer. The documentation for upgrading a package
After sequencing RSSOwl 2.x with Microsoft Application Virtualization (App-V) you may be able to launch RSSOWL during the monitoring and the launch phase, however after the second launch (and subsequent launches) the application fails to start with an application-specific error: “There are no more files” Cause This occurs due to a sharing violation with the initial configuration file and the
