I ran into an interesting situation this morning. I ran a couple of reports last night, a LastSynchDate, and a Client Version. This morning I was comparing the two and stumbled on an interesting situation. I have a machine that reports as having 5.2.1 in the Version report, and has a LastSynchDate of 12/3/2009. Not a big deal, but we didn't roll out 5.2.1 until after the New Year. So I went and connected remotely to the client machine, and took a look at the SBClientLog.txt, and it's happy as can be, had synched this morning without any issues. So, I figured okay maybe this is one of the machines that added the 0001 to the end in the database. Went to the admin console, searched for the machinename with the wildcard, and the only thing that popped up was the machinename from the report, whose audit log showed a last synch of 12/3/2009.
So basically, I have a client that is reporting up to the database, but I have no idea which machine object it is related to. My question is, Is there a way to determine the machine ID that a client is associated with from the client remotely? I know that if I call the user and have them do a machine recovery, I can get the machine ID. But I want a way to do it without bothering the user. Is there a registry entry or api that I can run that gives me the local client's machine ID?
I tried that before I posted on here, just forgot to mention it...
I used the ID Only switch, and GetmachineID switch , seperately. I just get a return of "ResultCode = 0xdb000002; Result Description = The database has not been created or initialized yet"Message was edited by: R3k1awyk5 on 3/25/10 8:41:38 AM GMT-06:00
I think it should be -command:getlocalmachinename -file:t.txt -idonly
you don't need admin creds to get the local ID, but you DO if you want to get the name. If you need that, then the command is telling you that it can't connect to the listed database name.
whats the command line you are using?
where did you get :true from? 🙂
you also need -adminpwd, not -admipwd. that won't work.
and finally, you don't need admin account details if you only want the id, but you DO need the -file parameter.
I got ":true" because the default is false and I wanted that information, and every other switch you use with SBADMCL needs some parameter.
Sorry about the typo on adminpwd:
Why do I have to write it to a file? I just want it to display on my rclient session.
I ran "sbadmcl -command:getlocalmachinename -idonly -file:id.txt
ResultCode = 0xe0050004
ResultDescription = The wrong version of the Endpoint Encryption for PC is currently active