Category: Virtual Server (EN)

To install Windows Server 2022 on your KVM server, you need to go through a few important steps. This guide will show you how to do it easily and quickly. All you need to do is enable the ISO feature, activate VNC, and prepare the ISO installation. After that, the installation of Windows Server 2022 can begin smoothly!

Note: This guide may look very long and might be intimidating. However, we have documented every single step to ensure you won’t face any unexpected surprises.

Enable ISO Feature

To use the ISO feature in the web interface, you first need to activate it in the settings.

• Click on “Miscellaneous” in the left menu
• Then open “VCP Settings”
• Go to the “Expert Functions” tab
• Set the “Enable ISO Upload for KVM Server” setting to “Enabled”.

A new menu entry will now appear in the navigation of your servers that are compatible with the ISO functionality, called the ISO Installer.

Activate VNC

To manually install your server later, you will need a VNC connection. This can be done easily through the browser.

• Open the cloud manager of the server where you want to install Windows.
• Click on “VPS Settings” in the action panel
• Open the tab named “VNC”.
• Enable VNC if it is not already enabled. You will need to stop and restart the server for the VNC functionality to be activated, allowing you to access the installation via the browser.
• Close the window and stop the server. Wait patiently until the server is fully shut down.
• Restart the server. Wait patiently until the process is complete. The system needs some time to configure VNC.

Prepare ISO Installation

Now it’s time to open the ISO Installer. Click on the corresponding menu entry.

Then let the web interface load all the data. Here you will see all the information about installing with an ISO disk.

• Shut down the server via the action buttons in the ISO Installer if it is still online.
• The ISO URL field will now be activated. Click on “Show Available ISOs” to select a predefined ISO. We have provided many ISOs for you. However, you can also enter your own URL. This must be publicly available.
• For Windows Server 2022, open “Windows” and select Windows Server 2022.
• You can choose a suitable distribution in the ISO Distribution list, but “win” is sufficient here.
• When you are ready, click on “Download and Start”. The process may take a short while. You can monitor the status live.
• Wait until the status switches to “ISO ready, installation can start”.
• Now connect to the NoVNC web console by clicking on “Open VNC Console”.
• If the Windows Installer does not start, you can send a reset (executed in 3 seconds) by clicking “Send Reset Signal”. Sometimes the installation starts only when any key is pressed at startup.

Install Windows Server 2022

Now you are in the Windows Server Setup.

• Select the desired language, time zone, and keyboard layout.
• Click on Next.
• Click on “Install Now”
• Wait for the setup to start.

Choose Operating System to Install

• Now select the operating system. In most cases, you will want to install “Windows Server 2022 Standard Evaluation (Desktop Experience)”. This is the second entry. Select this one.
• Click on Next.

Accept License Terms

• Accept the Microsoft Software License Terms by checking the box.
• Click on Next.

Select Installation Type

• Click on “Custom: Install Microsoft Server Operating System only” (2nd entry).

Select Disk for Installation

You now need to load a driver so that Windows can recognize the virtual disks. We have already inserted a virtual DVD with the appropriate drivers into your server.

• Click on “Load Driver”.
• Click on “Browse”.
• Find the CD drive “vz-tools-win” and navigate to
  • CD:\viostor\2k22\amd64
• Click on “OK”.

Windows will now load the necessary drivers.

• There should now be an entry for “Virtuozzo VirtIO SCSI controller”.
• Click on “Next”.
• Let Windows load the driver.
• The drives should now be recognized.
• Select each drive once and click “Delete”. This will remove the old operating system (Linux or Windows) from the server.
• Select the remaining drive and click on “Next”.
• Now Windows Server 2022 will be installed.

Wait patiently for this process to complete. The time it takes depends on the number of CPU cores. Windows will restart after the process is complete.

Prepare Windows

Windows has now booted from the disk.

• Enter your desired administrator password.
• Repeat your Windows password.
• Confirm by pressing “Enter” or clicking on “Finish”.

First Login

We are not quite done with the preparation yet. You need to log in via VNC once and enable RDP.

• Send a CTRL+ALT+DELETE signal to the server via VNC to access the login screen. You can find this option in the left menu panel of your VNC browser session.
• Log in with the administrator password you set earlier.

Wait for Windows to start the Server Manager.

Enable Remote Desktop

• In the Windows Server Manager, click on “Local Server”
• Click on “Disabled” next to “Remote Desktop”.
• In the dialog that opens, select “Allow remote connections to this computer”.
• Confirm the following information by clicking “OK”.
• Uncheck “Require Network Level Authentication” (directly below).
• Click “Apply”, then “OK”.
• Click on the “Refresh” icon at the top of the Server Manager to ensure that Remote Desktop is now enabled.

Configure Network

Final Step: Install Network Drivers

