Windows 10: I have this error in SCCM------ Unable to connect to remote machine "LAPTO-01" using...

I've been trying to solve this error for days, but without success. I configured my firewall

:)

 

SCCM remote session locking remote device

Hello,

We have SCCM (below details) installed on a Jump servers and we use it to connect to clients deployed in our environment.
In order to connect to the devices, we connect to the Jump server first using PAM and then to the devices.

Environment - SCCM2010 v5.2010.1093.3100 & Client 5.00.9040.1044
Deployed to Win 10-64bit Enterprise.
Locally installed SCCM Remote Control software v5.00.9040.1044

My problem is if I am connected to a device and DO NOT disconnect from the session, but simply disconnect from the jump server instead, the device I am connected to gets locked out.

I do not want it to lock out, instead I just need the SCCM session to just disconnect but not lock the remote machine out.

How can that be done ?

Thanks in advance.

 

Remote Desktop Connection problem with Virtual Machine

We made the big mistake of configuring a WINDOWS-10 VM to allow for Remote Desktop Connections. We are unable to disassociate the VM from RDM. We can no longer access the VM!!! The following is the pertinenet
information:

• Server is running Windows-10 Professional 64 with Hyper-V installed.
• VM is Windows-10 Professional 64.
• In VM allowed Remote Desktop Connections.
• From server successfully connected to VM via RDM.
• Closed RDM connection. Unable to access VM.
• Turned off VM from Hyper-V Manager.
• Attempted to restart VM, unable to connect via Hyper-V from message box the following is displayed:
  
  Video Remoting was disconnected. The virtual maching is currently using the Remote X 3D video adapter. A user is currently connected via Remote Desktop Connect to the virtual machine by using Remote Desktop Connection.
• Connected via Remote Desktop Connection. Attempted to turn off allowing Remote Desktop Connection. VM hung.
• VM Wouldn't turn off via Hyper-V manager.
• Shutdown host system and rebooted.
• Unable to connect via console or RDM.
• Shutdown host system and rebooted.
• Deleted VM via Hyper-V Manager.
• Restored VM system disk from backup prior to RDM usage.
• Created new VM. the messages in itm 7 above are displayed.

What can be done to recover? Why does Hyper-V retain a broken connection?

 

unable to connect remotely to desktop at work from personal machine

A user is unable to connect remotely to her desktop at work from a personal machine (both Windows 10)

error your computer cannot connect to the remote desktop gateway server

RD Gateway Server credentials popup appears, with logon attempt failed.

The user account was locking out on the local machine.

I connected to the users machine at work:

Flushed the dns resolver cache

Cleared Temporary Files.

Deleted Cookies / Temp Files / History / Saved passwords / Forms from all the browsers.

Deleted all Prefetch files.

Deleted unwanted tasks.

Removed stored passwords from Control Panel.

Removed unwanted applications from Start-up (skype)

The Account no longer locks out but rdp still requests RDGW server credentials.

I re-created the RDP session for the user but the issue still ongoing when attempting to remote, error your computer can't connect to the remote computer because the remote desktop gateway server is temporarily unavailable.

The user has to try multiple times before the connection is established. I remotely logged on to the users machine at work from my home office but did not have the same issue, rdp connected fine every time. Of course remote connections are allowed on the remote
machine else I would not be able to connect. Not sure of the relevance but the user is running AVG AV. Our server team have identified an issue whereby users can connect to their machine remotely only after 3 or 4 connection attempts. This user seems to have
a bigger problem connecting. Any help would be appreciated.