Jump to content

Recommended Posts

Posted

Hopefully this is the right forum for this, but please could it be moved if not

 

As with many others, no doubt, I am sick to the back teeth of having little way of differentiating devices that are built with HAADJ Autopilot - just a sea of random names!

 

I have come across scripts for renaming (such as Naming Hybrid Azure AD Joined Autopilot Devices Automatically using a Custom prefix and Serial Number – SMBtotheCloud) and I have done one manually, but want to make sure what I am seeing on Entra is also OK.

 

image.png.1859afb5f9c20b07bb493dbcc350485b.png

 

Prior to rename, the associated Intune and Entra devices matched, naturally. They now don't. But the Entra device doesn't seem to "work" anyway and if clicked and then selected to Manage, it comes back as device not found. This is the same for all our HAADJ devices

 

Is this to be expected and, should we go full AADJ in the future, would it present an issue? Could there be anything omitted from the Entra Connect application that we run locally?

 

I also did a test build which was AADJ joined only and renamed that PC (via Intune) and it changed both. In that case, the Entra device does exist, though

 

Many Thanks :)

 

 

 

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...