locked
SMS remote Control connects but only shows a blank screen RRS feed

  • Question

  • Pardon me if this question has already been asked and answered, but I'm not having any luck figuring out a solution!

    I have a newly added windows xp workstation added to the domain and sms and I only get a blank screen when I try to run the remote control through sms.  Clicking on the 'golden' key (or any of those icons) in the top right corner of the remote control dialogue doesn't do anything.  Initially, the remote control feature DID work a few times, but I cannot figure out how to get it to work anymore.  The system has SP2 installed and I can't even determine if that is either the culprit or how to get around it. Our SMS server is on a windows 2003 server.

    The other thing I've noticed is that when I try to run the remote tools to that workstation I will sometimes get the message that remote tools isn't installed!  When I see that, I run a repair on the components in the sms applet in control panel and then it will again at least let me 'connect' from the sms console but still only show me a blank screen.  The subnet for this system is defined in the site boundaries, so I don't understand why that component should disappear occasionally.

    I've tried all sorts of things including restarting the sms services, rebooting, leaving the firewall turned OFF, all to no avail. Again, I seem to connect to the remote control, but I only get a blank screen.

    Any help is greatly appreciated.  And if this isn't the best forum where I can find please do point me in a better direction.  Thanks!

    Wednesday, April 18, 2012 11:54 PM

Answers

