[Issue] - Health Checker

Provide Version Number
Exchange Health Checker Version 26.06.09.1656

Describe the issue
Hi, what if there is an issue with healthchecker.ps1 showing an issue with IIS bindings and when we log in to check in IIS for port 444, there are no certificates bond to port 444

Expected behavior
Healthchecker.ps1 highlighted 4 issues, Issue one reboot - resolved, Issue 2 issue above looking for self signed certs to be configured for each exchange server port 444, Issue 3 - Optimise network settings for the network adapter that is running on VMware server, Issue 4 memory has not been dedicated to Exchnage current RAM is 32GB.

Script Output
Warning: We recommend for the best performance to have a minimum of 128GB of RAM installed on the machine.
Dynamic Memory Detected: True 0GB is the allowed dynamic memory of the server. Not supported to have dynamic memory configured.
PageFile: System is set to automatically manage the PageFile Size: 0MB
Error: On Exchange SE RTM Feb26SU, the recommended PageFile size is 25% (8192MB) of the total system memory (32768MB).
More information: https://aka.ms/HC-PageFile
Warning: We recommend for the best performance to have a minimum of 128GB of RAM installed on the machine.
Dynamic Memory Detected: True 0GB is the allowed dynamic memory of the server. Not supported to have dynamic memory configured.
Sleepy NIC Disabled: False --- Warning: It's recommended to disable NIC power saving options
More Information: https://aka.ms/HC-NICPowerManagement
NIC Teamed: False
Packets Received Discarded: 93 --- Warning: This value should be at 0.
Known Issue with vmxnet3: 'Large packet loss at the guest operating system level on the VMXNET3 vNIC in ESXi (2039495)' - https://aka.ms/HC-VMwareLostPackets
Disable IPv6 Correctly: False
Default Web Site Started False http - *:80: - NULL
https - :443: - xxxxxx
http - 127.0.0.1:80: - NULL
https - 127.0.0.1:443: - xxxxxxxx
Exchange Back End Started False http - *:81: - NULL
https - *:444: - Cert thumbprint 'xxxxxxxxxxxxxxxx' not found on server

Certificate Binding Issue Detected: 'xxxxxxxxxxxxxxxxxxxx' Doesn't exist on the server and this will cause problems.

Additional context
The main concern is with issue 2 "there are no certificates bond to port 444", and concerned that if we apply the patch and reboot the server may not have running services.

Start with healthchecker.ps1 and trace the certificate-binding check that reports the Exchange Back End HTTPS binding on port 444. Reproduce the report against the IIS binding and certificate state described in the issue, then clarify whether the check or the server configuration is at fault; done means the expected certificate status is established and the reported warning is accurate.