Skip to main content

Hybrid Entra Join

Co-Managing Windows Autopilot Hybrid Join Devices
· loading
Microsoft Intune Microsoft Configuration Manager Windows 10 and later Windows Autopilot Remediation Scripts PowerShell Hybrid Entra Join Co-management
Installing the Configuration Manager client on Hybrid Azure AD Joined Autopilot devices should be an easy process right?
Proactively Renaming Hybrid Azure AD Joined Devices
· loading
Microsoft Intune Windows 10 and later Windows Autopilot Remediation Scripts Hybrid Entra Join PowerShell
Nothing has really changed in the Hybrid Join Autopilot space when it comes to device names, and we’re still stuck with useless naming conventions for these devices; sometimes a prefix and random characters just isn’t a good enough identification method for Windows devices.
Renaming Windows Autopilot Hybrid Joined Devices
· loading
Microsoft Intune Windows 10 and later Windows Autopilot Hybrid Entra Join PowerShell
You’ve probably hit the limitation with Windows Autopilot Hybrid Azure AD Join deployments and the device name templates being less than flexible, restricting to only a prefix and, well, that’s it.