All replies

  • The blank screen is related in general to a NIC driver problem on the client machine, so the first step is to making sure that the last NIC version is installed.

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1

    Thursday, April 19, 2012 8:37 AM
  • Thank you very much Bechir for your suggestion. 

    While I do not see an updated driver on the Dell web site, I do see one on the intel web site so will try that.  I do have another question while that is in process though.  Last nite while I was searching for an answer to this I felt positive that I ran across a link that said that SMS did not support windows xp with service pack 2 unless it was SMS SP 4 or SMS SP5.  I cannot refind that article and now I am confused which version of SMS I actually have installed and if this is true.  When I look at 'Help > About Systems Management Server it tells me that I have:  2.50.3174.1000.

    Any ideas?  Thanks!

    Thursday, April 19, 2012 8:42 PM
  • Hi,

    I think you're confused between SMS 2.0 and SMS 2003. Well, "2.50.3174.1008" means that you've SMS 2003 SP1. The SP4 and SP5 are for SMS 2.0 and the last SP for SMS 2003 is SP3.

    Yes you're right, your SMS version does not support Windows xp sp2 nor sp3 ==> You have upgrade to SMS 2003 SP3 http://www.microsoft.com/download/en/details.aspx?id=9901 ; http://technet.microsoft.com/en-us/library/cc179762.aspx


    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1


    Friday, April 20, 2012 8:15 AM
  • Hello Bechir,

    I meant to update to say that it will take us some time to apply SP3 and I will let you know how it goes when when we do. 

    Wednesday, May 2, 2012 3:39 PM
  • Hello, I'm back sooner than I thought I might be and hoping you are still able to help!

    We have upgraded to SP3 and we are still having the same problem!  What else can we do to help troubleshoot the problem?  One additonal piece of information I can provide is that when we are already logged into the workstation with SP2 (using RDP) we can remote control it using SMS.  But if we are not already logged in then we just get a blank screen.

    Saturday, May 5, 2012 9:28 PM
  • Hello,

    Have you upgraded the SMS client on computers also? Are the computers using the last video card driver? Have you checked remctrl.log on that xp machine?


    Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

    Sunday, May 6, 2012 10:11 AM
  • The SMS Client has been updated. I will report back about the video card driver.  Here are the contents of the latest remctrl.log file:

    ======= Logging initialized for module "C:\WINDOWS\System32\MsiExec.exe" =======  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.334 2012><thread=3156 (0xC54)>
    ********** Loading RCSvcs - Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.334 2012><thread=3156 (0xC54)>
    _RCSVCS(MSI): Entering StopDeleteWUSER32  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.334 2012><thread=3156 (0xC54)>
    RCSvcs - Stopping WUSER32 service.  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.334 2012><thread=3156 (0xC54)>
    RCSvcs - WUSER32 service stopped, return code 1.  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.334 2012><thread=3156 (0xC54)>
    StopDeleteWUSER32: StopWUSER32 returned 0x1  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.350 2012><thread=3156 (0xC54)>
    _RCSVCS(MSI): Leaving StopDeleteWUSER32  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.350 2012><thread=3156 (0xC54)>
    ********** RCSvcs - Unloading Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 10:57:51.350 2012><thread=3156 (0xC54)>
    ======= Logging initialized for module "C:\WINDOWS\System32\MsiExec.exe" =======  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 11:00:21.203 2012><thread=1840 (0x730)>
    ********** Loading RCSvcs - Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 11:00:21.218 2012><thread=1840 (0x730)>
    _RCSVCS(MSI): Entering SecureRegKeys  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 11:00:21.234 2012><thread=1840 (0x730)>
    _RCSVCS(MSI): Leaving SecureRegKeys  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 11:00:21.343 2012><thread=1840 (0x730)>
    ********** RCSvcs - Unloading Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Thu Apr 19 11:00:21.343 2012><thread=1840 (0x730)>
    ======= Logging initialized for module "C:\WINDOWS\System32\CCM\CcmExec.exe" =======  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:22.859 2012><thread=2096 (0x830)>
    ********** Loading RCSvcs - Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:22.859 2012><thread=2096 (0x830)>
    _RCSVCS(CCM): Entering InstallW2KDrivers  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:22.859 2012><thread=2096 (0x830)>
    ======= Logging initialized for module "C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe" =======  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.546 2012><thread=848 (0x350)>
    ********** RCSvcs - Starting Remote Control Service Manager **********  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.546 2012><thread=848 (0x350)>
    RCSvcs: Install Win2k devices, return success/failure status  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.546 2012><thread=848 (0x350)>
    InstallNT5Devices: Starting installation of Win2K device drivers  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.546 2012><thread=848 (0x350)>
    FindDevice(*SMS_MOUSE): found SMS Virtual Mouse  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.921 2012><thread=848 (0x350)>
    InstallNT5Device(*SMS_MOUSE): driver is up-to-date  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.921 2012><thread=848 (0x350)>
    InstallNT5Device(*SMS_MOUSE) succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:23.937 2012><thread=848 (0x350)>
    FindDevice(*SMS_KEYBOARD): found SMS Virtual Keyboard  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.093 2012><thread=848 (0x350)>
    InstallNT5Device(*SMS_KEYBOARD): driver is up-to-date  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.093 2012><thread=848 (0x350)>
    InstallNT5Device(*SMS_KEYBOARD) succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.109 2012><thread=848 (0x350)>
    FindDevice(*SMS_DISPLAY): found Microsoft SMS Mirror Driver  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.265 2012><thread=848 (0x350)>
    InstallNT5Device(*SMS_DISPLAY): driver is up-to-date  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.281 2012><thread=848 (0x350)>
    InstallNT5Device(*SMS_DISPLAY) succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.281 2012><thread=848 (0x350)>
    Checking if idisw2km service is enabled  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.281 2012><thread=848 (0x350)>
    InstallNT5Devices: succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.312 2012><thread=848 (0x350)>
    ********** RCSvcs - Ending Remote Control Service Manager **********  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Thu Apr 19 11:00:24.312 2012><thread=848 (0x350)>
    SpawnProcess: exit with code 0  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.421 2012><thread=2096 (0x830)>
    _RCSVCS(CCM): Leaving InstallW2KDrivers  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.437 2012><thread=2096 (0x830)>
    _RCSVCS(CCM): Entering InstallStartWUSER32  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.437 2012><thread=2096 (0x830)>
    RCSvcs - Creating WUSER32 service.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.453 2012><thread=2096 (0x830)>
    RCSvcs - WUSER32 service created, return code 0.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.468 2012><thread=2096 (0x830)>
    RCSvcs - Starting WUSER32 service.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.484 2012><thread=2096 (0x830)>
    RCSvcs - WUSER32 service started, return code 0.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.624 2012><thread=2096 (0x830)>
    _RCSVCS(CCM): Leaving InstallStartWUSER32  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.656 2012><thread=2096 (0x830)>
    ********** RCSvcs - Unloading Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Thu Apr 19 11:00:24.656 2012><thread=2096 (0x830)>
    ======= Logging initialized for module "C:\WINDOWS\System32\MsiExec.exe" =======  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.504 2012><thread=4024 (0xFB8)>
    ********** Loading RCSvcs - Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.504 2012><thread=4024 (0xFB8)>
    _RCSVCS(MSI): Entering StopDeleteWUSER32  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.520 2012><thread=4024 (0xFB8)>
    RCSvcs - Stopping WUSER32 service.  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.520 2012><thread=4024 (0xFB8)>
    RCSvcs - WUSER32 service stopped, return code 1.  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.520 2012><thread=4024 (0xFB8)>
    StopDeleteWUSER32: StopWUSER32 returned 0x1  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.520 2012><thread=4024 (0xFB8)>
    _RCSVCS(MSI): Leaving StopDeleteWUSER32  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.520 2012><thread=4024 (0xFB8)>
    ********** RCSvcs - Unloading Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:55:00.536 2012><thread=4024 (0xFB8)>
    ======= Logging initialized for module "C:\WINDOWS\System32\MsiExec.exe" =======  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:57:36.087 2012><thread=3824 (0xEF0)>
    ********** Loading RCSvcs - Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:57:36.102 2012><thread=3824 (0xEF0)>
    _RCSVCS(MSI): Entering SecureRegKeys  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:57:36.102 2012><thread=3824 (0xEF0)>
    _RCSVCS(MSI): Leaving SecureRegKeys  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:57:36.196 2012><thread=3824 (0xEF0)>
    ********** RCSvcs - Unloading Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\MsiExec.exe><Fri May 04 22:57:36.212 2012><thread=3824 (0xEF0)>
    ======= Logging initialized for module "C:\WINDOWS\System32\CCM\CcmExec.exe" =======  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:37.758 2012><thread=1544 (0x608)>
    ********** Loading RCSvcs - Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:37.758 2012><thread=1544 (0x608)>
    _RCSVCS(CCM): Entering InstallW2KDrivers  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:37.774 2012><thread=1544 (0x608)>
    ======= Logging initialized for module "C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe" =======  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:39.009 2012><thread=2332 (0x91C)>
    ********** RCSvcs - Starting Remote Control Service Manager **********  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:39.024 2012><thread=2332 (0x91C)>
    RCSvcs: Install Win2k devices, return success/failure status  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:39.024 2012><thread=2332 (0x91C)>
    InstallNT5Devices: Starting installation of Win2K device drivers  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:39.040 2012><thread=2332 (0x91C)>
    FindDevice(*SMS_MOUSE): found SMS Virtual Mouse  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.305 2012><thread=2332 (0x91C)>
    InstallNT5Device(*SMS_MOUSE): driver is up-to-date  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.305 2012><thread=2332 (0x91C)>
    InstallNT5Device(*SMS_MOUSE) succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.305 2012><thread=2332 (0x91C)>
    FindDevice(*SMS_KEYBOARD): found SMS Virtual Keyboard  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.384 2012><thread=2332 (0x91C)>
    InstallNT5Device(*SMS_KEYBOARD): driver is up-to-date  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.399 2012><thread=2332 (0x91C)>
    InstallNT5Device(*SMS_KEYBOARD) succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.399 2012><thread=2332 (0x91C)>
    FindDevice(*SMS_DISPLAY): found Microsoft SMS Mirror Driver  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.524 2012><thread=2332 (0x91C)>
    InstallNT5Device(*SMS_DISPLAY): driver is up-to-date  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.524 2012><thread=2332 (0x91C)>
    InstallNT5Device(*SMS_DISPLAY) succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.524 2012><thread=2332 (0x91C)>
    Checking if idisw2km service is enabled  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.540 2012><thread=2332 (0x91C)>
    InstallNT5Devices: succeeded  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.555 2012><thread=2332 (0x91C)>
    ********** RCSvcs - Ending Remote Control Service Manager **********  $$<C:\WINDOWS\System32\CCM\CLICOMP\RemCtrl\rcsvcs.exe><Fri May 04 22:57:40.555 2012><thread=2332 (0x91C)>
    SpawnProcess: exit with code 0  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.680 2012><thread=1544 (0x608)>
    _RCSVCS(CCM): Leaving InstallW2KDrivers  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.696 2012><thread=1544 (0x608)>
    _RCSVCS(CCM): Entering InstallStartWUSER32  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.696 2012><thread=1544 (0x608)>
    RCSvcs - Creating WUSER32 service.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.696 2012><thread=1544 (0x608)>
    RCSvcs - WUSER32 service created, return code 0.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.727 2012><thread=1544 (0x608)>
    RCSvcs - Starting WUSER32 service.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.727 2012><thread=1544 (0x608)>
    RCSvcs - WUSER32 service started, return code 0.  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.884 2012><thread=1544 (0x608)>
    _RCSVCS(CCM): Leaving InstallStartWUSER32  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.884 2012><thread=1544 (0x608)>
    ********** RCSvcs - Unloading Remote Control Service Manager Library **********  $$<C:\WINDOWS\System32\CCM\CcmExec.exe><Fri May 04 22:57:40.899 2012><thread=1544 (0x608)>

    Monday, May 7, 2012 1:52 PM
  • Hello.  We are still stuck in the same place.  The video driver on the client has now been updated, but we get the same results. 

    As I noted before, SMS remote control works only if someone is logged into the client using rdp.  But if no one is logged in, the sms remote control only produces a blank screen!  Any suggestions? 

    Wednesday, May 9, 2012 2:08 PM
  • I'm pretty sure it's time to go to ConfigMgr 2012 :)

    Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

    • Proposed as answer by Garth JonesMVP Monday, December 22, 2014 3:33 AM
    • Marked as answer by Garth JonesMVP Saturday, January 3, 2015 5:27 PM
    Wednesday, May 16, 2012 9:46 AM