[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1516
  • Last Modified:

SCCM Remote Tools: Now it works... now it doesn't

After a major update of our clients (XP SP3) (and a few on our servers), so they are fully patched, I expirience the following:

I can only use SCCM Remote Tools to access the client every second time i try. It goes like this...
1. The user logs on to the client. I can access the client with Remote Tools.
2. The user reboots the client. Now I can't access the client with Remote Tools.
3. The user reboots again. Now I can access the client again with Remote Tools.
4. The user reboots the client. Now I can't access the client with Remote Tools.
Get the picture?

It is only when I try to access the client with Remote Tools it counts. If the user reboots an extra time between  2. and 3., I will still be able to connect.
It is only every second time I use Remote Tools it doesn't work.

I have installed the KB975467 update on the client as explained in this article:
http://social.technet.microsoft.com/Forums/en/configmgradminconsole/thread/a10c7d4d-7ae4-444b-b01d-66a645d6f798

And I have looked into this one as well, but couldn't see any problems with the Remote Tools component:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Q_24338557.html

Any good ideas on how to solve this one?
0
Kasper Katzmann
Asked:
Kasper Katzmann
  • 4
  • 4
1 Solution
 
NJComputerNetworksCommented:
what error do you get?  

1) Check the remotecontrol.log on the client around the time the attempt is made to remote tool the client.
2) when this fails, can you ping the client (maybe there is a network resolution problem)?
0
 
Kasper KatzmannAuthor Commented:
I'll try that tomorrow (it's evening here in Copenhagen).

Can you tell me where I can find remotecontrol.log?
0
 
NJComputerNetworksCommented:
c:\windows\system32\ccm\logs
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Kasper KatzmannAuthor Commented:
This is what it says when it doesn't work:


<![LOG[Remote Control Server started.]LOG]!><time="09:35:15.726+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3276" file="servermain.cpp:347">
<![LOG[Remote Control Launcher started.]LOG]!><time="09:35:15.851+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="1832" file="launchermain.cpp:349">
<![LOG[Monitor thread started]LOG]!><time="09:35:15.882+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3444" file="properties.cpp:278">
<![LOG[Creating RDP session]LOG]!><time="09:35:15.882+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:399">
<![LOG[Remote Control Agent started.]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agentmain.cpp:454">
<![LOG[RCAgent successfully started.]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="1832" file="launcher.cpp:224">
<![LOG[Successfully created ticket for EVADK\kk]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:535">
<![LOG[Created invitation for EVADK\kk]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:240">
<![LOG[Launcher is no longer in use. Shutting down.]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="1832" file="launchermain.cpp:234">
<![LOG[Remote Control Launcher terminated normally.]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="1832" file="launchermain.cpp:372">
<![LOG[Server is no longer in use. Shutting down.]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3276" file="servermain.cpp:234">
<![LOG[Remote Control Server terminated normally.]LOG]!><time="09:35:15.991+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3276" file="servermain.cpp:370">
<![LOG[Received OnAttendeeConnected event]LOG]!><time="09:35:16.257+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:774">
<![LOG[Permission granted for viewer 0]LOG]!><time="09:35:16.257+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:668">
<![LOG[Changing color depth to 16 bpp]LOG]!><time="09:35:16.335+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:1075">
<![LOG[Received OnControlLevelChangeRequest event]LOG]!><time="09:35:16.335+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:914">
<![LOG[Set view mode to 3]LOG]!><time="09:35:16.335+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:934">
<![LOG[Fatal RDP error occurred (0x80070709).  Agent will terminate.]LOG]!><time="09:35:19.054+-60" date="12-23-2009" component="RemoteControl" context="" type="3" thread="3428" file="agent.cpp:1012">
<![LOG[Server is no longer in use. Shutting down.]LOG]!><time="09:35:19.069+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agentmain.cpp:319">
<![LOG[Closing RDP session]LOG]!><time="09:35:19.069+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agent.cpp:629">
<![LOG[Remote Control Agent terminated normally.]LOG]!><time="09:35:19.069+-60" date="12-23-2009" component="RemoteControl" context="" type="1" thread="3428" file="agentmain.cpp:485">

Open in new window

0
 
Kasper KatzmannAuthor Commented:
And I CAN ping the client while it is inaccessible through Remote Tools...
0
 
NJComputerNetworksCommented:
Hey, thanks for providing the log.  And it is good to know that this is not a network problem (seeing how you can ping be name).

I think this issue might be related to the Display drivers on the client machine.  Can you update the display driver on the client machine to the latest driver?

Here is a similar situation posted by another person:  http://www.myitforum.com/forums/Remote_Client_-_White_Screen/m_203041/tm.htm


0
 
Kasper KatzmannAuthor Commented:
YES YES YES!
I buy you a BIG beer if you should drop by.

Updated the displaydriver to the newest ATI Radeon 2400 PRO driver (released december 17th 2009) and know it works just as it should.

You are my hero.
0
 
NJComputerNetworksCommented:
coolio... thank you!
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now