@theopenem_admin Here is an additional log file
service.log
It seems that changing the log setting in the UI did not propagate to the problem clients. the below is the section of the log after I manually changed the Log level
2022-07-29 09:48:01,386 DEBUG [4] ApiRequest - Provision/GetStartupInfo/
2022-07-29 09:48:01,583 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 33 Seconds.
2022-07-29 09:48:34,594 INFO [4] ServiceProvision - Verifying Client Provision Status
2022-07-29 09:48:34,653 INFO [4] ServiceProvision - Verification Complete
2022-07-29 09:48:34,670 DEBUG [4] ApiRequest - Provision/GetIntermediateCert/
2022-07-29 09:48:35,041 ERROR [4] ServiceAD - Active Directory Search Failed:
2022-07-29 09:48:35,042 ERROR [4] ServiceAD - Current security context is not associated with an Active Directory domain or forest.
2022-07-29 09:48:35,044 DEBUG [4] ServiceProvision - Gathering Hardware Details
2022-07-29 09:48:36,408 DEBUG [4] ApiRequest - Provision/ProvisionClient/
2022-07-29 09:48:38,061 DEBUG [4] ApiRequest - ProvisionedComm/Provision/ConfirmProvisionRequest/
2022-07-29 09:48:38,704 ERROR [4] ApiRequest - Invalid Reponse, Signature Missing: ProvisionedComm/Provision/ConfirmProvisionRequest/
2022-07-29 09:48:38,705 DEBUG [4] ServiceInitialize - Provision Client: Error
2022-07-29 09:49:08,732 DEBUG [4] ApiRequest - ProvisionedComm/Provision/ConfirmProvisionRequest/
2022-07-29 09:49:09,302 ERROR [4] ApiRequest - Invalid Reponse, Signature Missing: ProvisionedComm/Provision/ConfirmProvisionRequest/
2022-07-29 09:49:09,303 DEBUG [4] ServiceInitialize - Provision Client: Error
2022-07-29 09:49:39,340 DEBUG [4] ApiRequest - ProvisionedComm/Provision/ConfirmProvisionRequest/
2022-07-29 09:49:39,827 ERROR [4] ApiRequest - Invalid Reponse, Signature Missing: ProvisionedComm/Provision/ConfirmProvisionRequest/
2022-07-29 09:49:39,830 DEBUG [4] ServiceInitialize - Provision Client: Error