![]() Hres=CoInitializeSecurity_(0, -1,0,0,#RPC_C_AUTHN_LEVEL_CONNECT,#RPC_C_IMP_LEVEL_IDENTIFY,0,#EOAC_NONE,0) MultiByteToWideChar_(#CP_ACP, 0, ansi, Len(ansi), unicode(), Size) #IFlags = #wbemFlagReturnImmediately + #wbemFlagForwardOnly While getting the MB serial would be ideal, I can live with generating a number that looked like a MS reg key or something. ![]() Something that looked official to keep the 1 or 2 who monkey with things from "adjusting" anything. The more I've thought about it I've realised that my users are compu-tards, so having a unique hash would be okay (not necessarily dependent upon hardware). Can't really change the MB in an IBM machine without putting another IBM board in and it's usually the same price to buy a new machine and keep the old for spare parts. Since most are on laptops, a CPU or MB identifier would be ideal as I can attest that these will not be changed very often. We occasionally (but not very often) change HDs to give the users more room (they like to save 700M TIFF images), but that's about it. We change NICs all the time in machines due to power surges/storms. ![]() In that case, mac address should suffice. It sounded to me like he wants an inventory system to keep track of things in a normal environment, where people aren't attempting to 'beat' the system. Yes, but almost anything an be cracked - and things can change (as I pointed out above). DoubleDutch wrote:MAC address is easy to fake. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |