![]() Get-ChildItem RDS:\GatewayServer -Recurse | Format-List > $HOME\Desktop\RDG.txt But I think it’s less successful for RDG.īut the main issue is that there doesn’t appear to be any documentation of what all the options are. That works well for resources like the registry ( HKLM:) and certificates ( Cert:). PowerShell providers (see about_Providers) make everything look like a filesystem. (If you find better doc, please leave a comment.) You’d expect that by now, given the importance of Windows jump servers to Azure and AWS IaaS deployments, Microsoft would have shipped PowerShell cmdlets to make configuration a snap.īut all I could find was a single blog post (from 2011!) describing in very general terms a PowerShell provider for Remote Desktop Services. Recently, I decided to see if there was a way to use PowerShell to configure a basic RDG server. ![]() This major disadvantage meant that you could use DevOps tools like Chef or Azure DSC to install the Remote Desktop role on the server - but you had to log into the machine to configure RDG itself. I do this all the time as a test - of the configuration as well as my own mind as it’s a bit of a mental twister.īut there’s always been a fly in the ointment of this otherwise standard process: configuring the RDG server itself had to be done via the UI. Simply specify the internal address or DNS of the RDG host as the RDP connection destination. ![]() Note that it’s possible for the RDG host to connect to itself. ![]() Remote Desktop Gateway connections (click to enlarge) Three years ago this month, I described how you can use the Remote Desktop Gateway (RDG) as a Windows bastion, or jump, server to provide secure access to Windows hosts inside a private subnet in either AWS and/or Azure. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |