Welp!.. same here, brand new laptop, fresh Win10 1803 install, script 3.1.0 with no params, same error.
commented out lines 682 to 693, it worked like a charm.
Is the laptop on a domain?
Yes
BTW, Audit it works with v2.3.3
Thanks for the info. I'll compare the two versions of the script and see if anything changed around that area.
I have made some changes to the script. Can you grab a copy from the URL below and try it out?
https://raw.githubusercontent.com/Opmantek/open-audit/master/other/audit_windows.vbs
I have found and fixed the issue. FYI - It was for reading policies on the device. That requires Admin. If we don't get that now, we work around it (and obviously don't get the policies).
You can download the newer fixed version from GitHub. This will be in the next release.
https://raw.githubusercontent.com/Opmantek/open-audit/dev/other/audit_windows.vbs
No, I just run "cscript audit_windows.vbs" ... no parameters. No user or password.
I basically just change the IP of the server and the rest is untouched. My PC is a Fully updated Win 10 machine, my AD server is Windows 2003 Server (I know...). That's it. Just commenting those lines makes the script work.
Can you post the full command you are using to run the scrtip, please.
It "looks" like you are passing a username and possibly a password when auditing a local machine. This will not work (and never has).
I was using audit_windows.vbs version 3.0.0. Now when I try 3.1.0 I get:
My workaround was comment lines 682 to 693, and its working. Any Ideas?.
Thanks.
Andrés.
I have made some changes to the script. Can you grab a copy from the URL below and try it out?
https://raw.githubusercontent.com/Opmantek/open-audit/master/other/audit_windows.vbs
Hi Mark, I just run it. Same results.
Your user must have Admin rights on the PC to run the script.
Specifically, they must be able to connect to -
I have just confirmed this. An unpriviledged user returns this error, an Admin does not. If your user is an Admin, try running it in an elevated console.
Hi Mark, I just confirmed, Admin can run the script. But the question is if this is a desired situation. I like the fact that I can keep track of the users triggering the audit (I do it on login scripts). But with this change all I will see is Administrator using all PCs. The should be a way to detect the situation and avoid the error.
Andres,
You are correct. It never used to require Admin. I'll investigate why this is now so and see if we can work around this. No promises on a timeline.
Mark.
I have found and fixed the issue. FYI - It was for reading policies on the device. That requires Admin. If we don't get that now, we work around it (and obviously don't get the policies).
You can download the newer fixed version from GitHub. This will be in the next release.
https://raw.githubusercontent.com/Opmantek/open-audit/dev/other/audit_windows.vbs