I'm currently struggeling with some Windows 11 non-persistent PVS target devices in DaaS who are setup to be hybrid joined to Entra ID. The Entra ID join takes about 60 - 90 minutes each time after reboot no matter how frequent I reboot them. Checking the dsregcmd /status command I can see that the issue is as of below. The join phase is working eventually if I trigger it manually (dsregcmd /join) but first after approximately 20 - 25 minutes and after 60 - 90 minutes if I just leave it to join by itself. I keep getting the same error message every time until it suddenly works/joins fine. I have checked the event logs between the last failed attempt to the succeeded join but haven't found any event at all.
Previous Registration : 2024-11-20 10:46:08.000 UTC
Registration Type : sync
Error Phase : join
Client ErrorCode : 0x801c005b
Server ErrorCode : invalid_request
Server ErrorSubCode : error_computer_signature_check_failure
Server Operation : DeviceRenew
Server Message : The verification of the signature failed for device XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX in domain XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Https Status : 400
Request Id : XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Is there anyone who posses key knowledge that can explain to me what is happening between the failed attempts and the successfull join? Some certificate that is renewed, some checkup or synchronization from Entra ID that is slow? The strange thing is that I have the same exact setup with the same image in two others resource locations at different regional sites within the organization where the join phase is immediate after reboot. It takes only 3 - 4 minutes after boot for the devices to register.
Any hint or tip is much appreciated.
Many thanks in advance.
Question
Christoffer Olsson1709162627
Dear all,
I'm currently struggeling with some Windows 11 non-persistent PVS target devices in DaaS who are setup to be hybrid joined to Entra ID. The Entra ID join takes about 60 - 90 minutes each time after reboot no matter how frequent I reboot them. Checking the dsregcmd /status command I can see that the issue is as of below. The join phase is working eventually if I trigger it manually (dsregcmd /join) but first after approximately 20 - 25 minutes and after 60 - 90 minutes if I just leave it to join by itself. I keep getting the same error message every time until it suddenly works/joins fine. I have checked the event logs between the last failed attempt to the succeeded join but haven't found any event at all.
Previous Registration : 2024-11-20 10:46:08.000 UTC
Registration Type : sync
Error Phase : join
Client ErrorCode : 0x801c005b
Server ErrorCode : invalid_request
Server ErrorSubCode : error_computer_signature_check_failure
Server Operation : DeviceRenew
Server Message : The verification of the signature failed for device XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX in domain XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Https Status : 400
Request Id : XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Is there anyone who posses key knowledge that can explain to me what is happening between the failed attempts and the successfull join? Some certificate that is renewed, some checkup or synchronization from Entra ID that is slow? The strange thing is that I have the same exact setup with the same image in two others resource locations at different regional sites within the organization where the join phase is immediate after reboot. It takes only 3 - 4 minutes after boot for the devices to register.
Any hint or tip is much appreciated.
Many thanks in advance.
BR
//Christoffer
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now