Remote Assistance Settings not Sticking for Dual Monitor Shadowing in XenApp 6

October 25, 2011 4 comments

If you have used a solution similar to my post about Dual Monitor Shadowing in XenApp 6 you may have experience issues where launch and activation permissions get reset. I have found this to be an issue when there is a WMI corruption which makes the SCCM client repair. Specifically with Windows Server 2008 R2 with Citrix XenApp 6 I found that there is an issue where the WMI repository gets corrupted and then the SCCM client repairs and resets these values.

To remediate this you will need to determine why the WMI repository is getting corrupted. One hotfix we did apply in our environment was KB2465990 as we were getting the described behavior and errors.

Referenced hotfix:

Categories: SCCM, XenApp 6

Why I think DISM is awesome…

August 5, 2011 2 comments

Have you ever run into a situation where a NIC driver just will not install from a driver package in a ConfigMgr task sequence? The NIC driver works when you use it in WinPE. It will install in the full OS outside of the imaging process without issue (i.e. via Device Manager). It just will not install from “Auto Apply Drivers” or a “Apply Driver Package” in the task sequence. I have to say this can be really frustrating. This happened to me with Windows 7 32-bit and some Intel drivers. No version difference would help.

But, I used DISM (Deployment Image Servicing and Management) to install the drivers in the image that I captured and the NIC drivers installed without issue using that new image in the same task sequence. In fact I used the same drivers from the driver package that didn’t work in the task sequence. Nothing different other than installing them into the offline .WIM file of the captured OS.

That is why I think DISM is awesome!


Does McAfee Endpoint Encryption support the Advanced Format Drives with Windows XP as the OS loaded?

Sure it does…just not the way some of the devices have their BIOS configured and not officially supported by McAfee of course (see link below). Specifically the Dell E6320 and E6420 laptops have this issue. They comes with “RAID on” selected in the BIOS. If you have Windows XP on the laptop, this RAID configuration, and load McAfee Endpoint Encryption you will not be able to use the laptop. You won’t even be able to log in…

However, if you change the BIOS configuration to “AHCI” it will work…of course you will need to reconfigure your ConfigMgr task sequence to specify a different driver and model and then reimage first.


Endpoint Encryption Advanced Format Drive support link:

Dual Monitor Shadowing in XenApp 6

May 17, 2011 8 comments


***NOTE – you may need to reference Remote Assistance Settings not Sticking for Dual Monitor Shadowing in XenApp 6 in addition if you have issues with the settings sticking***

We have XA6 deployed and ran into that not so fun issue where shadowing does not work when either the “shadower” or “shadowee” have dual monitors. One option around this is to fork up some cash and buy a tool like GoToAssist.

Or for free you could use Microsoft Remote Assistance. This option worked really well for us because we are a ConfigMgr shop and the client helped us fast-track the workaround. With some suggestions and help from the Lead Sales Engineer from Citrix we did the following.

***NOTE*** I have not determined how to use group policy for the DCOM permissions yet.

***NOTE*** You will want to be careful when/if you modify the “Remote Tools Client Agent” security tab as this will reconfigure DCOM as it relates to RAServer – thus the need for policy or something to enforce these settings.

Configure Remote Assistance & DCOM:

  1. Install Remote Assistance in the Windows Server 2008 R2 OS (not installed by default)
  2. Run “dcomcnfg”
  3. Expand “Component Services – Computers – My Computer – DCOM Config”
  4. Navigate to “RAServer”, right click it, and select “Properties”
  5. Click on the “Security” tab
  6. Click on “Edit” under “Launch and Activate Permissions”
  7. Add the “ConfigMgr Remote Control Users” local group and grant “Local Launch”, “Remote Launch”, “Local Activation”, and “Remote Activation”
  8. Click on “Edit” under “Access Permissions”
  9. Add the “ConfigMgr Remote Control Users” local group and grant “Local Access” and “Remote Access”
  10. . Click on “Edit” under “Configuration Permissions”
  11.   Add the “ConfigMgr Remote Control Users” local group and grant “Full Control”

There are a few ways that you can initiate the Remote Assistance session. Each of these require that you get the server that the user is connected to. The best way is to have them open “Citrix Connection Center” and get the name of the XA6 server they are connected to.


Below are some of the options to start Remote Assistance:

  1. From a local device run “msra /offerra”
  2. From the ConfigMgr console you can right click on the device, select “Start” and then click on “Remote Assistance”
  3. You can take the command “msra /offerra” and create a Citrix XA6 published application
  4. You can use something like

