MBSA Could not resolve the computer name

This is often due to the host and/or the target machines missing some
prerequisites. Check the items below:

First off, please ensure that all of the System Requirements have been met
as called out in the MBSA Help file. Depending on the situation, these may
include enabling the Workstation, Server, Remote Registry and File and Print
sharing services – and ensuring that the administrative shares are enabled
(C$, D$, etc.).

If the necessary services are enabled, try the following additional steps to
troubleshoot why the registry may not be accessible:

Please be sure to check the following:

1. Check to see if you have Simple File Sharing enabled on any of the
affected target
machines? <this has sometimes caused a problem since remote access will use
guest
account>

2. On a target machine, check the permissions on the following Registry
key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\SecurePipeServers\winreg

See if this Winreg key has the following permission:
Local System <read>

If the Winreg key on the target does not have Local System <read>
permission, add this and test again.

You can also test permissions on this key using this alternate method: On
the machine running the scan, open REGEDIT and selected „File” > „Connect
network registry…”, provide the machine name or the IP address of the
target machine to be scanned.

Confirm you can open and view all of the nodes of the remote registry,
including

HKEY_CLASSES_ROOT
HKEY_LOCAL_MACHINE
HKEY_USERS

If you have a problem opening any node such as:

Error Opening Key
Cannot open HKEY_LOCAL_MACHINE: Error while opening key.

Ensure that you add „LOCAL SERVICE” with read permission to the following
registry key: HKLM\System\Currentcontrolset\control\securepipese rvers\winreg