SCCM 2111 problem with Remote Control on x86 windows device

Question

question

alexostroushko-1581 asked Jan 5, '22 miaminemo commented Jan 25, '22

SCCM 2111 problem with Remote Control on x86 windows device

Helo, maybe someone faced with a problem. After upgrade sccm to version 2111 and upgrade sccm agent to version 5.00.9068.1008. Stop working remote control on x86 devices. After trying to connect, have status "Connection to the host session" and black screen and message do not apear to approve the connect/

On the client machine if looking on the log CmRcService.log:

======> A connection has been established. (OnConnectionEstablished) CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Incoming connection IP address: XXX.XXX.XXX.XXX Port: 54275 IsLocationConnection: false CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Ready to start the security handshake. CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
=== Starting security handshake === CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
=== Security handshake completed [0x10000000] === CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
The user(domain\username) is authorized for Remote Control CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Session allowed: Full Control CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
=== Session Info === CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Authorized viewer user: domain\username CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Viewer address: XXX.XXX.XXX.XXX:54275 CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Host address: XXX.XXX.XXX.XXX:2701 CmRcService 05.01.2022 13:54:14 6652 (0x19FC)
Connection completed (ID = 1) (OnConnectionCompleted) CmRcService 05.01.2022 13:54:15 6096 (0x17D0)
Create a process application Name=C:\WINDOWS\CCM\SCToastNotification.exe, with lpCommandLine=SCToastNotification.exe /MOSH_ONLY "Configuration Manager Remote Control" "Administrator is requesting to remote control your computer. Click to check request." CmRcService 05.01.2022 13:54:17 7272 (0x1C68)
Local user allowed the remote control session. CmRcService 05.01.2022 13:54:19 10084 (0x2764)
The remote control session is allowed. (OnSessionAllowed) CmRcService 05.01.2022 13:54:19 8368 (0x20B0)
=== A remote control session is in progress (OnViewerConnected) === CmRcService 05.01.2022 13:54:19 8368 (0x20B0)

mem-cm-co-management

· 4

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

alexostroushko-1581 · Jan 05 at 09:38 PM

execuse me, wrong log copy. Here what set the x86device

======> A connection has been established. (OnConnectionEstablished) CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Incoming connection IP address: XXX.XXX.XXX.XXX Port: 59689 IsLocationConnection: false CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Ready to start the security handshake. CmRcService 05.01.2022 23:28:15 5236 (0x1474)
=== Starting security handshake === CmRcService 05.01.2022 23:28:15 5236 (0x1474)
=== Security handshake completed [0x10000000] === CmRcService 05.01.2022 23:28:15 5236 (0x1474)
The user(domain\username) is authorized for Remote Control CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Session allowed: Full Control CmRcService 05.01.2022 23:28:15 5236 (0x1474)
=== Session Info === CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Authorized viewer user: domain\username) CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Viewer address: 172.23.1.11:59689 CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Host address: 172.21.27.153:2701 CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Connection completed (ID = 1) (OnConnectionCompleted) CmRcService 05.01.2022 23:28:16 4760 (0x1298)

and found if i made a politics where i can connect with out approve, i can connect to device. So the problem that do not create a process C:\WINDOWS\CCM\SCToastNotification.exe,

0 ·

alexostroushko-1581 · Jan 05 at 09:38 PM

execuse me, wrong log copy. Here what set the x86device

======> A connection has been established. (OnConnectionEstablished) CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Incoming connection IP address: XXX.XXX.XXX.XXX Port: 59689 IsLocationConnection: false CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Ready to start the security handshake. CmRcService 05.01.2022 23:28:15 5236 (0x1474)
=== Starting security handshake === CmRcService 05.01.2022 23:28:15 5236 (0x1474)
=== Security handshake completed [0x10000000] === CmRcService 05.01.2022 23:28:15 5236 (0x1474)
The user(domain\username) is authorized for Remote Control CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Session allowed: Full Control CmRcService 05.01.2022 23:28:15 5236 (0x1474)
=== Session Info === CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Authorized viewer user: domain\username) CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Viewer address: XXX.XXX.XXX.XXX:59689 CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Host address: XXX.XXX.XXX.XXX:2701 CmRcService 05.01.2022 23:28:15 5236 (0x1474)
Connection completed (ID = 1) (OnConnectionCompleted) CmRcService 05.01.2022 23:28:16 4760 (0x1298)

