RE: Recommendations on uniquely identifying a system.
RE: Recommendations on uniquely identifying a system.
- Subject: RE: Recommendations on uniquely identifying a system.
- From: "Tom Fortmann" <email@hidden>
- Date: Thu, 5 Mar 2009 14:31:10 -0600
> It still isn't clear wether you are interested in tracking a very
> precise piece of hardware or a very precise registration against a
> server (whatever it is, since you didn't tell anything about it).
> Unless I'm wrong, these could be very different things. Could you
> elaborate?
We are trying to track a specific machine. This ID value will be sent in
all communications with our back-end server. The requirements are that it
should be globally unique and persist across application
uninstall/re-installs. I've added a person requirement to not leave any
stray files on the system after an uninstall.
My solutions is to combine the Mac address and the serial number to create
the unique ID. These are the Apple recommended values based on TN1103. If
either or both of these are not defined I may factor in the IOPlatformUUID
value, and as a last resort will default to generate a UUID.
Thanks to everyone for their input. I still haven't found any more
information on the IOPlatformUUID value, so I'm going to assume Mac and
serial number are still the preferred methods.
Tom
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden