App-V: Why would new users on RDS/Terminal Servers not get any App-V Applications?
I recently came across a situation where a customer was in a panic because newly provisioned users were unable to receive any applications on their RDS Servers. Existing users were actually able to launch applications just fine and they appeared to be pre-cached properly. The scenario always seem to be tied to specific users as all of the users leveraged roaming profiles to maintain consistency across the farm.
The first thing to always do in this situation is verify connectivity to the App-V management server. This was quickly done. In addition verification of user group/provider policy configuration was also very quick as all users were part of the same global group tied to the server’s provider policy.
The next test quickly confirmed the issue. From both a user experiencing this issue and a user not experiencing this issue, a simple SFTTRAY /refreshall was performed and it was quickly revealed that the RDS servers running the App-V client had been specifically placed in offline mode.
The Virtual Application Client could not refresh your publishing information.
The Application Virtualization Client is operating in offline mode and cannot perform the operation requested. Disable offline mode, ensure that you have a network connection, and then retry the operation. If the problem persists, report the following error code to your System Administrator.
Error Code: 4615186-19101601-0003100F
The interesting aspect is this was done only after the first batch of users had logged on and initially refreshed against the server. Then the “Online” value beneath the following registry key:
Was set to 0. Setting the key back to 1 allowed the new users to refresh and get applications upon login.
The administrator wanted to “cut down on excessive traffic” as he had read on a web site where this would be a good trick. As you can see from the example above, there are ramifications of doing this. In addition, this is the exact reason Microsoft offers Stand-alone mode as an option.
Microsoft App-V is the only application virtualization product capable of virtualizing Visual Studio 2010. However, you may receive the following error message when attempting to launch the primary development environment (DEVENV.EXE) within a Visual Studio 2010 package virtualized with Microsoft App-V:
The ‘Environment Package Window Management’ package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the /log parameter on the command line, and then examining the file ‘C:users<USERNAME>AppDataRoamingMicrosoftVisualStudio10.0ActivityLog.xml’.
Continue to show this error message?
This is nothing to be alramed about. This can happen if one or more of the following is missing/configured incorrectly on the App-V Client where the Visual Studio package is being deployed:
– The Microsoft .NET Framework 4 Full Profile
– The KB 2468871 Update
– Interference from the Windows Presentation Foundation Font Cache Service.
To resolve this issue, be sure to complete the following steps on all App-V Clients to which the virtualized package of Visual Studio 2010 will be deployed.
1. Install Microsoft .NET Framework 4 Full Profile. Using Microsoft Update, install all updates for Windows and .NET Framework. The full download for the .NET Framework 4 Full Profile can be found here:
2. Make sure that the following update was installed by Microsoft Update. If not, install it manually from the following location: http://www.microsoft.com/download/en/details.aspx?id=3556
3. Run services.msc and disable the Windows Presentation Foundation Font Cache service.