In my VM lab environment, with absolutely no mail-enabled users yet - the instant I install Exchange 2016 and the server's CPU spikes through the roof.
The process eating all of the cycles is w3wp.exe (IIS), and numerous articles indicate that this could be caused by IOS / Android devices hammering the box. Unfortunately, in my case, this is a lab - and I have none of those devices in or around the server at all. Within the lab, I have yet to mail-enable any user account as well, of which there are only about 5 test accounts anyway.
I have started fresh installs multiple times, on both the Domain, and Exchange 2016 combo, but all have resulted in this same scenario.
The VMs (DC as well as Exchange) all have had 2 virtual procs, 8GB static RAM, fixed size hard drives of 300Gb. All over the required published specs needed for Exchange. I also do not experience this in my 2013 lab builds.
Any assistance would be appreciated.