'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Intune Device Enrollment Naming Convention Not Working
Question details
New devices enrolled in Microsoft Intune are failing to receive the configured naming convention (e.g., RIB-%SERIAL%).
- Product
- Microsoft Intune
- Device & OS
- not provided
- Scenario
- Enrolling new devices using an Intune enrollment profile.
- Observed behavior
- Devices are assigned to the correct enrollment profile but do not successfully receive the specified RIB-%SERIAL% device name.
Ensure that you have global administrator or Intune administrator privileges in the Microsoft Endpoint Manager admin center to review and modify enrollment profiles.
Verify Intune Enrollment Profile and Device Naming Settings
Check the existing enrollment profile settings to ensure the naming template is configured correctly and applied to the proper device group.
Sometimes, formatting errors or sync delays prevent the naming template from applying correctly during the Out-of-Box Experience (OOBE). Verifying the template syntax and assignment is the primary troubleshooting step.
Log in to the Microsoft Endpoint Manager admin center using your administrator credentials.
Go to 'Devices' > 'Enroll devices' and select the specific deployment program, such as 'Windows Autopilot deployment profiles'.
Select the profile assigned to the affected devices and click 'Properties' to edit the configuration.
Review the 'Device name template' field. Ensure 'Apply device name template' is set to Yes and the template uses correct macros like %SERIAL% or %RAND:x%.
Deploy WPS Office to Your Intune-Managed Devices
While managing your endpoint infrastructure with Microsoft Intune, consider deploying WPS Office as a lightweight, cost-effective productivity suite for your organization. It seamlessly replaces heavy alternatives while maintaining strict document compatibility.
- 1. Download the Installer: Get the lightweight WPS Office installer suitable for enterprise deployment.
- 2. Upload to Endpoint Manager: Add the installer as a Win32 or Line-of-Business (LOB) application in your Intune console.
- 3. Assign to Groups: Deploy the application silently to your enrolled device groups for automatic provisioning.
Frequently Asked Questions
What variables are supported for Intune device naming conventions?
Intune Autopilot deployment profiles typically support the %SERIAL% macro for the hardware serial number and %RAND:x% for a random string of numbers, where 'x' represents the number of digits.
Why did my Autopilot device not rename after successful enrollment?
Device renaming during the Autopilot process can sometimes fail if the device does not reboot after the Enrollment Status Page (ESP) phase, or if there is a synchronization delay with Azure AD.
Can I manually rename a device from the Intune admin center?
Yes. You can manually rename a managed Windows device by navigating to 'Devices' > 'All devices', selecting the specific device, and clicking the 'Rename device' action from the top menu.
