Archive for the ‘SCCM Client’ Category

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:


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

ConfigMgr “obsolete” clients

May 5, 2011 1 comment

Do you have clients that sometimes do not get any advertisements and you cannot figure out why. Have you checked to see if the client has multiple records in the ConfigMgr database? One or more of those records is likely obsolete. This means that the record was superseded by a newer record for the same client.

To get the client to see advertisements you can easily delete the obsolete record(s) from the console and then initiate the “Machine Policy Retrieval & Evaluation Cycle” on the client either manually or using SCCM Client Center or SCCM Right Click Tools.


Now that is only a short-term solution. In the console you can enable a task found in “System Center Configuration Manager – Site Database” – Site Management – SITECODE – Site Settings – Site Maintenance – Tasks”. There is a task named “Delete Obsolete Client Discovery Data”. This will not be a sure fire every time but will automate a good chunk of it.


The key with this task is to have it run at an interval greater than the heartbeat discovery schedule. For example if your heartbeat schedule is set to 6 days you would want this task to be set to delete data older 7 days.


Categories: SCCM, SCCM Client

SCCM Client – NIC Speed Duplex

February 17, 2010 Leave a comment
This is not the end-all solution but if your SCCM client is installed, appears to be talking tot he server, and it doe snot seem to work at all an easy thing to check is to verify that the NIC Speed/Duplex matches the switch.  If these do not match you could have some issues not only with your SCCM client but other applications and parts of the OS that require network access.  I reccomend you set your devices to AUTO/AUTO.
Categories: SCCM Client

SCCM Client – WMI Namespace ccmdcm Error

December 14, 2009 Leave a comment
When deploying the SCCM client you may get the error "Setup was unable to delete WMI namespace ccmdcm" in the CCMSETUP.LOG
A way to fix this is to to stop WMI, rename (or delete) %windir%system32wbemrepository and start WMI again. Wait a few minutes and try the installation again.
Categories: SCCM Client
%d bloggers like this: