There are things you can do to get around this, though I'm not sure they're compliant with the Windows EULA. Note one restriction: if the EC2 instance you're running isn't a Server edition of Windows, you'll be restricted to one RDP session at a time. Now launching that RDP session should give you e.g. edit the new RDP connection to supply the correct server address (from the client's perspective) and prepopulated authentication credentials. rdp file into Microsoft Remote Desktop ħ. rdp file for that session, and get it back to your computer Ħ. use the tool to generate an RDP connection profile on the instance-naming the session and browsing for an EXE path is usually enough ĥ. install this thing on the instance: (since Windows doesn't come with any sort of GUI for this†) Ĥ.
enable receiving Remote Desktop Connections on the instance's System prefs (might already be enabled if that's how they expect people to connect to manage their instances) ģ. on the instance, select a base image of any edition of Windows 7/8/10 that supports receiving Remote Desktop Connections Ģ. I guess plain EC2 Windows instances will still work, though. (This is apparently on purpose WorkSpaces advertises "keeping your data on-premise by never exporting it to the client the client only gets pixels.") Checking further, it looks like AWS WorkSpaces doesn't actually support any protocol other than "Teradici PC-over-IP"-I'm guessing that whether or not you enable RDP on the remote, the AWS firewall policy won't expose the port.
0 kommentar(er)
