Virtualization by Davis: “Technotes: Best Practices for Upgrading to the Latest Feature Pack Levels for XenApp 5.0 for Windows 2003” plus 4 more

Technotes: Best Practices for Upgrading to the Latest Feature Pack Levels for XenApp 5.0 for Windows 2003
KB: How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V
KB: Launching an App-V application fails with "Unable to initialize package information (0x00000000)" error
SolarWinds releases Virtualization Manager, now supports VMware vSphere and Microsoft Hyper-V
Technotes: HP LaserJet Bidirectional or hpzbdi Related Performance Issues

Technotes: Best Practices for Upgrading to the Latest Feature Pack Levels for XenApp 5.0 for Windows 2003

Posted: 19 Apr 2012 04:36 AM PDT

Technotes: Best Practices for Upgrading to the Latest Feature Pack Levels for XenApp 5.0 for Windows 2003

KB: How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V

Posted: 19 Apr 2012 01:16 PM PDT

Here's one more Knowledge Base article we published today. This one shows you how to sequence (virtualize) the ConfigMgr admin console in App-V.

=====

Symptoms

When trying to Sequence (virtualize) the System Center Configuration Manager 2007 (ConfigMgr) administrator's console, the resulting package will generate the following error and fail to run:

MMC cannot initialize the snap-in

Resolution

Using the steps below, you can virtualize the admin console and have it run successfully.

NOTE In the example below, it is assumed that we are sequencing the Microsoft System Center Configuration Manager 2007 R3 admin console for the 64-bit version of Windows 7 Service Pack 1.

1. Follow Best Practices for the Microsoft Application Virtualization Sequencer : http://technet.microsoft.com/en-us/library/dd351420.aspx

2. Build the clean system with 64-bit version of Windows 7 SP1 and join it to the domain.

3. Install the APPV 4.6 SP1 Sequencer with Hotfix 3 (http://support.microsoft.com/kb/2571168). Launch the Microsoft Application Virtualization Sequencer and select Create New Virtual Application Package.

4. Select Create Package (Default) option and Click Next. Note that Prepare the Computer for Creating a Virtual Package may give the Warning "Windows Defender is active". If so, launch the Services.msc snap-in and stop the Windows Defender service. After doing so, click refresh and then click Next.

5. Select the Standard Application (default) option and click Next.

6. On the Select Installer Screen, browse to "SPLASH.HTA" on the Configuration Manager (ConfigMgr) installation media and click Next.

7. Name the Package SCCMConsole.001 and leave other options as the defaults and click Next.

8. Once the ConfigMgr installation screen appears, click Install Configuration Manager 2007 SP2 and click Next.

9. Select Install or Upgrade an Administrator Console and click Next.

10. Accept license agreement and Click Next.

11. Select No, I do not want to participate right now and click Next.

12. Leave the Destination Folder to the default (i.e. C:\Program Files(x86)\Microsoft Configuration Manager Console\) and click Next.

13. Provide your site Server Name and Click Next, then Next again.

14. Ensure the Pre-check passes then click on Begin Install.

15. Once the installation finishes click Next and then click Finish.

16. Back on the Installation screen on the Sequencer, click on the "Run" option to install the ConfigMgr R3 prerequisite hotfix http://support.microsoft.com/kb/977384) and R3.

17. Provide the path to the 977384 hotfix and choose Install.

18. When complete and back at the Installation screen on the Sequencer, click on the "Run" option to install R3.

19. Click on Run and provide the path to R3's "SPLASH.HTA" and click Next and install R3.

20. When complete, click on I am Finished installing

21. Select the ConfigMgr console and run it. After launching the console close it. Click Next to review the installation report and click Next when you're done.

22. Select the Customize option and click Next

23. Now under Edit Short Cut screen, right Click and edit the ConfigMgr Console.

24 Click on "Change Icon…" and browse to "C:\Program Files\Microsoft Configuration Manager Console\bin\i386\" and select "SETUP.EXE"

25. Select the proper icon and provide the version No: 4.00.6487.2157

26. Click "Save"

27. Right click "ConfigMgr Documentation" and click "Edit"

28. Click on "Change Icon…" and browse to "C:\Windows" and select "hh"

29. Select the proper icon and click "Save"

30. Right click on ConfigMgr setup and select Remove.

31. Right click on ConfigMgr Setup Repair Wizard and select Remove.

32. Click next and then Run ALL.

33. Select the Target OS, click Next and then select Create the Package. The Package will be saved as SCMMConsole.001.

34. Copy the Package to the App-V management content share.

35. Edit the OSD file of ConfigMgr Console.OSD in Notepad. Change the VALUE of <SUBSYSTEM VALUE= "windows"/> to <SUBSYSTEM VALUE= "console"/> and save the OSD file.

36. Now follow the normal procedure to import the Package in to your APPV Management server and verify that the console is published to the APPV users.

When you double click ConfigMgr Console on an App-V client you may see the error "MMC cannot initialize the snap-in." If so, hold the Shift Key and right-click on ConfigMgr Console and select Run as different user. Provide whichever user credentials that have access to the ConfigMgr site server.

More Information

This is published on the Microsoft App-V blog here:

http://blogs.technet.com/b/appv/archive/2012/03/20/how-to-sequence-the-system-center-configuration-manager-2007-r3-admin-console-with-microsoft-app-v.aspx

Also see the following Knowledge Base article:

2559075 - Elevation and Run-As Considerations in Microsoft App-V Environments (http://support.microsoft.com/kb/2559075)

=====

For the most current version of this article please see the following:

2685079 : How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

KB: Launching an App-V application fails with "Unable to initialize package information (0x00000000)" error

Posted: 19 Apr 2012 11:02 AM PDT

Here's a new Knowledge Base article we published this morning. This one talks about a couple work arounds for an App-V issue where launching an App-V application fails with "Unable to initialize package information (0x00000000)":

=====

Symptoms

When launching an application virtualized with Microsoft Application Virtualization (App-V), the application fails to start and generates the following error message:

Unable to initialize package information (0x00000000)

Cause

This can occur when App-V is set to work in Full Infrastructure Mode (http://technet.microsoft.com/en-us/magazine/2008.10.appv.aspx#id0110023) and the Configuration Manager (ConfigMgr) client agent is installed on the same machine where the App-V client is already installed. When the Configuration Manager client agent is installed, it assumes that it should handle the virtualized applications. During the Configuration Manager client agent installation, the App-V client cache is flushed and App-V registry keys are modified, causing the error described above.

Resolution

There are 3 potential work arounds for this issue:

1. The ConfigMgr client agent takes managing virtualized applications when "Allow virtual application package advertisement" in the Advertised Programs Client Agent properties in the ConfigMgr console is checked. If this box is unchecked, it is then possible to run both ConfigMgr and App-V client agents at the same time. To modify this setting, open the ConfigMgr Console, expand Site Database, Site Management, <Site Name>, Site Settings, Client Agents; then open the properties for Advertised Programs Client Agent. The next time the client agents refresh (or if you kick off a Machine Policy Retrieval & Evaluation Cycle), the App-V client will become the default handler again.

2. The second option is to manually modify the registry keys on the client back to the original values. Thus, we can make the following modifications:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface

Change to the following:

LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>"
DDELaunchCommand"C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>"

However, keep in mind that if "Allow virtual application package advertisement" in the Advertised Programs Client Agent properties in the ConfigMgr console remains checked, it is possible that it will reset the registries to their previous values and the issue will reoccur.

3. The third option is to use ConfigMgr to manage the virtual applications instead of using the App-V management server. More info on this can be found here:

http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/APP-V/App-V_and_ConfigMgr_Whitepaper_Final.docx

More Information

Below are the App-V registry keys that are changed during the SCCM client agent installation:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface

LaunchCommand "C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"

DDELaunchCommand"C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"
Instead of the original values shown below:
LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>"

DDELaunchCommand"C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>"

=====

For the most current version of this article please see the following:

2694295 : Launching an App-V application fails with "Unable to initialize package information (0x00000000)" error

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

This posting includes an audio/video/photo media file: Download Now

SolarWinds releases Virtualization Manager, now supports VMware vSphere and Microsoft Hyper-V

Posted: 19 Apr 2012 11:25 AM PDT

Yesterday Solarwinds announced the release of a new version of its IT Management Software, Solarwinds Virtualization Manager.

Inherited from the acquisition of Hyper9 this product has been developed and now introduce, in this release, Hyper-V support allowing the management of heterogeneous virtual data center from a single console.

Virtualization Manager offers integrated VMware vSphere and Microsoft Hyper-V capacity planning, performance monitoring, VM sprawl control, configuration management and chargeback automation and integrates with SolarWinds Storage Manager for a deeper analysis of the storages.

Virtualization Manager supports VMware vSphere 5, VMware vSphere v4.x, VMware Infrastructure 3 (ESX 3.5+, ESXi 3.5+, vCenter 2.5+), Microsoft Hyper-V R1 or R2 (SP2).