Forum Discussion
Windows "management name" field has wrong timezone
I noticed that our devices that are being registered into Intune (Hybrid join) register OK, but oddly the "management name" field always seems to append a time that is four hours ahead of our timezone, even though the machines have the correct time zone. This does not impact functionality but I can't find where I would set that as part of the import parameters. Is there a place where I can customize that "management name" field?
1 Reply
The behavior you are experiencing, where the “management name” field in Intune Hybrid Join devices shows a timestamp that's four hours ahead of your local timezone, is a known quirk. While it doesn’t impact how everything works, it might cause some confusion about consistency and control.
The timestamp added to the management name field (like username_Windows_MM/DD/YYYY_HH:MM) isn't based on your device’s local time. Instead, it comes from the Intune backend or Azure AD registration service, which often operates in UTC or another standard time zone.
Azure AD and Intune are global services that typically log events in UTC or server local time, not your device’s local time.-
The management name is automatically generated when your device joins Hybrid or enrols in MDM, and it uses the server-side timestamp when that event took place.- You can't change
this timestamp through import settings or configuration profiles it’s a system-generated ID meant for internal tracking and ensuring uniqueness.
Reference: https://learn.microsoft.com/it-it/office/troubleshoot/activation/activation-error-0xcaa50021
