Microsoft Windows on Jetstream

We presently do not support Windows on Jetstream. It can be used via the API side but we are unable to provide any sort of support for it at all.

If you wish to explore installing Windows on Jetstream, first get a Startup Allocation if you do not have one.

Once you have the allocation you'll need to get API access. Follow these instructions to get API access.

Once you have API access, you'll want to install the command line clients for later. Instructions for that are available for Windows and for Linux and OSX,

Then you can follow instructions like these to get Windows onto Jetstream via the OpenStack API:

One key difference is you'll need to make sure the image is in RAW format to upload. There are instructions on uploading images, especially making sure you specify the right options, here under "Uploading a snapshot or new image into Glance"


There is a Windows Server 2016 and a Windows Server 2019 image available on Jetstream. While these were created by one of the Jetstream parters in conjunction with Jetstream staff, it is NOT supported nor guaranteed to work. It is unlikely that the Jetstream staff will be able to do more than general VM troubleshooting as we do not have Windows expertise on staff. It has no license installed so you will need to bring your own license. This will likely never, ever work on the Atmosphere side - just FYI. 

The image names and UUIDs for available Windows versions are: 

Image NameImage UUIDImage sizeMinimum VM size required

Active / 






54gbm1.mediumIN DEVELOPMENT


No longer available





No longer available





No longer available


We recommend that you run Windows Update immediately for ANY of these images. They are patched up to the time they were imaged but may need immediate patching for any security issues that have cropped up since.

It is recommended that you have security rules allowing:

  • Inbound icmp from anywhere
  • Inbound ssh (tcp port 22) from either anywhere or from wherever you will likely be accessing your instance from
  • Inbound rdp (tcp port 3389) from wherever you will likely be accessing your instance from – best security practice would definitely say to limit this as much as possible. You might consider multiple rules with single or small IP ranges to cover secure networks you'll be working from

You will need to retrieve the Admin password after boot. This can be done from Horizon IF and ONLY IF your ssh key isn't password protected...which is not a recommended practice. For that reason, we will recommend that you also install the python-novaclient package in addition to the python-openstackclient so you can retrieve the Admin password by doing:

nova get-password INSTANCE_UUID path_to_ssh_private_key

You'll get back a long, random string that you can use to RDP to your instance. The username will be Admin for Win 2012 Server. It will be Administrator for Win 2016 and 2019 Server.

It will be a different password for every instance. You should be able to change it as you see fit, though you can always retrieve the password again with that nova command. You may get a certificate error trying to RDP in – that's not unexpected and can generally just be cleared. 

In general, depending on the application you are wanting to use, you might see if there is a Linux version available. It would definitely be easier to install a Linux-based software package rather than install and support your own Windows installation on Jetstream.