03_Server_2019_PDQ_Deploy
This post comes way after the fact, but here is what happened. I was able to join my Windows 11 computer to the mylab.local domain and then I was able to find it in Active Directory. Next, I created a user in AD and then I was able to login as that user on the domain. So far so good. Now comes the hard part. After installing PDQ Deploy onto my Windows Server 2019 I tried deploying Filezilla, a simple and small program that should install without a hitch. Guess what? There was a hitch!
So what was the problem? Well, I had to consult Gemini and it turns out the firewall was the problem. To test this I disabled the firewall on the Windows 11 machine and then deployed Filezilla successfully and then I uninstalled it successfully.
But hey, we don't want to leave our Windows 11 defenses down! Lord knows that any Windows machine has an attack surface the size of Texas! Our solution, let's brainstorm with Google Gemini! Google Gemini helped walk me through pushing Group Policy I called GP_PDQ_Firewall_Rules which opened up ports 445 (SMB) and port 135 (RPC). After I pushed this policy I restarted the Windows 11 machine and then after it took affect I ran PDQ Deploy again and install Filezilla onto the Windows 11 machine. This time it was successful. After I installed Filezilla, I also uninstalled it and checked the Windows 11 machine. I would say that doing this a few times would help a person like me to understand how to use PDQ Deploy and configuring GPO to do different things helps to learn the GPO process, even though in my opinion, the GPO interface and process seems the least user friendly feature so far on Windows Server 2019 (YIKES!).
