There are five ways I know.
1. If you are on the machine itself, in windows, you can look at the show status log and scroll to the top, if log has not been cleared, you will see when machine first entered into database in log and it will tell you Machine ID.
2. You can also look in SbClientLog.txt located in C:\Program Files\McAfee\Endpoint Encryption for PC folder. It is essentially the show status window. But remember, if log cleared from sys icon---it is gone here too.
3. Go to login screen, hit cancel, hit Options, Recover, Machine Recovery----there you will see Machine ID=0x000 hex number. This is the most reliable.
4. On console you look for machine in database and to the right of name you will see hex id.
5. If you know the user of machine, do an audit of the user, it will show the name and hex id of machine you are seeking.
Safeboot---that assumes tou have sbadmcl.exe on local machine and by default, it isn't there with a normal install. Least not that I recall. Have you added the exe part to your client files or a separate download to client machine?
no, put the exe and sbadmdll.dll in a NEW file group, mark it as a client file type, then add it to existing machines. Of course if you're using something like autodomain it will already be there.
You don't need sbadmcom.dll unless you want to use the COM interface.Both the COM and EXE are simply interfaces to the DLL itself.
Thanks Simon---we want to use forcesynch which needs this exe and the sbadmdll.dll within a script that forces a synch and does other things (windows updates, download dats) to update a machine.