Windows 11 RDP - Need help

[deltaexray]

Hello everyone,

Following countless installs and custom ISOs with NTLite, I have recently come to the point where I need, and also want, to use RDP. So, with the knowledge I‘ve gained over the years, I started to customise a 25H2 ISO with RDP enabled and so on so forth.
So far so good, everything worked out the way it was suppose until I wanted to try that ISO as a VM, specifically the RDP function - that did not work. Not at all. So I went back and installed a „vanilla“, not touched Win11 ISO and guess what - RDP worked just fine. So I started my day long journey of researching, fixing, trying and so on. By now, I‘ve sort of hit a dead end. Not really clueless but rather a „There a to many trees to see the woods“.
So, I‘ve a got two questions for anyone reading this:
A) Any advice, tips, solutions on your own, etc. ?
B) Would anyone like to take a few minutes to check the attached xml file of a preset of mine, which is the last one I did or saved as, so to speak.

Anyway, thank you for your time and Thanks in Advance for the help
Cheers, Alex.

 

[garlin]

When you change the RDP listening port, the default firewall rules to allow RDP don't recognize the port change.
Configure the Remote Desktop listening port

Add this command to Post-Setup (Before logon):

Command	Parameters
powershell	"New-NetFirewallRule -DisplayName 'RDPPORTLatest-TCP-In' -Profile Public -Direction Inbound -Action Allow -Protocol TCP -LocalPort 7291; New-NetFirewallRule -DisplayName 'RDPPORTLatest-UDP-In' -Profile Public -Direction Inbound -Action Allow -Protocol UDP -LocalPort 7291"

 

[deltaexray]

When you change the RDP listening port, the default firewall rules to allow RDP don't recognize the port change.
Configure the Remote Desktop listening port

Add this command to Post-Setup (Before logon):

Command	Parameters
powershell	"New-NetFirewallRule -DisplayName 'RDPPORTLatest-TCP-In' -Profile Public -Direction Inbound -Action Allow -Protocol TCP -LocalPort 7291; New-NetFirewallRule -DisplayName 'RDPPORTLatest-UDP-In' -Profile Public -Direction Inbound -Action Allow -Protocol UDP -LocalPort 7291"

First of all: Thank your for your reply ans time, that is certainly not a given!
Regarding your reply: I will test this out tomorrow morning, it sounds plausible to me for sure but does it also apply when the defender & firewall is removed completely? I‘d guess so but also it would suggest that certain features within windows cant be removed completely

 

[garlin]

Defender is a separate component from Windows Firewall, which you have not removed in the preset.

 

[deltaexray]

Defender is a separate component from Windows Firewall, which you have not removed in the preset.

So I guess Firewall is none removable without going into too many details and registry edits?

Okay, I will have a look at it now - Huge thank you !

 

[garlin]

Windows Firewall has its own components for removal. You will have to click the Compatibility button, and uncheck the Recommended box.

For installation and Windows Update, you need to keep Windows Firewall Service.

 

[deltaexray]

Windows Firewall has its own components for removal. You will have to click the Compatibility button, and uncheck the Recommended box.

For installation and Windows Update, you need to keep Windows Firewall Service.

View attachment 15203

Hello again, Update:

I've tried what u have suggested multiple times now and I'm starting to think I'm doing something wrong. I you'd be so kind to take a look at the save settings, I chose, to maybe find the issue?
Firewall has not been removed.

Thank you very much

 

[EvilDrewM24]

When you change the RDP listening port, the default firewall rules to allow RDP don't recognize the port change.
Configure the Remote Desktop listening port

Add this command to Post-Setup (Before logon):

Command	Parameters
powershell	"New-NetFirewallRule -DisplayName 'RDPPORTLatest-TCP-In' -Profile Public -Direction Inbound -Action Allow -Protocol TCP -LocalPort 7291; New-NetFirewallRule -DisplayName 'RDPPORTLatest-UDP-In' -Profile Public -Direction Inbound -Action Allow -Protocol UDP -LocalPort 7291"

Hey Garlin - this may be a stupid question but when I am setting up a Powershell command, how do I specify it is powershell? Do I just type powershell in the box next to the command prompt icon and then put my command string into the parameters? Does my command need to be in quotes?

This is what I have going on currently. The pscall.bat calls a .ps1 file from my network. Am I doing it correctly? Would calling a .ps1 look the same only "Powershell.exe" would be under task and the UNC path to my file under parameters? Do the parameters need to be in quotes?