• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Using MS Baseline Security Analyzer v1.2

L

leeym

Member
I'm using MS Baseline Security Analyzer v1.2, and am scanning the IP address of a specific machine. The resulting message is "User is not an administrator on the scanned machine."

How is this possible if I'm logged into that machine as an Administrator. I've double checked the priviledges and everything is ok. Am I missing something?

Also, if I'm to scan an entire domain, or a wide range of IP's, must the user always be logged in as an Admin? If so, won't network admins have to run around all night logging into each machine so it be scanned for vulnerabilities?

Thanks
 
I'm using MS Baseline Security Analyzer v1.2, and am scanning the IP address of a specific machine. The resulting message is "User is not an administrator on the scanned machine."

How is this possible if I'm logged into that machine as an Administrator. I've double checked the priviledges and everything is ok. Am I missing something?
Click to expand...
What is the machine that you're scanning (Workstation, Server, etc.) and what are its roles (i.e. if it's a server is it a DC)?

Also what account are you running MBSA with and what privilages does it have over the machine you are scanning (not the account that's logged into the machine you're scanning, but the one that's actually running MBSA)?
Also, if I'm to scan an entire domain, or a wide range of IP's, must the user always be logged in as an Admin? If so, won't network admins have to run around all night logging into each machine so it be scanned for vulnerabilities?
Click to expand...
The account running MBSA must have administrative privilages over the target machine, it doesnt matter who is logged in to that machine locally.

The reason the account running MBSA needs administrative privilages is because it needs access to a number of the files and registry keys on the target machine(s) otherwise it cant review file versions.
 
Great questions:

1. I'm scanning another workstation in the same Workgroup. It's not a server, and it's not a DC.
2. I'm running MBSA from another workstation with Admin priviledges. Remember, I'm operating in a workgroup, not domain environment.

Thoughts?
 
yes, just as the error states the account on the machine you are located does not have administrative privilages on the machine you are scanning.
 
yes, use an account on the machine you are scanning from that has the same username and password as an account that has administrative privilages on the machine you are scanning (i.e. Administrator).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top