Users Guide

Troubleshooting

Unable to remotely connect to Windows Management

Instrumentation

If Common Information Model (CIM) information for a remote client computer system is not available to

the management application or if a remote BIOS update that uses Distributed Component Object Model

(DCOM) fails, the following error messages are displayed:

• Access Denied

• Win32:RPC server is unavailable

1. Verify that the client system is connected to the network. Type the following in the command

prompt of the server:

ping <Host Name or IP Address> and press <Enter>.

2. Perform the following step if both the server and the client system are in the same domain:

• Verify that the domain administrator account has Administrator privileges for both systems.

Perform the following step if both the server and the client system are in a workgroup (not in the

same domain):

• Make sure that the server is running on the latest Windows Server.

NOTE: Back up your system data files before changing the registry. Editing the registry

incorrectly may render your operating system unusable.

3. Edit the registry change on the client system. Click Start → Run, then type regedit, and then click

OK. In the Registry Editor window, browse to My Computer\HKEY_LOCAL_MACHINE\SYSTEM

\CurrentControlSet\Control\Lsa.

4. Set the forceguest value to 0 (default value is 1). Unless you modify this value, the user remotely

connecting to the system will have guest privileges, even if the supplied credentials provide

Administrator privileges.

a. Create an account on the client system with the same user name and password, as an

administrator account on the system running the WMI management application.

b. If you are using IT Assistant, run the IT Assistant ConfigServices utility (configservices.exe in

the/bin directory under the IT Assistant installation directory). Configure IT Assistant to run under

a local administrator account, which is also now an administrator on the remote client. Also,

verify that DCOM and CIM are enabled.

c. If you are using IT Assistant, use the administrator account to configure subnet discovery for the

client system. Enter the user name as <client machine name>\<account name>. If the system has

already been discovered, remove the system from the list of discovered systems, configure

subnet discovery for it, and then rediscover it.