Without knowing exactly what you are querying it's hard to say for sure other than to stop using the name as a unique identifier for resources and state messages sent by those resources. The ResourceID should be maintained and thus your queries should use the resourceID and not the name.
OSD temporary name to real name
When deploying an image to an unknown PC, the OSD process assigns a temporary name with the format: MININT-xxxxx
Our task sequence reads the serial number of the device and sets the task sequence variable OSDComputername to the serial number which is then used when joining the domain.
All pretty standard.
However when querying the SQL database for state messages for the task sequence, all of the rows have the machine name as the temporary name.
This only seems to be an issue with unknown devices - known devices log all of the task sequence steps using the actual serial#/computername.
We use this to query to provide metrics/statistics for imaging at our various worldwide sites (device imaging count, reimaging count, how long for the process, number of items successful/unsuccessful, etc.)
Is there a way to "map" the temporary name to the real name? Or can you think of a way to get the temporary name recorded in some way for a device so I can "look it up"?
TIA
2 answers
Sort by: Most helpful
-
Jason Sandys 31,306 Reputation points Microsoft Employee
2020-08-18T18:23:05.133+00:00 -
Fiona Yan-MSFT 2,311 Reputation points
2020-08-19T04:21:59.473+00:00 Hi,
Thanks for posting in Q&A.
Could we create a CM Query or a CM Status Message query?Use Status Message queries for a more detailed view on task sequence deployments and individual steps.
For more details,please refer to this helpful articles:
https://msendpointmgr.com/2014/02/27/monitor-osd-with-status-message-queries-in-configmgr-2012/Hope this could help you. Thanks for your time.
Best regards,
Fiona YanPlease remember to mark the replies as answers if they help.