To actually connect to your server now, Windows of course needs a network connection. By default, the drivers for the virtual network card are not installed. But once again, the included driver DVD will help.

• Right-click on the Start button in the bottom left.
• Select “Device Manager”.
• Double-click on the entry with a warning triangle named “Ethernet Controller”.
• In the dialog that opens, click on “Update Driver”.
• Click on “Browse my computer for drivers”.
• Click on “Browse”.
• Again, search for the drive “Virtuozzo Tools”. Here you only need to select the drive.
• Make sure “Include subfolders” is selected.
• Click on “Next”.
• Wait for Windows to install the network driver.
• If Windows asks if the PC should be discoverable by other computers on the network, make sure to click “No”!

Complete ISO Installation

Now go back to the web interface and click on “Complete Installation” in the ISO Manager. The server will now be stopped one last time, the ISO will be removed, and the server will then be restarted.

You have now installed Windows and can connect to your server via Remote Desktop!

If you want to send an email from your server, there are many things to consider. You need a clean configuration so other mail providers do not classify your emails as spam or reject them completely. Sometimes the error messages can be a bit confusing.

If there is a configuration problem, Google might reject your emails with the following error message:

550-5.7.1 [45.145.224.X] The IP you're using to send mail is not authorized to 
550-5.7.1 send email directly to our servers. Please use the SMTP relay at your 
550-5.7.1 service provider instead. For more information, go to 

The IP you’re using to send mail is not authorized to send email directly to our servers. Please use the SMTP relay at your service provider instead. For more information, go to …

Why does this error occur?

Google rejects emails sent from IP addresses listed in the Spamhaus database. This is to prevent spam and unwanted emails. This can cause the error message.

How can I fix this problem?

1. Check your IP address: Go to Spamhaus. Enter your server’s IP address to see if it is listed.
2. Remove the IP from the list: Follow the instructions on the Spamhaus website to remove your IP address from the database. Usually, removal is immediate.
3. Use an SMTP relay server: Instead of sending emails directly from your server, configure your mail server to use an SMTP relay server provided by your service provider. This increases the chances of your emails being delivered correctly.

