Page 1 of 2
[SOLVED] “Not ready for Deployment, try again (20s)”
Published: March 26, 2026 - 08:33
by cedric_974
Hello,
I'm trying to deploy a Windows 11 machine from a Linux distribution.
I get to task 3: data server, and then it's stuck in a loop: "Not ready for Deployment, try again (20s)".
The same message appears in the status section of the console.
Thanks in advance.
Re: “Not ready for Deployment, try again (20s)”
Published: March 26, 2026 - 10:34
by dcardon
Hi Cédric,
did you check "start deployment in the console"?
Regards,
Denis
Re: “Not ready for Deployment, try again (20s)”
Published: March 31, 2026 - 10:15
by cedric_974
Good morning,
Yes, I select it from the menu, it then forces me to create a DJOIN.
I enter all the information, the ORs are clearly visible, and I can even choose a group to place the machine.
However, when I try to submit, I get this error:
- Screenshot 2026-03-31 121155.png (5.17 KB) Viewed 29221 times
And I'm back on the Data Server: "Not ready for Deployment, try again (20s)"
Thank you for your help.
Re: “Not ready for Deployment, try again (20s)”
Published: March 31, 2026 - 10:17
by sfonteneau
Hello,
could you try without adding the machine to an AD group?
Simon
Re: “Not ready for Deployment, try again (20s)”
Published: March 31, 2026 - 10:26
by sfonteneau
After looking into it, you're in a strange situation.
We're looking at the domain controller you selected.
Then we make an LDAP request with the name mentioned:
(dNSHostName=srvads.mydomain.lan).
This would mean that the domain controller you have doesn't have the correct value for the dNSHostName attribute.
Re: “Not ready for Deployment, try again (20s)”
Published: April 8, 2026 - 7:23 AM
by Ted_974
sfonteneau wrote: ↑March 31, 2026 - 10:17 AM
Hello,
Could you try without adding the machine to an AD group?
Simon
No, we cannot; we do not have control over the configuration XML files, and those offered by our organization require DJOIN.
So we find ourselves stuck; when we start the deployment, it asks us to prepare the DJOIN.
During DJOIN configuration:
-Our domain is indeed found in the list.
-Domain controllers are found and displayed in the list.
-The connection to the domain is established and the AD tree and OUs are displayed.
When we click on "Save" to validate the DJOIN
-The computer account is correctly created in the correct OU
-The error message "Unable to retrieve Domain Controller object" appears and the validation of this DJOIN step fails, preventing the deployment from starting and prompting the DJOIN preparation again...
Re: “Not ready for Deployment, try again (20s)”
Published: April 8, 2026 - 9:23 AM
by Ted_974
sfonteneau wrote: ↑March 31, 2026 - 10:26
After looking into it, you're in a strange situation.
We're looking at the domain controller you selected.
Then we make an LDAP request with the name mentioned:
(dNSHostName=srvads.mydomain.lan).
This would mean that the domain controller you have doesn't have the correct value for the dNSHostName attribute.
After checking in our AD, the value of the dNSHostName attribute of the domain controller is correct.
I assume that the LDAP query made by WAPT on our AD uses the credentials specified in the "Domain Credentials" section of the DJOIN configuration?
If that's the case, could our blockage stem from the permissions assigned to this account on AD?
Re: “Not ready for Deployment, try again (20s)”
Published: April 8, 2026 - 10:52 AM
by sfonteneau
Ted_974 wrote: ↑Apr 8, 2026 - 09:23
After checking in our AD, the value of the dNSHostName attribute of the domain controller is correct.
The associated code is as follows:
Code: Select all
if DomainController = '' then
DCObject := GetDCforIp(ldap)
else
DCObject := ldap.SearchFirst(ldap.WellKnownObject(lkoDomainControllers), FormatUtf8('(dNSHostName=%)', [DomainController]), ['dNSHostName', 'serverReferenceBL']);
if not Assigned(DCObject) then
raise Exception.Create('Unable to retreive Domain Controller object');
Can you try making the LDAP request with your account?
(dNSHostName=srvadcs.mydomain.lan)
srvadcs.mydomain.lan comes from the GUI join in the domain controller
Re: “Not ready for Deployment, try again (20s)”
Published: April 8, 2026 - 1:37 PM
by Ted_974
sfonteneau wrote: ↑Apr 8, 2026 - 10:52
Ted_974 wrote: ↑Apr 8, 2026 - 09:23
After checking in our AD, the value of the dNSHostName attribute of the domain controller is correct.
The associated code is as follows:
Code: Select all
if DomainController = '' then
DCObject := GetDCforIp(ldap)
else
DCObject := ldap.SearchFirst(ldap.WellKnownObject(lkoDomainControllers), FormatUtf8('(dNSHostName=%)', [DomainController]), ['dNSHostName', 'serverReferenceBL']);
if not Assigned(DCObject) then
raise Exception.Create('Unable to retreive Domain Controller object');
Can you try making the LDAP request with your account?
(dNSHostName=srvadcs.mydomain.lan)
srvadcs.mydomain.lan comes from the GUI join in the domain controller
Based on the LDAP query information in your response, I tried the following PowerShell command to verify that I can query the DC attributes
Get-ADComputer -identity "NOM_DU_DC" -Properties dNSHostname | select-object Name, dNSHostName
And the result of the command is:
"Get-ADComputer: Unable to find an object with the identity 'DC_NAME'"
I asked our domain admin to place the order with his account and the order works.
We are therefore leaning towards a problem with rights/delegations of our AD account on the DC.
Re: “Not ready for Deployment, try again (20s)”
Published: April 8, 2026 - 2:01 PM
by sfonteneau
Interesting... I haven't encountered this kind of configuration elsewhere (even on other sites within your organization).
This part of the code is open source and readable here:
https://github.com/tranquilit/pltis_djo ... n.pas#L194
We could theoretically do without it, but is the `serverReferenceBL` attribute at least readable?