Windows 10: Setting up a device for user for Entra ID

So when I am setting up the device it saysConnecting to: My organisationUser name: User@myorganisationUser Type: AdministratorI do not understand the user type section I am logging onto the admin account as instructed am I doing something wrong?So I am logging on with the user account on the local admin account through Entra ID join.Kind regardsWilliam

:)

 

Some windows 11 devices shows as Entra ID registered in Intune

Some devices onboarded to Intune with self deploying Autopilot mode, and now they shows as Entra ID registered in Intune and not Entra ID joined. Why these shows Entra ID registered and how to make them appear Entra ID joined.

 

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.

 

I am setting up devices for my small business

So I will sign in using the user credentials on the admin side. Sign in through Entra ID

I will then log out of that user and give the device to the user, who can sign in to their own device. Will they have admin privileges or not? I presume not and they use the account as usual and the device is now managed.

1. I will set up the device remove unwanted applications and install required software.

2. Enroll the device into Entra ID by signing on with the user's credentials (Admin Account)

3. Verify within Intune

4. Run the MDATP script on the device. (Do I run this on the Admin side? Or does it not matter)

5. Verify the setup in defender

6. signout of the admin account and hand the device to the user where they can click 'other user' and sign in with there work credentials.

These steps should allow the device to be managed, download applications remotely, and track the device compliance. ETC?

I am optimistic this is correct but please enlighten me on areas of change or improvement. Many thanks