Azure Centric
EN PT
Hyper-V 6 min read

Use SSH for routine Linux guest administration

MN
Marcos Nogueira
On this page
  1. Why VMConnect is not the right tool for Linux administration
  2. Configure SSH for routine administration
  3. Key-based authentication
  4. Verification and next steps
  5. Prerequisites and limitations
  6. Additional considerations

You are running a Linux virtual machine on a Windows Server 2025 Hyper-V host and need to perform routine administration. The temptation is to use Virtual Machine Connection (VMConnect). However, for Linux guests, VMConnect provides only a basic console session. It does not support the enhanced session mode features like clipboard sharing, drive redirection, or smart card authentication, which are restricted to recent Windows operating systems Use local resources on Hyper-V with VMConnect. Relying on VMConnect for day-to-day tasks introduces friction and limits automation. The correct approach is to configure SSH. This provides a standard, secure, and scriptable interface that aligns with Linux best practices.

Why VMConnect is not the right tool for Linux administration

VMConnect is a valuable tool for initial setup, troubleshooting, or accessing a VM when the network stack is broken. It allows you to use local resources like printers, USB drives, and the clipboard, but only when the guest operating system supports enhanced session mode Use local resources on Hyper-V with VMConnect.

For Linux guests, enhanced session mode is not available. You are limited to a basic console session. This means you cannot easily copy and paste text or files between your host and the Linux guest. You cannot redirect local drives to the Linux guest for easy file transfer. While you can resize the VMConnect window, the experience is fundamentally a video feed of the guest console, not a rich integration. For routine administration, this is inefficient. You are forced to type commands manually, retype long strings, or find workarounds for file transfer.

The source documentation notes a path for Linux-based guest VMs at /home/shared-drives Use local resources on Hyper-V with VMConnect, but this is inconsistent with the explicit restriction that enhanced session mode features are available only for recent Windows operating systems. In practice, Linux guests do not receive the resource redirection capabilities that make VMConnect useful for Windows guests. You should not expect drive redirection or clipboard sharing to work reliably in this scenario.

Configure SSH for routine administration

SSH is the standard protocol for secure remote administration on Linux. It is lightweight, secure, and supports key-based authentication, which is far superior to password-based logins for automation. It also allows you to use standard Linux tools and scripts.

To set up SSH on your Linux guest, you need to install the SSH server package. The exact command depends on your distribution. For Debian-based systems like Ubuntu, you would use:

sudo apt update
sudo apt install openssh-server

For RHEL-based systems like CentOS or RHEL, you would use:

dnf install openssh-server
systemctl enable sshd
systemctl start sshd

Once the SSH service is installed and running, you need to ensure it is accessible from your host. This requires configuring the virtual network adapter on the Linux VM to be connected to a virtual switch that provides network connectivity to the host. You also need to ensure that the network configuration on the Linux VM allows inbound connections on port 22.

Key-based authentication

Password-based authentication is convenient for initial setup but is weak for routine administration. It is susceptible to brute-force attacks and is difficult to automate securely. Key-based authentication is the preferred method. You generate a key pair on your host machine and copy the public key to the Linux guest.

On your Windows host, you can generate an SSH key pair using the OpenSSH client tools. Note that ssh-keygen is an external command, not a native PowerShell cmdlet. You must ensure the OpenSSH Client feature is installed on your Windows Server 2025 host. If it is not installed, you can add it via PowerShell:

Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0

Once the feature is installed, you can generate an Ed25519 key pair:

ssh-keygen -t ed25519 -C "your_email@example.com"

This command creates a new key pair. You will be prompted for a file location and a passphrase. The passphrase adds an extra layer of security. Once the key pair is generated, you need to copy the public key to the Linux guest. You can do this manually by appending the content of the public key file to the ~/.ssh/authorized_keys file on the Linux guest. Alternatively, if you have password-based access, you can use the ssh-copy-id command:

ssh-copy-id -i ~/.ssh/id_ed25519.pub user@linux_vm_ip

After copying the public key, you can disable password authentication on the Linux guest for added security. Edit the SSH configuration file /etc/ssh/sshd_config and set PasswordAuthentication no. Then restart the SSH service.

Verification and next steps

To verify that SSH is working, connect from your host to the Linux guest using the SSH client:

ssh user@linux_vm_ip

If key-based authentication is configured correctly, you will be logged in without being prompted for a password. If you set a passphrase, you will be prompted for it. This connection is secure and encrypted. You can now perform routine administration tasks using standard Linux commands. You can also use tools like scp or rsync to transfer files securely between your host and the guest.

For more complex scenarios, such as managing multiple Linux VMs, consider using an SSH config file on your host to define aliases and connection parameters. This simplifies the process of connecting to different VMs. You can also use SSH agents to manage your keys and avoid entering passphrases repeatedly.

VMConnect remains a useful tool for initial setup and troubleshooting, but it should not be your primary interface for day-to-day operations. By configuring SSH and implementing key-based authentication, you align with Linux best practices, improve security, and enable automation.

Prerequisites and limitations

To follow this guide, you need:

  • A Windows Server 2025 Hyper-V host.
  • A Linux virtual machine running on the host.
  • Network connectivity between the host and the Linux VM.
  • Administrative privileges on the Linux VM to install and configure the SSH server.
  • The OpenSSH Client feature installed on the Windows host for key generation.

SSH is a text-based protocol. It does not provide graphical desktop access. If you need a graphical interface, you will need to set up a remote desktop protocol like RDP or VNC on the Linux guest. SSH also does not provide native access to local resources like printers or USB devices. If you need to use these resources, you will need to set up a separate solution, such as USB over IP or a network printer.

SSH requires configuration on both the host and the guest. This can be a barrier for users who are not familiar with Linux administration. However, the long-term benefits in terms of security and automation outweigh the initial setup effort.

Additional considerations

  • Firewall configuration: Ensure that the network configuration on the Linux VM allows inbound connections on port 22. You may need to create a new inbound rule for this purpose.
  • SSH hardening: Consider implementing additional security measures, such as disabling root login, changing the default SSH port, and using fail2ban to block brute-force attacks.
  • Key management: Regularly rotate your SSH keys and remove any unused keys from the authorized_keys file on the Linux guest.
  • Documentation: Document your SSH configuration and key management procedures to ensure consistency and ease of troubleshooting.

By addressing these additional considerations, you can further enhance the security and reliability of your SSH connection.

Search