Windows 10: Dell Rugged Pro 14 - LTE does not start on Logon Screen after domain join

We’ve recently deployed a few Dell Rugged Pro 14 devices running Windows 11. Both after the Out-of-Box Experience and after applying our custom image, the LTE module initializes and connects at the Windows logon screen as expected.However, after joining the devices to a domain tested with both Azure AD and on-prem AD, the LTE connection no longer initializes until after a user logs in. This prevents users from logging in with Azure credentials and blocks access to network-dependent services like DUO MFA at the logon screen.We’re looking for guidance on how to restore LTE connectivity at the

:)

 

Windows 10 after joining 2012 domain will not allow logon of domain users

So I have a new computer, recently upgraded from 10 home to 10 pro.

I join the computer to the 2012 r2 domain. it seems to join fine, I see that it is listed in the domain directory. however, no domain user is able to desktop logon on, it gives out a username or password incorrect message, even using the original joining
user account. it is happy to unjoin, even with administrative accounts that will not allow desktop logon.

I tried domain\user user@domain even domain.local versions of same and double checked caps lock to no avail.

noted a curious thing. when I look at the Settings>System>about instead of the normal three gray boxes one of which should say join a domain, I get this:

 

domain login freezing when joining domain for the first time

Setting up a new Dell AIO pc as a workgroup pc was working correctly the minute I joined it to the domain (currently a 2012R2 domain) it wont logon to the domain user account and just sits there saying welcome and never actually logs in.

Anyone got any ideas?

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account? The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join. Thoughts?