The Example Command section of the readme shows both the -Credentials and -Credential arguments. Using '-Credentials domain\username' throws the error "A parameter cannot be found that matches parameter name 'Credentials'.", which makes sense, because there's no variable named 'Credentials' in the script.
Using '-Credential domain\username' appears to work, however the script is still running as the user who launched the PowerShell window, and retrieves permissions. Logs on a scanned server show my own account accessing shares on the system, rather than the alternate credentials. This causes false scan results when the script is run by an account that may have elevated rights over some of the systems targeted by the scan.
The Example Command section of the readme shows both the -Credentials and -Credential arguments. Using '-Credentials domain\username' throws the error "A parameter cannot be found that matches parameter name 'Credentials'.", which makes sense, because there's no variable named 'Credentials' in the script.
Using '-Credential domain\username' appears to work, however the script is still running as the user who launched the PowerShell window, and retrieves permissions. Logs on a scanned server show my own account accessing shares on the system, rather than the alternate credentials. This causes false scan results when the script is run by an account that may have elevated rights over some of the systems targeted by the scan.