No known issues with slow scan times from Server 2016.
Are you stating a scan to a single server is taking 5 hours or are you scanning multiple servers? That scan time is fairly unheard of..
Are any of the target machines the target server located over a WAN, VPN or similar network connection?
Is this scan and deployment or just a scan alone?
I start a scan on PC groups about 300 computers per group, the majority of computers are in the LAN, and some in the WAN.
The rise of the scane take 5 hours for a group of computers in a mixed LAN-WAN.
Do you think the information lift slow scan Ivanti problem is related to the virtual machine?
Under powered VMs could cause slower scans, but 5 hours is on the extreme side. What are the specs of your console machines?
My guess is the machines located over the WAN are the cause of the scan taking 5 hours. The scan doesn't complete until all machines are scanned so a single WAN machine increase the time of the scan. Are you able to split the WAN and LAN machines into different Machine Groups? That would allow the machines on the LAN to scan faster. For the WAN machines, I would suggest scanning a single machine and see who long it takes. Performing a ping -t against the target machine (during the scan) and look at the MS latency. This will tell us what to expect for these machines. If a machine on the LAN with <1MS latency takes 5 minutes to scan then a higher latency will increase the scan.