This content has been marked as final. Show 4 replies
The getCryptState command runs locally and does not query the database, so you can use that to get what you need. To run it remotely, you can use any of the normal tools that an enterprise might use (SMS, SCCM, Altiris, ZenWorks, Login Scripts, GPOs, etc) or you can use a tool like PSEXEC from SysInternals/Microsoft if you know the machines you want to target.
Since you mentioned AutoIt, I'll shamelessly recommend the UDF I wrote for AutoIt:
Here is an example of how you use the UDF, issuing a ForceSync:
If I have some free time later today, I'll write-up and post a GetCryptState example. Once you have the machine running your AutoIt script, it'd be easy to do with the results as you wish - write them out to a text file, registry key, http post, whatever.
No worries... I've done a bit of development myself with the VB interface to SBADMCL and AutoIt. I really, really appreciate the offer though. I will be taking a look at your UDF for sure! grin
Basically just gets the data back as XML, then loops over each drive to get the CRYPT value and writes it out. If the drive didn't return a value, it deletes it.
If you need the object ID for the machine, you can use the SBAdmCL function GetLocalMachineName.
If you do not provide credentials, it returns object ID. If you provide sufficient credentials, it will return object ID and name as it exists in database.