can't remote desktop into windows machines created by juju

[Nate Finch]

I have tested this on Azure, not sure if it's true for maas with Windows images.

If I create a Windows machine in Azure manually, I can RDP into it. If I try to RDP into a Windows machine Juju has created in Azure, I can't. This is a critical problem, since there's no other way to get into the machine - there's no SSH, for example.

This really needs to get fixed ASAP, or it renders Windows all but unusable if you ever need to connect to it to debug.

[Andrew Wilkins (axwalk)]

It does work on Azure, I've done it before. There's a couple of things you need to do:
 - enable port 3389
 - set a password (the one that's set initially is random, and not recorded anywhere; you can use `juju run --machine N "net user JujuAdministrator <password>"`)

[Nate Finch (natefinch)]

That only works if juju is working. If juju is broken, you're hosed, because you can't connect to debug why juju is broken (well, not exactly, you can edit the security group to open up 3389, but that's hard to figure out if you don't already know how to do it).

[Anastasia (anastasia-macmood)]

Removing 2.1 milestone as we will not be addressing this issue in 2.1.