Problem joining the AD - WADS (online) domain

[gavit]

Good morning,

When configuring the OS deployment via WAPT, I am unable to join the computer to the domain.
I have checked that my user has the correct rights and it is possible to join a computer to the domain (manually).

WAPT configuration
- WAPT version 2.3.0
- Debian server OS
- Windows 11 administration machine operating system

I'm using the win11_with_join_ad_online.xml conf file.
I made the following changes to this file:

Code: Select all

                
                 <Identification>
				<Credentials>
					<Domain>mydomain.lan</Domain>
					<Password>password</Password>
					<Username>wadsjoin</Username>
				</Credentials>
				<JoinDomain>mydomain.lan</JoinDomain>
			</Identification>

Code: Select all

		
<UserAccounts>
<LocalAccounts>
	<LocalAccount wcm:action="add">    
		<Password>
				<Value>password</Value>
				<PlainText>true</PlainText>
			</Password>
			<Description/>
			<DisplayName>superadmin</DisplayName>
			<Group>Administrators</Group>
			<Name>admin</Name>
		</LocalAccount>
	</LocalAccounts>
</UserAccounts>  				

Have you ever encountered this problem?

Also, I can't automatically retrieve the OEM keys, is there a specific procedure to follow?

Thank you in advance.

[dcardon]

Hello Gaëtan,

did the machine originally have a Windows 10 Home license or a Windows 10 Pro license?

We've already seen a deployment issue on a machine that had been running Home and to which a Pro license was added. During the installation with WADS (or MDT, for that matter), the Home license was reclaimed.

Regarding the second question, it would be best to start a separate thread to keep each topic one. Thank you

. Best regards,

Denis

[gavit]

Hello,

The computer historically had a Windows 10 Pro OEM license.

I will open another thread for my second request.


Sincerely,
Gaëtan Vittaz

[dcardon]

Hi Gaëtan,
does the machine deploy correctly if we remove the domain connection?
Denis

[sfonteneau]

Did you modify the activation key mentioned in the template?

It's best to modify the key in the job's column (we've had issues if the key is modified directly in the XML).

[gavit]

Hello,

The machine deploys correctly both online and with and without joining the domain, but it never reaches our domain.

Regarding the license key issue, I opened another request on the forum: viewtopic.php?t=3427.
However, I haven't modified the default key in the XML file.


Sincerely,
Gaëtan Vittaz

[sfonteneau]

Hello Gaëtan,

Regarding the license key issue, I've opened another request on the forum: viewtopic.php?t=3427

Actually, I asked the question again about the license because it can sometimes be related.

We had a case the other day of a connection that didn't work precisely because of the change in the Windows edition type.

Windows, in fact, failed to join the domain because it thought it was running as Windows Home due to the license in the BIOS

Alternatively, you can contact our support team to look at it together by phone and screen sharing, because I don't really have any ideas.

see you soon,

Simon