KONNECT ACCESS+ · Installation

Konnect Access+ on Microsoft Hyper-V

From ISO to first login — in six steps.

00:00 / 00:00

Now playingOverview

From ISO to first login — in six steps.

Chapters

OverviewWhat you needKonnect Access+ on Microsoft Hyper-VFrom ISO to first login — in six steps. Welcome to the installation of Konnect Access on Microsoft Hyper-V. In this video, we will set up the virtual machine completely — from ISO to the first login. Step one: We download the system image and verify the file. Step two: Preparing the Hyper-V host. Step three: We create the two virtual switches — one for the internet, one for the guest Wi-Fi. Step four: We create the virtual machine using the wizard and adjust the settings. Step five: We boot from the ISO and install the system. And step six: the first login and the network checklist to ensure you go live safely. Here is what you need before you start. With these preparations, the installation takes about thirty minutes. A Hyper-V host: Windows Server 2019, 2022, or 2025 — or Windows 11 Pro with the Hyper-V role enabled. Two physical network ports are important: one for the internet, one for the guest Wi-Fi. The system image konnect-access-v1.3.iso from your customer account, plus the SHA-256 file for verification — and your license key, which is listed with the product in your account. Network data: a management IP with gateway and DNS for the WAN side, the VLAN IDs of the guest Wi-Fi if it is tagged, and the guest subnet. The default is 10.1.19.0/24. During installation, the VM needs internet access: the installer downloads updates and the geo-location. Expect about fifteen minutes for copying. How large does the virtual machine need to be? That depends on the number of concurrent users. For up to five hundred concurrent users, two virtual CPUs, four gigabytes of RAM, and one hundred gigabytes of SSD are sufficient. The typical hotel is in the 'Medium' tier: up to two thousand users, four virtual CPUs, eight gigabytes of RAM, and a two hundred gigabyte hard drive. We will use these values in the video. Large facilities with up to ten thousand users get eight CPUs, sixteen to thirty-two gigabytes of RAM, and five hundred gigabytes of storage. For anything above that, we plan an enterprise setup with you — sixteen or more CPUs, sixty-four gigabytes of RAM, NVMe storage, and a high-availability pair. Keep the key data for Hyper-V in mind: Generation 2, Secure Boot off, static RAM, two network adapters. A dynamic VHDX is fine.
ISO & HostCheck download, enable Hyper-VThe image and the hostVerify file and turn on Hyper-V. You can find the system image on konnect-plus.com in your customer account under Konnect Access, in the 'Documents & downloads' list. The 'System image (ISO)' row downloads the file — about five gigabytes. The SHA-256 file is right next to it. If the row still says 'On request', our team will unlock the image for your license. Below that is your license with the 'Licence key'. You enter this key in the console after installation — use the copy icon to add it to your clipboard. Before you use the image, verify the file. This is how you rule out a corrupted download. In PowerShell on the Hyper-V host: Get-FileHash with the SHA256 algorithm calculates the checksum. Get-Content shows the target value from the .sha256 file. Both values must be identical — otherwise, download it again. Copy the ISO to a local hard drive on the host, for example D:\ISO. Hyper-V cannot boot from a network share. If Hyper-V is not yet installed on the host, do it now. The host will restart once during this process. On Windows Server, 'Install-WindowsFeature Hyper-V' with the management tools is sufficient. On Windows 11 Pro, use 'Enable-WindowsOptionalFeature' for Microsoft-Hyper-V. In the BIOS or UEFI of the host, Intel VT-x or AMD-V and VT-d must be active. Secure Boot can remain enabled on the host. This is the Hyper-V Manager. On the left is the host, in the center are the virtual machines, and on the right are the actions. Everything else happens here. In the 'Actions' pane on the right, you will find 'New' for a new virtual machine and the 'Virtual Switch Manager'. We will need both shortly.
Virtual SwitchesSeparating WAN and guest Wi-FiTwo switches, two tasksInternet on one, guest Wi-Fi on the other — never mixed. Konnect Access sits between two networks. That is why the VM needs two virtual switches with two physical network cards. The first switch is called 'WAN'. It is of the type 'External' and is connected to the first physical network card — the hotel LAN with internet, DNS, and the PMS. In the VM, this becomes adapter one, or eth0: the management interface through which you reach the console. The second switch is called 'Guest'. Also external, but connected to the second network card, which leads to the guest Wi-Fi — to the access points or the Wi-Fi controller. This becomes adapter two, eth1: the guest gateway with the address 10.1.19.1. This is where the captive portal, DHCP, and RADIUS run. The access points deliver guest traffic unchanged to this switch. The hotel's admin network never belongs on the guest switch. Open the 'Virtual Switch Manager' in the Hyper-V Manager. 'New virtual network switch' is already selected on the left. There are three types: 'External', 'Internal', and 'Private'. For Konnect Access, both switches need the 'External' type because they are connected to real network cards. Select 'External' and click on 'Create Virtual Switch'. Now for the properties of the new switch. Enter 'WAN' as the name — this way you will recognize the switch later in the VM settings immediately. Under 'External network', select the physical network card connected to the hotel LAN. Each card may only belong to one external switch. Leave the 'Allow management operating system to share this network adapter' checkbox checked for the WAN switch if the host accesses the network via the same card. Click 'Apply' to create the switch. The host's network connection will drop for a few seconds — this is normal. Repeat the process for the second switch named Guest on the second network card. For this switch, uncheck the box for the management operating system — the host does not need an address in the guest network.
Virtual machineThe wizard, page by pageCreating the VMName, generation, memory, network, hard disk, and ISO. Now for the virtual machine. Right-click on 'New' and then on 'Virtual Machine…'. The 'New Virtual Machine Wizard' begins with the 'Before You Begin' page. Click on 'Next'. Page 'Specify Name and Location': Name the VM KONNECT-ACCESS. You will need this name later for PowerShell commands. Check the box 'Store the virtual machine in a different location' and select a drive with enough space, for example D:\Hyper-V. Page 'Specify Generation': Select 'Generation 2' — UEFI boot, faster and more modern. This choice cannot be changed later. Page 'Assign Memory': Enter 8192 megabytes for 'Startup memory' — eight gigabytes for the Medium tier. Uncheck the box 'Use Dynamic Memory for this virtual machine'. A gateway with RADIUS and a database requires fixed memory. Page 'Configure Networking': Select the WAN switch for 'Connection'. This will be the first adapter. We will add the second adapter in the settings shortly. Page 'Connect Virtual Hard Disk': 'Create a virtual hard disk', size 200 gigabytes. Hyper-V creates it dynamically — it only occupies as much space as is actually used. Page 'Installation Options': Select 'Install an operating system from a bootable image file' and enter the path to the Konnect-Access-ISO for 'Image file'. The summary shows all values again: name, generation 2, 8192 MB, network WAN, the hard disk, and the ISO. Clicking 'Finish' creates the VM — it is not started yet.
SettingsSecure Boot, CPU, second adapterThe settings that matterEverything else remains at the Hyper-V default values. Before we start, we will adjust four things in the VM settings. Generation 2 with UEFI — and Secure Boot disabled. Eight gigabytes of static RAM. Four virtual processors. On a host with many VMs, you should reserve the performance. Two hundred gigabytes VHDX, dynamically expanding. Adapter one on the WAN switch: It receives the management IP — first via DHCP, later statically — and reaches the internet, DNS, and the PMS. Adapter two on the Guest switch: for tagged guest Wi-Fi as a VLAN trunk, plus MAC spoofing on, DHCP guard and router guard off. The new VM is now in the list. Select KONNECT-ACCESS and right-click on 'Settings…'. Go to 'Security' on the left and uncheck 'Enable Secure Boot'. The Linux image will not start with Secure Boot enabled. Under 'Processor', set 'Number of virtual processors' to 4. Under 'Memory', check: 'RAM' 8192 MB, 'Enable Dynamic Memory' remains off. Now for the second adapter: 'Add Hardware', select 'Network Adapter', 'Add'. For the new adapter, select Guest as the 'Virtual switch'. If the guest Wi-Fi is a single tagged VLAN, activate 'Enable virtual LAN identification' and enter the VLAN ID — here 100. For multiple guest VLANs, use the trunk via PowerShell instead; more on that in a moment. Expand the adapter and open 'Advanced Features'. Activate 'Enable MAC address spoofing' — otherwise, Hyper-V will block guest traffic. Below that, 'Enable DHCP guard' and 'Enable router advertisement guard' must remain off. Konnect Access is itself the DHCP server and router for the guests. For multiple guest VLANs, adapter two becomes a trunk. The Hyper-V Manager cannot do this — but PowerShell can. Set-VMNetworkAdapterVlan with -Trunk and the list of allowed VLAN IDs, native VLAN zero. Then Set-VMNetworkAdapter with MAC spoofing on, DHCP guard off, router guard off. Get-VMNetworkAdapterVlan shows the result. Only enter your guest VLANs — never the admin or PMS VLAN. For a single untagged guest network, skip this step. Under 'Automatic Start Action', select 'Always start this virtual machine automatically'. After a host restart, the guest Wi-Fi will be back up without any intervention. Save all settings with 'OK'.
InstallationBoot from ISOBoot and installationThe boot menu, the installer, and the first start. Use 'Connect…' to open the 'Virtual Machine Connection' console window. Click on 'Start'. The VM boots from the ISO. In the boot menu, 'Install KONNECT+ OS' is preselected — confirm with Enter. If you encounter graphics issues, select the 'safe graphics' entry. The KONNECT+ OS Installer opens with the 'Welcome' page. On the left, you can see the six steps: Welcome, Location, Keyboard, Partitions, Install, and Finish. The installer language remains 'American English' — you will set the console itself to your language later. Click 'Next' to continue. Page 'Location': The installer detects the location via the internet and marks it on the map. Check 'Region' and 'Zone' — the time zone determines when guest access expires and how reports are dated. Then 'Next'. Page 'Keyboard': Select your console layout, for example 'English (US)' or 'German'. You can test it at the bottom. Then 'Next'. 'Partitions' page: Select 'Erase disk'. The virtual hard drive is empty — the installer will create all partitions automatically. Under 'After', you see the result: a small EFI partition and the system on the rest of the 200 gigabytes. The installation begins with 'Install'. Page 'Install': The system is being copied to the hard disk. The progress bar runs for about ten to fifteen minutes. Let the VM work undisturbed. 'Finish' page: 'All done.' The installation is complete. 'Restart now' remains checked — click 'Done' to restart the VM, now booting from the hard drive. On the first boot, KONNECT+ OS asks for the network mode for eth0, the WAN adapter. 'Current IP' shows the address the adapter received via DHCP. For now, select 'DHCP' — you can set the fixed management IP comfortably in the console later. If you want to assign the fixed address immediately, select 'Static' and enter the IP address, netmask, gateway, and DNS. 'DHCP Success': The console shows the assigned IP address and the address of the platform — http://<ip>/platform. Note this address. The VM opens the console in kiosk mode: 'Welcome to KONNECT+'. You can reach the same page from any computer in the admin network via https://<ip>/platform.
First loginConsole and licenseThe first loginOpen console, change password, enter license. Three small things after installation. In Hyper-V, eject the ISO: 'Settings', 'DVD Drive', 'None'. The hard drive is at the top of the 'Firmware' boot order, and the automatic start action is active. This is what the 'DVD Drive' page looks like: set 'Media' to 'None' and confirm with 'OK'. And under 'Firmware', the 'Boot order': move 'Hard Drive' to the top using 'Move Up'. The console shows the IP address of the VM. Open https://<ip>/platform from the admin network, log in with the credentials from the account, and change the password immediately. This is the Konnect Access console. First steps: enter the static management IP and guest VLANs under 'Network', paste the key from your customer account under 'License', then connect the PMS. Each area is explained step-by-step in the online presentation.
Network checklistBefore you go liveNine checks before go-liveThese points prevent nine out of ten support requests. Finally, the network checklist. Go through these nine points before the first guests go online. Guest side: Only one DHCP server in the guest network — Konnect Access. Disable DHCP on the WLAN controller for this VLAN. Only the guest VLANs are on the trunk. Enable MAC spoofing, disable guards. And the access points forward traffic unchanged — without their own captive portal. WAN side: A static management IP after installation. Internet, DNS, and NTP must be reachable. In the firewall, allow HTTPS 443 to the console only from the admin network, and SSH only for IT. The PMS must be reachable — Opera on-premise via port 1521 or IFC8 FIAS for Opera Cloud. And outbound HTTPS to konnect-plus.com for updates and license verification. That was the installation of Konnect Access on Hyper-V. If you have any questions, our support team is here to help — you can find the contact details in your customer account.