and found if i made a politics where i can connect with out approve, i can connect to device. So the problem that do not create a process C:\WINDOWS\CCM\SCToastNotification.exe,

0 ·

BlekickiMaciej-8767 · Jan 13 at 10:59 AM

Hi,
According to the information obtained from Microsoft, we have to wait for the release of the next patch to fix this problem. Unfortunately, there is no information about when it will be released yet.

0 ·

miaminemo · Jan 25 at 08:35 PM

Did you also experience this on x64 clients, or only on x86 clients?

Did you try on x64 clients?

0 ·

Answer 1 · 2022-01-18T06:29:18.7Z

BlekickiMaciej-8767 answered Jan 18, '22

Hi,
Update KB12959506 has been released which fixes this problem definitively. After installing it, the client version changed to 5.00.9068.1012 and Remote Control works fine.
https://docs.microsoft.com/pl-pl/mem/configmgr/hotfix/2111/12959506

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2022-01-10T09:18:19.367Z

Evgeny-1721 answered Jan 10, '22 alexostroushko-1581 commented Jan 11, '22

Hello! I have the same thing.
1 Updated in the console from SCCM 2103 to SCCM 2111. Clients on all PCs were forcibly installed on the new version 5.00.9068.1008 and after that, it was on all PCs with Windows 7 x32 that remote control stopped connecting. When connecting, the Connection to the node session hangs waiting and does not reach the Request for remote management permission from the remote user. Windows 7 x32 clients with older agent versions 5.00.8913.1012 and 5.00.9049.10.10 connect without problems.
Didn't find the reason for the connection?

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

alexostroushko-1581 · Jan 11 at 01:30 PM

For now i make a workaround. Install old agent on x32 device and disable auto upgrade on workstation. But for now this is just a workaround but not a solution.

Just for information found a topic about this problem. https://forums.prajwaldesai.com/threads/sccm-2111-some-clients-black-screen-when-connecting-with-remote-viewer.4766/page-2#posts

0 ·

Answer 3 · 2022-01-11T13:49:58.723Z

Evgeny-1721 answered Jan 11, '22 alexostroushko-1581 commented Jan 11, '22

I'm having trouble installing the old version of the agent.
1 Disabled the Hierarchy Parameters in the console - Exclude the specified clients from the update and selected a collection with Windows 7 x32.
2 Deleted the new agent on the Windows 7 x32 client and then install the agent version from scm 2103 ccmsetup.exe 5.00.9049.1003, but he still installs a new version of agent 5.00.9068.1008 for me
Can you tell me how to install the old version of the agent correctly?

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

alexostroushko-1581 · Jan 11 at 02:12 PM

on Windows 7 i use a script on powershell. (actual i make GPO wich make a sheduler to start powershell because winrm disable on WInodws 7 in my company

start-process -filepath "C:\Windows\ccmsetup\ccmsetup.exe" -ArgumentList "/uninstall" -Wait
Start-Sleep -Seconds 5
Get-Item C:\windows\ccmsetup | Remove-Item -Recurse -force -Confirm:$false
Start-Sleep -Seconds 10
Get-Item C:\windows\CCM | Remove-Item -force -Recurse -Confirm:$false
Start-Sleep -Seconds 15
start-process -filepath "\\file_shre_with_old_client\ccmsetup.exe" -ArgumentList "SMSSITECODE=XXX", "/AlwaysExcludeUpgrade:TRUE" -wait

SMSSITECODE=XXX where XXX your sccm site code

0 ·

Answer 4 · 2022-01-13T16:25:17.937Z

alexostroushko-1581 answered Jan 13, '22 BlekickiMaciej-8767 commented Jan 14, '22

Also remote control start work when i change C:\Windows\CCM\RemCtrl\SCCMRDPUser.exe from older agent without reinstall agent

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Evgeny-1721 · Jan 14 at 05:07 AM

Replaced the file C:\Windows\CCM\RemCtrl\SCCMRDPUser.exe and everything worked. Thanks!

0 ·

BlekickiMaciej-8767 · Jan 14 at 11:18 AM

I also have the replacement of the C:\Windows\CCM\RemCtrl\SCCMRDPUser.exe file working properly. It was a bit hard for me to find an old working agent at my place, but luckily I made it. Thank you very much for the valuable hint.

0 ·

question