-
Notifications
You must be signed in to change notification settings - Fork 10
Image Compatibility
PRTG is compatible with both Windows Server 2016, 2019 and 2022* based images. When installing in Server Core 2019 based images, PrtgDocker will automatically install the required fonts (Arial and Tahoma) required for PRTG's chart drawing library (Chart Director) that have been stripped from the base installation.
Attempting to use the 32-bit version of PRTG Server will cause immediate crashes upon starting when utilizing any version of PRTG using Themida anti-cracking software (PRTG 16.4.28+). The the 64-bit version of PRTG will always be automatically installed when the host server contains at least 6gb RAM.
Due to the way that Docker for Windows works, the version of Windows running within a container must roughly match the version of Windows running outside of the container. This requirement can be circumvented however through the use of Hyper-V. For more information please see Hyper-V Isolation.
- Server 2022 MUST be Windows Updated to run PRTG inside Docker. For more information, see below
If you've downloaded a Windows Server Core base image after February 11, 2020, please note that these images are incompatible with the version of Server 2016 and Server 2019 that is installed out of the box. In order to successfully install PRTG in these images, please make sure the version of Windows on your Docker host is at least higher than the February 11, 2020 update. If there is an issue with your Docker host and/or container version, you may find that the PRTG installer will fail with error code -1073741511.
To check whether your Docker Host is up to date, run the following command to check the version of Windows installed on the host
C:\> winver
Microsoft Windows Server
Version 1607 (OS Build 14393.2248)
...If you've already attempt to run New-PrtgBuild or have run docker pull on the appropriate Server Core LTSC image already, you can inspect the version of the image to compare it with the version of your Docker host
C:\> docker inspect mcr.microsoft.com/windows/servercore:ltsc2016 -f "{{.OsVersion}}"
10.0.14393.3930To find out what update each version correspond to, simply Google the build number. In this scenario, we can see that while the container image is running the September 8, 2020 update, the host is only running the May 8, 2018 update, so will likely encounter issues when attempting to install PRTG inside of Docker.
To remediate these issues, simply keep applying Windows Updates to your host system until it is up to date and the version reported by the system is newer than the version of the container image.
For more information please see the following articles
- Host and Container Version Compatibility
- You might encounter issues when using Windows Server containers with the February 11, 2020 security update release
If you experience issues with WMI requests inside your docker container in Server 2016, you may be suffering from issues introduced in Windows Update KB5014702 which hardens DCOM by default. To resolve this issue, set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\AppCompat -> RequireIntegrityActivationAuthenticationLevel to 0 on each host you wish to monitor with WMI and then restart. This solution is merely a stop-gap however as from March 14, 2023 DCOM hardening will be force enabled with no way to disable it. While I don't know whether Server 2019 suffers from these issues, I can confirm that Server 2022 containers on Server 2022 hosts work without issue.
On a fresh installation of Windows Server 2022, the whole server may blue screen when PRTG Probes are run inside docker. Specifically, various WMI sensors such as WMI Uptime may cause the system to blue screen. Microsoft suspected this was due to a bug in msquic.sys on the host server; installing the July 2022 CU resolved this issue. msquic.sys should be at least version 1.0.4.0