Windows 10: How to get non-domain joined in use systems to be entra joined without having to touch the...

Is there a way for me to get my non-domain joined systems to be entra joined without having to touch each one?

:)

 

How to reserve Windows 10 for a non-domain joined PC (but perhaps fomerly domain joined)

My reservation icon for Windows 10 has not appeared. After ensuring i have all outstanding Windows updates, and run the script that runs scheduled tasks, the icon still doesn't appear.

Then there was the hint from
KB3081048:

> The "Get Windows 10" app doesn’t appear in Windows 7 or 8.1

>

> If your device is has been connected to a domain it may be blocked from the upgrade reservation.

It is entirely possible that for 2 or 3 minutes two or three years ago, my machine
was joined to a domain.

• What registry key is the upgrade advisor mistakenly using to determine if a machine is joined to a domain?
• How do i check if a machine was previously joined to a domain?
• How do i unjoin a non-domain joined machine from a domain?
• How do reserve a copy of Windows 10 for a non-domain joined PC?

Bonus Chatter: It's a Surface Pro 3

I tried using the
Media Creation Tool, but it fails with a non-descript error:



How do i upgrade to Windows 10 now that it is released?

 

Issue with Primary DNS Suffix Not Applying in User Driven Entra Join Deployment Profile

Hello,

1. I have an on-premises AD setup.
   
2. Intune Connector and Azure AD Connectors are configured and functioning correctly.
   
3. My requirement is to configure auto-pilot with an Entra Join Profile, enabling users to log in via Entra AD. After-login, users should be able to ping "server1" once connected to the VPN.
   
4. Currently, everything operates as expected, except users cannot ping "server1" directly. Instead, they must use the full domain name "server.mydomain.com" because the Primary DNS Suffix is not applied to the client machines.
   

To address my auto-pilot, I configured a User Driven Entra Join Deployment Profile under Devices -> Enrollment in Intune. The setup seemed to go through without any hitches. However, after a successful enrollment, the local machine did not pick up the Primary DNS Suffix. This is puzzling because I have ensured that the Domain Join configuration within Intune is correctly set up. Additionally, Entra Join shows as "Not Applicable" in the configuration profile.



Has anyone encountered a similar problem or can offer insights into what might be missing or misconfigured? I'm particularly interested in ensuring that users can access "server1" without having to specify the full domain name, implying that the Primary DNS Suffix needs to be applied automatically upon device enrollment.



Any guidance, solutions, or troubleshooting tips would be greatly appreciated.

 

Always On VPN non join domain


Hello,

So I deploy a Always on VPN on Windows Server 2019.
I follow guidance from this YouTube video


Basically I'm deploying 3 windows server (RAS, NPS, and AD with CA) and all of this server is join domain.
I setting the VPN to use IKE protocol and authenticate to radius server.
I create 2 policy on radius server, first one is authenticate using certificate and the second one is authenticate using user and password only.

For join domain endpoint there's a auto enroll certificate policy and can connect to the VPN seamlessly.
But I have problem to connect VPN for non join domain endpoint.

I've import the client certificate from join domain endpoint and also CA certificate and then export it to non join domain endpoint and setting the VPN like link below but not still work with the error "IKE authentication credentials are unacceptable"
https://social.technet.microsoft.co...ap-for-nondomain-computers?forum=winserverNIS

Can someone give me enlightenment of what could be wrong?

Note:
Both radius policy (using user or certificate for authentication) is tested with join domain endpoint and it works fine.