<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on Aaron Warwick</title><link>https://aaronwarwick.com/tags/windows/</link><description>Recent content in Windows on Aaron Warwick</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aaronwarwick.com/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>RDP on an Entra-Joined Machine: The Two Problems Nobody Warns You About</title><link>https://aaronwarwick.com/posts/rdp-on-azure-joined-pcs/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://aaronwarwick.com/posts/rdp-on-azure-joined-pcs/</guid><description>&lt;p&gt;I have been remoting into Windows machines for over a decade. Domain-joined, workgroup, across VPNs, across the internet. RDP is one of those things that just works once you flip the toggle and open port 3389. Until it does not.&lt;/p&gt;
&lt;p&gt;This week I spent hours chasing an RDP failure on an Entra-joined machine. The machine was on the same subnet, on the same switch, plugged into the same network as the source machine. Everything about it should have been a two-minute connection. Instead, I ended up knee-deep in packet captures, NIC driver investigations, certificate stores, and registry edits before I found the actual problem.&lt;/p&gt;</description></item></channel></rss>