List
of trouble shooting tips related to OpManager MSP Remote Control.
·
- Error
while pushing file to remote machine – Bad username /
password
- Error
while pushing files to the remote machine -0xC0000192
- Unable
to install agent in the remote machine - RPC server is unavailable
- Unable
to install agent in the remote machine - Access Denied
- Agent
installed successfully but device missing from Admin->Device List.
- WMI Script thread not responding..Hence quitting the thread.Waiting to install
Error
while pushing file to remote
machine - Bad username /password
- Username
and password supplied for the device could be incorrect.
- If
password is correct, check the following
- If
the device is in a domain environment, ensure that username is supplied
in this format username = domain\username.
- If
the device is in a workgroup, ensure that username = username.
Error
while pushing files to the
remote machine -0xC0000192
- Ensure
that Netlogon and Computer Browser
service is started in the remote machine.
- Select
Start > Run
- Type
'services.msc' in the text box and click OK
- In
the listed services, see if the status of Netlogon and Computer Browser service is shown as
started.
- Start
the service if it is not started.
Unable
to install agent in the
remote machine - RPC server is unavailable
- Ensure
that the Remote
Procedure Call(RPC) and Windows
Management Instrumentation(WMI) Services are running
- Select
Start > Run
- Type
'services.msc' in the text box and click OK
- In
the listed services, see if the status of RPC and WMI services are
shown as started.
- Start
the services if it is not started.
- Check
if firewall is configured on the remote computer. If yes, enable Remote
Administration.
- Click
Start, click Run, type gpedit.msc, and then click OK.
- Under
Console Root, expand Computer Configuration, expand Administrative
Templates, expand Network, expand Network Connections, expand Windows
Firewall, and then click Domain Profile.
- Right-click
Windows Firewall: Allow remote administration exception, and then click
Properties.
- Click
Enabled, and then click OK.
- A
firewall might be blocking the WMI traffic. Give access to WMI traffic
in the firewall. You will need to open the ports 445,135 in the
firewall.
Unable
to install agent in the
remote machine - Access Denied
- Check
if 'Remote DCOM' is enabled in the monitored workstation. If it is not
enabled, enable it as follows:
- Select
Start > Run
- Type
dcomcnfg
in the text box and click OK
- Choose
component services->computers->My Computer. Right click and
choose Properties
- Select
the Default Properties tab
- Select
the Enable Distributed COM in this machine checkbox
- Click
OK
- Local
Security Policy allows only guest access
- Go
to Administrative Tools -->Local Security Policy Select Security settings-Local Policies-Security
Options
- From
the options on the right, select Network access: Sharing and security
model for local accounts
- Right-click
and select Properties
- Change
the privilege from Guest to Classic.
- If
the user name provided does not have sufficient access privileges to
perform the operation.
- It
is possible that this user does not belong to the Administrator group
for this host machine.
- Try
moving the user to the Administrator Group of the workstation.
- Try
with an administrator (preferably a Domain Administrator) account.
- If
the probe is running a service try the following steps
- Go
to Windows Service UI.
- Open
"Properties" dialog of the "ManageEngine OpManager Probe" service
- Go
to "Log On" tab
- In
the "Log on as" option select "This Account" and enter domain
name\username and password, which has rights to access WMI data.
- Save
and restart probe service
While
installing the agent,
OpManager MSP displays the result as “agent successfully installed and
started”.
But the remote device does not appear in the Admin->Remote
Control-> Device
list
- Check whether the following ports are opened in the central server
- Possible
reason could be the service was not successfully started due to
presence of a file called "Program"
in C drive. Delete the file and try to install the agent again.
- check whether the remote machine has dual ip address.if so there is a possibility that the remote agent returns an ip address diffrent from the one discovered by opmanager.In such cases the device will not be visible in the list.As a workaround please edit the ipaddress in the device snapshot page and provide the other ip address of the device
WMI Script thread not responding..Hence quitting the thread.Waiting to install
- check the remotecontrol already installed in the corresponding system and uninstall the remotecontrol service completely from the system
- download remotecontrol.exe from Central-Admin-Remotecontrol and uninstall the remotecontrol service by running the exe file