Once Remote Assistance is started:

  1. you can put the server name into the name field and click “Next”. The following
  2. You can use the pull down menu to select the user and their session

Alternative Solution Reference Link:

Dell E6320, E6420, & E6520 mass storage drivers in ConfigMgr for Windows XP

May 16, 2011 7 comments


Unfortunately still need to drop a Windows XP SP3 image on our new Dell Latitude laptops (E6x20). I ran into some issues trying to determine the driver and model for the mass storage driver section in ConfigMgr. This was primarily due to the fact that the driver in the OEM image wasn’t as nice as other versions…it did not specify for some reason. Maybe it is Windows 7 SP1 in combination with the new drives?

Anyway, I checked the BIOS and found that the storage was set to “RAID on” and used the table found in the following link to determine that my Dell Latitude E6320 needed to be setup as follows for the Windows XP mass storage drivers:

Dell System


Vendor version

BIOS Setting for SATA Operation

OSD Driver Name

OSD Model Name

Latitude Exx20 R291722 ATA Intel® ESB2 SATA AHCI Controller

Intel(R) Mobile Express Chipset SATA AHCI Controller

Latitude Exx20 R291722 AHCI

Intel® ESB2 SATA AHCI Controller

Intel(R) Mobile Express Chipset SATA AHCI Controller
Latitude Exx20 R291722 RAID On Intel® ESB2 SATA RAID Controller

Intel(R) Mobile Express Chipset SATA RAID Controller


The selected driver is not applicable to any supported platforms

May 13, 2011 1 comment


Ever have one of those days where you think you are going crazy? I had one today related to an experience trying to import some Dell drivers for the new E6320 and E6420 laptops. The most important of the drivers for my ConfigMgr OSD task sequence are NIC drivers. The version that I needed for WinPE was But guess what? Every time I tried to import I got an error “The selected driver is not applicable to any supported platforms”. What?!?!?!

Apparently, if using Windows Server 2008 (not R2), you need to patch the OS for the import to work.

Per the KB:

Consider the following scenario:

  • On a computer that is running Windows Vista or Windows Server 2008, an application uses the SetupVerifyInfFile function to validate an.inf file.
  • The function uses the AltPlatformInfo parameter.
  • The version of the .inf file is newer than the version of the operating system.

In this scenario, the validation fails.
For example, assume that you install a Microsoft System Center Configuration Manager (SCCM) 2007 site server. Then, assume that you try to import a Windows 7 driver into an Operating System Deployment (OSD) image. In this scenario, the driver import fails. At the same time, you receive the following error message:

Error: Failed to import the following drivers:
<Driver file> The selected driver is not applicable to any supported platforms.

Note SCCM 2007 uses the SetupVerifyInfFile function to validate the .inf file.

KB979492 Link":

Something worth trying – Fix ConfigMgr Remote Tools

I have this in production using a modified Ron Crumbaker Web Remote Console v3.21 with a button that calls “PSEXEC.EXE” to remotely run the script below. More often than not this will fix Remote Tools if there aren’t client issues in general.

on error resume Next

‘Variables and Constants
Dim WshShell, objFSO, objNetwork, objShell
Dim strDirectory, strFileName,  objTextFile
Dim regPath, regValue

Set WshShell = CreateObject(“Wscript.Shell”)
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
Set objNetwork = CreateObject(“Wscript.Network”)
Set objShell = CreateObject(“WScript.Shell”)

Const ForReading = 1, ForWriting = 2, ForAppending = 8
Const HKEY_LOCAL_MACHINE = &H80000002

regPath = “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control\Enabled”
regValue = “1”

‘Create logs folder if it does not exist
strDirectory = “c:\Logs”
strFileName = “c:\Logs\RemoteToolsFix.log”

If objFSO.FolderExists (strDirectory) Then

 ‘WScript.Echo “No need to create ” & strDirectory
 Set objFolder = objFSO.CreateFolder(strDirectory)
 ‘WScript.Echo “Created ” & strDirectory
End If

Set objTextFile = objFSO.OpenTextFile (strFileName, ForAppending, True)
 objTextFile.Write (“RemoteToolsFix script ran at “)
 objTextFile.WriteLine Now

objShell.RegWrite regPath,regValue,”REG_DWORD”

Set objTextFile = objFSO.OpenTextFile (strFileName, ForAppending, True)
 objTextFile.Write(“Script finished at “)
 objTextFile.WriteLine Now


Categories: SCCM, SCCM Client
%d bloggers like this: