How to create Windows VM on OpenStack Horizon and access it via web console on 3Engines Cloud[🔗](#how-to-create-windows-vm-on-openstack-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline")
===========================================================================================================================================================================================================================

This article provides a straightforward way of creating a functional Windows VM on 3Engines Cloud cloud, using the Horizon graphical interface.

The idea is to

> * start the creation of a Windows virtual machine from the default Horizon dashboard and then
> * access it via the web console,

all from your Internet browser.

What Are We Going To Cover[🔗](#what-are-we-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------

> * Accessing the Launch Instance menu
> * Choosing the Instance name
> * Choosing source
> * Choosing flavor
> * Choosing networks
> * Choosing security groups
> * Launching virtual machine
> * Setting **Administrator** password

Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------

No. 1 **Account**

You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://horizon.3Engines.com>.

Step 1: Access the Launch Instance menu[🔗](#step-1-access-the-launch-instance-menu "Permalink to this headline")
----------------------------------------------------------------------------------------------------------------

In the Horizon dashboard, navigate to **Compute -> Instances**. Click the **Launch Instance** at the top of the **Instances** section:

![create-windows-vm-horizon-web-console-01_creodias.png](../_images/create-windows-vm-horizon-web-console-01_creodias.png)

You should get the following window:

![create-windows-vm-horizon-web-console-02_creodias.png](../_images/create-windows-vm-horizon-web-console-02_creodias.png)

Step 2: Choose the instance name[🔗](#step-2-choose-the-instance-name "Permalink to this headline")
--------------------------------------------------------------------------------------------------

In the window which appeared, enter the name you wish to give to your instance in the **Instance Name** text field. In this example, we use **test-windows-vm** as the name:

![create-windows-vm-horizon-web-console-03_creodias.png](../_images/create-windows-vm-horizon-web-console-03_creodias.png)

Click **Next >**.

Step 3: Choose source[🔗](#step-3-choose-source "Permalink to this headline")
----------------------------------------------------------------------------

The default value in the drop-down menu **Select Boot Source** is **Image**, meaning that you will choose from one of the images that are present in your version of Horizon. If another value is selected, revert to **Image** instead.

![create-windows-vm-horizon-web-console-04_creodias.png](../_images/create-windows-vm-horizon-web-console-04_creodias.png)

Enter **windows** in the search field in the **Available** section to filter Windows images:

![create-windows-vm-horizon-web-console-05_creodias.png](../_images/create-windows-vm-horizon-web-console-05_creodias.png)

Choose the newest available version by clicking **↑** next to it. As of writing of this article, it is **Windows 2022**.

![create-windows-vm-horizon-web-console-06_creodias.png](../_images/create-windows-vm-horizon-web-console-06_creodias.png)

Your chosen image should appear in the **Allocated** section:

![create-windows-vm-horizon-web-console-07_creodias.png](../_images/create-windows-vm-horizon-web-console-07_creodias.png)

Click **Next >**.

If you allocate a wrong image by mistake, you can remove it from the **Allocated** section by clicking **↓** next to its name.

Step 4: Choose flavor[🔗](#step-4-choose-flavor "Permalink to this headline")
----------------------------------------------------------------------------

In this step you will choose the flavor of your virtual machine. Flavors manage access to resources such as VCPUS, RAM and storage.

The following screenshot shows what the flavors table looks like in general:

![create-windows-vm-horizon-web-console-09_creodias.png](../_images/create-windows-vm-horizon-web-console-09_creodias.png)

The presence of yellow warning triangles means that the flavor in that row is unavailable to you. To see the exact reason for this unavailability, hover your mouse over that triangle, like so:

![create-windows-vm-horizon-web-console-21_creodias.png](../_images/create-windows-vm-horizon-web-console-21_creodias.png)

Here are the flavors which you can choose when creating a Windows virtual machine in each particular cloud:

WAW4-1WAW3-1WAW3-2FRA1-2

On WAW4-1 cloud there are no flavors which have the name containing with **w** so it cannot be used to run Windows.

On WAW3-1 cloud, only flavors which have the name starting with **hmw** can be used to run Windows.

Filter them by entering **hmw** in the search bar in the **Available** section:

![create-windows-vm-horizon-web-console-23_creodias.png](../_images/create-windows-vm-horizon-web-console-23_creodias.png)

On WAW3-2 cloud, only flavors which have the name starting with **hmaw** can be used to run Windows.

Filter them by entering **hmaw** in the search bar in the **Available** section:

![create-windows-vm-horizon-web-console-24_creodias.png](../_images/create-windows-vm-horizon-web-console-24_creodias.png)

On FRA1-2 cloud, only flavors which have the name starting with **hmw** can be used to run Windows.

Filter them by entering **hmw** in the search bar in the **Available** section:

![create-windows-vm-horizon-web-console-25_creodias.png](../_images/create-windows-vm-horizon-web-console-25_creodias.png)

Always be sure to check the actual flavors (that info can be found in the Horizon dashboard).

Choose the flavor which suits you best and click **↑** next to it to allocate it.

Click **Next >**.

Note

In examples that follow, we use two networks, one with name starting with **cloud\_** and the name of the other starting with **eodata\_**. The former network should always be present in the account, but the latter may or may not present. If you do not have network which name starts with **eodata\_**, you may create it or use any other network that you already have and want to use.

Step 5: Attach networks to your virtual machine[🔗](#step-5-attach-networks-to-your-virtual-machine "Permalink to this headline")
--------------------------------------------------------------------------------------------------------------------------------

The next step contains the list of networks available to you:

![create-windows-vm-horizon-web-console-10_creodias.png](../_images/create-windows-vm-horizon-web-console-10_creodias.png)

By default, you should have access to the following networks:

> * A network which has the same name as your project - it can be used to connect your virtual machines together and access the Internet.
> * The network which has **eodata** in its name - it can be used to access the EODATA repository containing Earth observation data.

Allocate both of them and click **Next >**.

The next step is called **Network Ports**. In it simply quick **Next >** without doing anything else.

Step 6: Choose security groups[🔗](#step-6-choose-security-groups "Permalink to this headline")
----------------------------------------------------------------------------------------------

Security groups control Internet traffic for your virtual machine.

In this step, make sure that the **default** security group is allocated. It blocks incoming network traffic and allows outgoing network traffic.

Group **allow\_ping\_ssh\_icmp\_rdp** exposes your VM to various types of network traffic but here, do **not** allocate it. It is not needed for the purposes of this article, since you will only access your virtual machine using the web console. You should still be able to perform standard Windows operations such as browsing the Internet or accessing e-mail without this security group.

![create-windows-vm-horizon-web-console-11_creodias.png](../_images/create-windows-vm-horizon-web-console-11_creodias.png)

Step 7: Launch your virtual machine[🔗](#step-7-launch-your-virtual-machine "Permalink to this headline")
--------------------------------------------------------------------------------------------------------

Other steps from the **Launch Instance** window are optional. Once you have done the previous steps of this article, click **Launch Instance** button:

![create-windows-vm-horizon-web-console-12_creodias.png](../_images/create-windows-vm-horizon-web-console-12_creodias.png)

Your virtual machine should appear in the **Instances** section of the Horizon dashboard. Wait until its **Status** is **Active**:

![create-windows-vm-horizon-web-console-13_creodias.png](../_images/create-windows-vm-horizon-web-console-13_creodias.png)

Once the **Status** is **Active**, the virtual machine should be running. The next step involves setting access to it.

Step 8: Set the Administrator password[🔗](#step-8-set-the-administrator-password "Permalink to this headline")
--------------------------------------------------------------------------------------------------------------

Once your instance has **Active** status, click on its name:

![create-windows-vm-horizon-web-console-14_creodias.png](../_images/create-windows-vm-horizon-web-console-14_creodias.png)

You should see a page containing information about your instance. Navigate to **Console** tab:

![create-windows-vm-horizon-web-console-15_creodias.png](../_images/create-windows-vm-horizon-web-console-15_creodias.png)

You should see the web console with which you can control your virtual machine. When the system finishes startup, you will see prompt to set the Administrator password:

![create-windows-vm-horizon-web-console-16_creodias.png](../_images/create-windows-vm-horizon-web-console-16_creodias.png)

Click **OK**. You should now see two text fields:

![create-windows-vm-horizon-web-console-17_creodias.png](../_images/create-windows-vm-horizon-web-console-17_creodias.png)

Enter your chosen password in the **New password** text field.

Enter it again in the **Confirm password** text field.

Click right arrow next to the **Confirm password** text field:

![create-windows-vm-horizon-web-console-18_creodias.png](../_images/create-windows-vm-horizon-web-console-18_creodias.png)

You should get the following confirmation:

![create-windows-vm-horizon-web-console-19_creodias.png](../_images/create-windows-vm-horizon-web-console-19_creodias.png)

Click **OK**.

Wait until you see the standard Windows desktop.

Step 9: Update Windows[🔗](#step-9-update-windows "Permalink to this headline")
------------------------------------------------------------------------------

Once the Windows virtual machine is up and running, you should update its operating system to have the latest security fixes. Click **Start**, and then **Settings**:

![create-windows-vm-horizon-web-console-26_creodias.png](../_images/create-windows-vm-horizon-web-console-26_creodias.png)

After that, click **Update & Security**:

![create-windows-vm-horizon-web-console-27_creodias.png](../_images/create-windows-vm-horizon-web-console-27_creodias.png)

You should now see **Windows Update** screen, which can look like this:

![create-windows-vm-horizon-web-console-28_creodias.png](../_images/create-windows-vm-horizon-web-console-28_creodias.png)

Follow the appropriate prompts to update your operating system.

What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------

If you want to access your virtual machine remotely using RDP (Remote Desktop Protocol), you should consider increasing its security by using a bastion host. The following article contains more information: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on 3Engines Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md)

To learn more about security groups, you can check this article: [How to use Security Groups in Horizon on 3Engines Cloud](How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md)