Tutorials How to finalise your Windows Server deployment

How to finalise your Windows Server deployment

Creating a new Windows Server on UpCloud automatically performs the initial setup after deployment after which you can log in using Remote Desktop Connection. Here is a quick run-through on how to get this done.

Automated setup

Once the server has been deployed and is running, you will still need to wait for the Windows setup to complete. You can follow the setup process by viewing the server using the web console found in your UpCloud control panel. Open your server settings by clicking your server name, move to the Console tab, then click Open the console connection button.

Console connection

If the cloud server was just created, file system checks might still be running when you open the console.

Windows Server initializing

Once Windows has completed the initial setup, you’ll see the usual login screen.

Windows Server login screen

Your Windows cloud server is then ready to accept Remote Desktop connections.

Connecting using Remote Desktop

When the setup is done, you will land on the Windows login screen. From here on out you can close the web console and use the Microsoft Remote Desktop Connection instead. Log in using the user Administrator and the password you received via email or SMS.

RDC is a built-in feature on most versions of Windows and can be found in your start menu.

A version of the Remote Desktop is also available for macOS at the Mac App Store.

Linux has many options for open source applications that employ the Remote Desktop Protocol, for example, rdesktop or Remmina.

Changing localisation settings

Each new Windows Server deployment is configured setting region as US and language to US English by default. If you wish to change the localisation settings, log into your Windows Server and open the following menu:

Computer settings  > Time & Language > Region

Windows Server localization settings

Choose the country and regional format that best suit you. Country and region are best set as to where your server will be used, not necessarily the physical location of the cloud server.

Language and keyboard layout are set on the next menu page. Add a new language and select the keyboard layout that best matches your own keyboard.

Computer settings  > Time & Language > Language > Language options

Windows Server language settings

The keyboard layout option should be selected according to your own physical keyboard for the best usability later on.

Windows IPv6 Compatibility

If you wish to use IPv6 connectivity and have created an IPv6 address for the server, you must disable IPv6 address randomization. While logged in with RDC, open the command prompt or Power Shell and execute the following commands:

netsh interface ipv6 set global randomizeidentifiers=disabled store=active 
netsh interface ipv6 set global randomizeidentifiers=disabled store=persistent 
netsh interface ipv6 set privacy state=disabled store=active 
netsh interface ipv6 set privacy state=disabled store=persistent

Editor-in-chief and Technical writer at UpCloud since 2015. Cloud enthusiast writing about server technology and software.

One thought on “How to finalise your Windows Server deployment

  1. Can windows server be installed on the 1GB, 1 Core and 20GB disk plan? I don’t see how if Windows Server Core is not on the distribution choice?

    Can you please confirm?

Leave a Reply

Your email address will not be published. Required fields are marked *


Helsinki (HQ)

In the capital city of Finland, you will find our headquarters, and our first data centre. This is where we handle most of our development and innovation.


London was our second office to open, and a important step in introducing UpCloud to the world. Here our amazing staff can help you with both sales and support, in addition to host tons of interesting meetups.


Singapore was our 3rd office to be opened, and enjoys one of most engaged and fastest growing user bases we have ever seen.


Seattle is our 4th and latest office to be opened, and our way to reach out across the pond to our many users in the Americas.