If you have any questions about this topic, you can check Google’s error codes (https://support.google.com/a/answer/3726730?hl=en) or contact our support team.

How can I clone my server?

Cloning a server at Prepaid-Hoster is an easy process that you can complete in a few steps. Here’s how you can clone your server.

Step 1: Enable Data Backup

First, turn on data backup on your old server. This is important to ensure that all your data is securely stored.

Step 2: Create a Backup

Create a backup of your server. This will be used as a template for cloning.

1. Go to the Backup Section: Sign in to the web interface and navigate to the backup section of your server.
2. Start the Backup: Click on “Create Backup.” You may be asked to enter a name and description for the backup.
3. Wait for Completion: The backup process can take a few minutes to several hours, depending on the size of your data.

Step 3: Get a New Server

Get a new server that has at least the same amount of disk space as the original server. This is necessary to transfer the backup to the new server.

Step 4: Transfer Backup

In the management area, select the option “Clone from Backup.”

1. Select the Backup: In the clone section, choose the previously created backup from the list.
2. Select Destination Server: Choose the new server to which the backup should be transferred.
3. Confirm: Check the box “Yes, I understand that my data on the server will be deleted and replaced with the chosen backup!”

Step 5: Start Cloning Process

Click on “Transfer Backup” and confirm. You will then be redirected to the maintenance window. The server will shut down, the backup will be downloaded, and installed on the new server. This process can take varying amounts of time depending on the size of the disk.

Following these steps should help you successfully clone your server. If you have any further questions, our support team is always here to help.

This guide will help you quickly and easily log into your Windows server with Prepaid-Hoster and use the Remote Desktop connection.

Preparation:

Remote Desktop is automatically enabled on Windows servers:

• Make a note of your server’s IP address.

Find your password in the Cloud Manager:

• Log into the Cloud Manager and navigate to your server to retrieve the password.

Install Windows after purchase:

Go to your server in the Cloud Manager and select the option to install Windows.

Connecting

Open Remote Desktop Connection on your Windows PC

• Press Win + R, type mstsc, and hit Enter.
• Enter the server’s IP address and click Connect.

Enter your login details

• Username: Administrator
• Password: Your assigned password (from the Cloud Manager)

Accept certificate warning

• You may see a warning that the identity of the remote computer cannot be verified. This is because the certificate is not from a trusted certification authority.
• Check “Don’t ask me again” and click Yes to continue the connection.

Tips

• Security: Ensure your password is strong and secure.
• Performance: Close unnecessary programs to improve connection quality.

Conclusion

This guide helps you efficiently access your Windows server. If you encounter any issues, our support team is always available to help.

At Prepaid-Hoster, the security of your server is our top priority. That’s why we have developed the Security Manager – a powerful tool that checks your Linux server for known vulnerabilities and provides advice on how to address these weaknesses. In this FAQ entry, you will learn about the security checks performed by the Security Manager and effective ways to secure your server.

Possible Vulnerabilities

At Vionity, we assess your Linux server for potential vulnerabilities. We focus on common weaknesses that even inexperienced users can address.

Name	Issue	Description
SSH Default Port	Using the standard SSH port	The standard SSH port (22) is widely used and therefore a popular target for attacks. Changing the port can enhance security.
FAIL2Ban not installed	Lack of protection against brute-force attacks	FAIL2Ban is a security program that blocks IP addresses after multiple failed login attempts. Without FAIL2Ban, the server is more susceptible to brute-force attacks.
No Root SSH Keys	Authentication via password	SSH keys are more secure than passwords. Without SSH keys, the server is more vulnerable to password theft and brute-force attacks.
SSH Root Password Auth enabled	Allowing root login via password	Direct root login via password is insecure. It is better to disable root logins or only allow them through SSH keys.
Failed Login attempts (high)	Many failed login attempts	Many failed login attempts can indicate brute-force attacks. This requires immediate attention and appropriate measures.
Java Root Process	Running Java as root process	Java processes running as root can pose a security risk as any vulnerability in Java can provide full access to the system.
TeamSpeak Root Process	Running TeamSpeak as root process	Running TeamSpeak processes as root can jeopardize the entire system in the event of software vulnerabilities.

Detailed Description of Security Issues

SSH Default Port

The SSH default port 22 is often the target of automated attacks. Changing this port to a less well-known number can reduce the attack surface of your server. This is a simple but effective measure to enhance security.

FAIL2Ban not installed

FAIL2Ban protects your server from brute-force attacks by blocking IP addresses after multiple failed login attempts. Without this safeguard, your server remains vulnerable to repeated attack attempts that could ultimately succeed.

No Root SSH Keys

Using SSH keys instead of passwords offers higher security. Passwords are more prone to being stolen or guessed through brute-force attacks, while SSH keys are more difficult to compromise. It is recommended to allow root access only through SSH keys.

SSH Root Password Auth enabled

Direct root logins via password should be disabled as they pose a significant security risk. It is safer to grant root access only to a regular user who can then obtain root privileges using sudo or su.

Failed Login attempts (high)

A high number of failed login attempts can indicate ongoing brute-force attacks. It is important to monitor these attempts and take appropriate measures such as blocking the attacker’s IP or implementing additional security mechanisms.

Java Root Process

Java applications should not be run as root processes as vulnerabilities in Java can lead to complete system compromise. It is safer to run Java applications with a non-privileged user.

TeamSpeak Root Process

Similar to Java, TeamSpeak should not be run as a root process. Security vulnerabilities in TeamSpeak could be exploited to compromise the entire system. It is better to run TeamSpeak with its own restricted user account.

General Advice

Regular Updates

Ensure that your system and all installed packages are regularly updated. Security updates address known vulnerabilities and enhance stability. Learn how to update your VServer on our FAQ page.

Set Up a Firewall

Use a firewall like ufw (Uncomplicated Firewall) or iptables to prevent unauthorized access. Enable only the necessary ports.

User Management

Create separate user accounts for different tasks and grant only the necessary permissions. Avoid working regularly as the root user.

Create Backups

Make regular backups of your data and configurations. Automate the backup process to prevent data loss.

Don’t Copy Commands You Don’t Understand

Look at a command before copying it into your console. A wrong rm -rf or a chmod in the wrong directory can jeopardize the security of your server and render it unusable.

Quick Solutions

• How do I change the SSH port?
• Creating and using SSH keys
• Disabling SSH password authentication

Sources

• SSH Security Best Practices
• FAIL2Ban Official Documentation
• SSH Key Authentication Guide
• Java Security Overview
• TeamSpeak Security Advisory

If you need further information or specific guidance on implementing security measures, please let me know!

You’re trying to access your server but it’s not working? You’re receiving a message that the login credentials are incorrect? Don’t worry! We’re here to help you. Let’s work together to get RDP access to your Windows server.

Check the installation

If you order a Windows server from Prepaid-Hoster, it will initially be delivered with a Linux system. You need to install Windows on the server through the web interface. In the Cloud Manager, “Windows Server” should be selected in the operating system field. If not, perform the Windows installation first.

Default login credentials

You can find your login credentials in Vionity in the Cloud Manager.

IP Address	See welcome email/web interface
Username	Administrator
Password	See welcome email/web interface

Troubleshooting

Check the username

Make sure you enter the correct username. By default, this should be either Administrator or LocalAccount\Administrator. Sometimes a typo or incorrect capitalization can be the cause.

Reset the password in the web interface

If you’re sure that the username is correct but the password still isn’t working, you can reset it in the web interface. Log in to your Prepaid-Hoster account, navigate to the RDP settings, and reset the password to the default value. After that, you can log in with the new password.

Use IP address instead of hostname

Try using the direct IP address of the server instead of the hostname. In some cases, this can solve connection problems caused by DNS or network issues.

Other common sources of errors and solutions

• Typos: Double-check that you entered the password correctly. Pay attention to uppercase and lowercase letters.
• Special characters: Sometimes certain characters in the password can cause problems. Try using a simpler password without special characters to narrow down the issue.
• Connection settings: Verify that your network settings are correct and that you have a stable internet connection.

If the above steps don’t solve your problem, you can contact Prepaid-Hoster support. Prepare all relevant information to expedite the process. The exact error message you receive during login will be crucial – preferably send it to us.

In this guide, you will learn how to connect to your server using the SSH client PuTTY. We will be using example data for this purpose. If you are unsure about which data is being referred to, you can find all the data in the Cloud Manager of your virtual server.

We will be using the IP address 62.68.75.47, the default port 22, and the password cxp9zqaJ.

Connection guide

Downloading and installing PuTTY

1. Download PuTTY: Go to the official PuTTY website and download the latest version for your operating system.
2. Installation: Run the downloaded file and follow the installation instructions.

Starting PuTTY

1. Open PuTTY: After the installation, open PuTTY. You will see the configuration window where you can set up your connection settings.

Configure connection settings

1. Host Name (or IP address): Enter the IP address of your server: 62.68.75.47.
2. Port: The default SSH port is 22. Make sure this port is entered.
3. Connection type: Select SSH if it is not already selected.
4. Save session (optional): If you want to save these connection settings for future use, enter a name under “Saved Sessions” (e.g. “My Server”) and click “Save”. This will allow you to easily restore the connection later. Your window should now look like this.

Establishing the connection

Tip: If you receive a prompt regarding a host key, click “Yes”. This message should only appear during the first connection.

1. Click Open: Click “Open” to establish the connection. A terminal window will open and prompt you to enter your username.
2. Enter username: Enter root and press Enter.
3. Enter password: You will now be prompted for your password. Enter the password cxp9zqaJ and press Enter. Note that the password will not be displayed during input (not even as asterisks). Your terminal window should now look like this:

Successfully connected

If you have entered everything correctly, you are now successfully logged in to your server. You should see a prompt that looks like this:

root@62540-47788:~#

Now you can navigate the Linux file system, update the server to the latest version, or install programs.

IPv6 addresses offer numerous advantages for modern networks, particularly in server administration. With multiple IPv6 addresses, you can run different services on different addresses, manage security zones better, and set up virtual hosts. This improves the organization, security, and accessibility of your services.

However, when using KVM servers with Vionity, there is a challenge: Vionity overwrites the interfaces file with each restart, causing manual changes to be lost. To ensure that additional IPv6 addresses persist after each restart, alternative methods like scripts in the if-up.d and if-down.d directories are necessary. These guarantee a stable and consistent network configuration despite Vionity’s interventions.

Step-by-step guide

If you want to add additional IPv6 addresses to your default interface (e.g., eth0) and ensure that these settings persist after a reboot, follow this guide. Here, you will learn how to create scripts for if-down.d and if-up.d to add and remove the IPv6 address 2a12:edc0:4:1337::4242/64.

Make sure you have root privileges, as you will need to make changes to the network scripts.

Add IPv6 address

Create script for if-up.d:
Create a new file in the directory /etc/network/if-up.d/. Name it, for example, add-ipv6.

sudo nano /etc/network/if-up.d/add-ipv6

Content of the script add-ipv6:

#!/bin/sh
# Add additional IPv6 address when eth0 interface comes up

if [ "$IFACE" = "eth0" ]; then
   ip -6 addr add 2a12:edc0:4:1337::4242/64 dev eth0
fi

Make the file executable:

sudo chmod +x /etc/network/if-up.d/add-ipv6

Remove IPv6 address

Create script for if-down.d:
Create a new file in the directory /etc/network/if-down.d/. Name it, for example, remove-ipv6.

sudo nano /etc/network/if-down.d/remove-ipv6

Content of the script remove-ipv6:

#!/bin/sh
# Remove additional IPv6 address when eth0 interface goes down

if [ "$IFACE" = "eth0" ]; then
   ip -6 addr del 2a12:edc0:4:1337::4242/64 dev eth0
fi

Make the file executable:

sudo chmod +x /etc/network/if-down.d/remove-ipv6

Test the configuration

After creating and executing the scripts, you can restart your network interface to test the configuration:

sudo ifdown eth0 && sudo ifup eth0

Then, check if the IPv6 address has been added correctly:

ip -6 addr show dev eth0

If everything is set up correctly, the IPv6 address 2a12:edc0:4:1337::4242/64 should be displayed.