<div>
Are you scanning using a domain account or a local computer account?
</div>


<div>
So that user is in the admins group? (I mean, the name alone doesn't matter).<br />
Can you connect tor \\remotepc\admin$? That has to work or MBSA will fail.
</div>


<div>
This is a local computer account. &nbsp;No domain.<br />
A scan directly on the target works.<br />
McKnife: \\remotepc\admin$ ... that's a good test! &nbsp;It works.<br />
<br />
I've now progressed to where I get:<br />
&nbsp;<b><i>Cannot contact Windows Update Agent on target computer, possibly due to firewall settings. </i></b>Otherwise it seems to be working.<br />
&nbsp;<br />
I've researched this a bit but don't find anything that seems to apply.
</div>


<div>
See if you can reach port 135 at the remote pc:<br />
telnet remotepc 135<br />
(telnet needs to be installed as a windows feature, first).
</div>


<div>
Good pick. It runs on Windows 8.1 so I had assumed also on Windows 10.
</div>


<div>
I'm running 2.3 from Windows 7 but I have a choice as far as that OS goes. &nbsp;For now, Windows 7 is more readily available.<br />
I do need to scan Windows 10 machines so it looks like that will mostly work.<br />
The current target is Windows 7 Pro SP1<br />
Port 135 and others are open on the target. &nbsp;I've constructed a script to deal with most of the WMI needs that includes opening the suggested ports.<br />
<br />
One thing I'm a bit unsure about:<br />
If port 135 (for example) is needed, I see that the firewall rules have opened it a number of times - which suggests that there are other uses. &nbsp;But there is very little going on with this particular target so it may not be an issue right now. &nbsp;Maybe later on other machines?
</div>


<div>
If you are unsure what that scan needs: just deploy a GPO that adds a complete exception for incoming traffic from your scanning machine - all ports open to the scanning IP. Do the scan, remove the rule, all is good.
</div>


<div>
McKnife. &nbsp;Yes, I suppose I could do that but if I put this into production then that would be very tedious if it applied to a lot of machines.<br />
<br />
But, my uncertainty goes in the other direction:<br />
- If I open a port that's already being &quot;used&quot; then what happens? &nbsp;Multiple app's or services listening on that port? &nbsp;Is that OK? &nbsp;In some cases I don't see tools that will allow one to force the addressed port from the outside to be something different.
</div>


<div>
Firewall rules don't open ports. Firewall rules allow or deny access to ports that are already open, where some service is listening. Common language goes &quot;open that ports on your firewall&quot; but that is misleading.<br />
<br />
You would not do any harm with it.
</div>


<div>
McKnife: &nbsp;Nice distinction. &nbsp;I'd not thought of it quite that way but it's clear. &nbsp;And it sure answers my question! &quot;Not Blocked&quot; is passive. &nbsp;Listening is active. &nbsp;<br />
<br />
Later today, one of the sites will be set up so that the Administrator question should be clarified.<br />
We'll see what happens next. &nbsp;But, since the machines in question already had them matching, I'm not sure why the message and the failure to work.
</div>


<div>
As noted above, and after some checks of my own, MBSA will NOT run on Windows 10.<br />
<br />
<a href="http://betanews.com/2015/10/16/check-your-pc-network-security-with-microsoft-baseline-security-analyzer/" rel="ugc">http://betanews.com/2015/10/16/check-your-pc-network-security-with-microsoft-baseline-security-analyzer/</a>
</div>


<div>
What might be an alternate tool that's similar to MBSA?
</div>


<div>
At this point there is no counterpart for Windows 10. Why? MBSA was for older less secured systems and Windows 10 is the most secured Windows system yet. So there is no apparent need.
</div>


<div>
John Hurst: Actually there is a pressing need. &nbsp;Do I need to justify my questions just for you?
</div>


<div>
Fred, may I assume that you did not get it to run, although you turned off the firewall?<br />
I know no alternative. You'd need to look at security scanners, maybe &quot;nessus&quot; or exploit scanners. Those do similar checks, but won't be as small and easy as MBSA. There should be no problem with MBSA, though , as long as<br />
1 the scanning user is admin on the remote system<br />
2 the ports are allowed
</div>


<div>
At this point, short of alternatives McKnife has suggested, there is not a Microsoft alternative to MBSA - such does not exist.<br />
<br />
If the need is pressing, back away from Windows 10 until an upgrade to or replacement for MBSA has been announced.
</div>


<div>
My apologies: &nbsp;I switched the context of the question when it became clear that Windows 10 isn't a viable target for MBSA. &nbsp;So, I asked for suggestions of alternative tools.<br />
<br />
I am in very early stages of using tools like this and in the very early process of learning what settings are necessary on the targets. &nbsp;I figure that all the tools of this type do share those requirements for the most part. &nbsp;<br />
<br />
I have focused on ManageEngine EventLog Analyzer as a likely candidate for SIEM implementation.<br />
I was trying MBSA as an adjunct.<br />
I just tried LanSweeper with pretty good success but I don't know if its pricing will be OK.<br />
So, I was looking for suggestions along these lines.<br />
I suppose I should ask a new question.
</div>


<div>
You are welcome and I was happy to help.
</div>


<div>
<div class="content wysiwyg-content">
I am scanning some computers with Microsoft Baseline Security Analyzer. &nbsp;Windows 7 Pro is the host for the scanner.<br />
One Windows 10 Pro machine returns:&quot;User is not an administrator on the scanned Machine&quot;<br />
Yet the username and password for the current user is identical between the machines!<br />
<br />
Now what??
</div>
</div>


I am scanning some computers with Microsoft Baseline Security Analyzer.  Windows 7 Pro is the host for the scanner.
One Windows 10 Pro machine returns:"User is not an administrator on the scanned Machine"
Yet the username and password for the current user is identical between the machines!

Now what??

&quot;User is not an administrator on the scanned Machine&quot; MBSA

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Operating system security (OS security) is the process of ensuring OS integrity, confidentiality and availability. OS security refers to specified steps or measures used to protect the OS from threats, viruses, worms, malware or remote hacker intrusions. OS security encompasses all preventive-control techniques, which safeguard any computer assets capable of being stolen, edited or deleted if OS security is compromised, including authentication, passwords and threats to systems and programs.

OS Security

IT Administration is the processes and best practices for programming and development, and incorporates methodologies for managing activities and projects. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, extreme programming and various types of agile methodology. The life-cycle "model" is a more general term for a category of methodologies, and a software development "process" a more specific term to refer to a specific process chosen by a specific organization.

&quot;User is not an administrator on the scanned Machine&quot; MBSA

"User is not an administrator on the scanned Machine" MBSA