Hey everyone! I've been using RealVNC for remote access to devices for our hybrid employees, as I've always preferred keeping RDP disabled for security reasons. Lately, I've been looking into AdminByRequest for remote access since I use it for endpoint protection management (EPM), but I have to set up SSO via SAML, which is a bit of a hassle. However, when I tried to remote into a test PC, I got a message saying "Remote Control Problem. RDP is disabled on the endpoint." I'm curious about why AdminByRequest works this way and if it poses any security risks, considering I've always been taught to keep RDP closed to external connections as part of network security best practices.
3 Answers
Have you checked if the PCs are joined to a domain? Sometimes policies differ based on whether devices are domain-joined vs. others like Azure AD joined. If they're Intune-managed but not domain-joined, it might have different access privileges or configuration requirements.
I get your concern! When it comes to RDP, 'external connections' typically refer to those open to the internet on port 3389, which is definitely a security risk. But having RDP enabled on a local area network (LAN) for internal connections is more common and generally considered safe, especially if you trust those on your network. If you're worried about security, using something like AdminByRequest with RDP could be safer than using RealVNC, as it typically has built-in protections, but it really depends on how it's configured.
That's interesting you don't want to enable RDP internally. Many folks like using RDP because it usually offers a better experience compared to VNC. What did support say when you reached out for help? That might shed light on the message you’re getting.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures