A
Andrew-555556
Hello
we have a very strange issue.
we needed to reinstall RDS locally on a windows 2016 server.
RDS created the following 2 system rules
port 445 (SMB) - open to all
port 3389 (RDP) - open to all
these rules are over riding our GPO rules (where these ports are restricted) - and no user has permissions to delete them (even domain admins)
this is obviously causing us some issues here. We are using RDS per user license to allow for X number of users to connect to RDP on this server
We have tried to remove these rules via GPO, locally on the server as domain admin, via powershell, etc. We simply cannot remove these rules
Has anyone seen this before? any ideas how/why RDS would even do this?
history - previously - this server was joined to azure AD and connected to the azure RDS platform. we decided this setup was not working for us and RDS app sessions were not reliable enough, and instead switched the server to our local domain and installed RDS licensing to use with RDP directly on the server. Everything is working perfectly fine, except that RDP and SMB are open to the world (I’m nor sure previously being attached to azure ad or rds on azure matters, just figure I’d mention it)
thanks in advance
Andrew
Continue reading...
we have a very strange issue.
we needed to reinstall RDS locally on a windows 2016 server.
RDS created the following 2 system rules
port 445 (SMB) - open to all
port 3389 (RDP) - open to all
these rules are over riding our GPO rules (where these ports are restricted) - and no user has permissions to delete them (even domain admins)
this is obviously causing us some issues here. We are using RDS per user license to allow for X number of users to connect to RDP on this server
We have tried to remove these rules via GPO, locally on the server as domain admin, via powershell, etc. We simply cannot remove these rules
Has anyone seen this before? any ideas how/why RDS would even do this?
history - previously - this server was joined to azure AD and connected to the azure RDS platform. we decided this setup was not working for us and RDS app sessions were not reliable enough, and instead switched the server to our local domain and installed RDS licensing to use with RDP directly on the server. Everything is working perfectly fine, except that RDP and SMB are open to the world (I’m nor sure previously being attached to azure ad or rds on azure matters, just figure I’d mention it)
thanks in advance
Andrew
Continue reading...