How To Troubleshoot Windows Access Errors In Device ManageR For Windows Log Off, Reboot, and Shutdown Actions

If you experience ‘access denied’ or other access errors when using the Windows Plugin Bundle in Device ManageR, please see the recommendations and troubleshooting steps below:

Recommendations for user credentials

Troubleshooting access denied errors

Recommendations for user credentials

When a remote computer attempts to shut down, reboot or log off a target Windows system, it must provide user credentials to the target computer. Below are recommendations about what those credentials should be and where you should enter them:

On networks with domains

– Enter the username and password for a domain admin into the Windows action you create in Device ManageR. See this FAQ for instructions on creating Windows actions: How To Configure A Windows Plugin Bundle Action In Device ManageR.

– Typically, you’ll also need to enter those same credentials into the Device ManageR service to run it as an administrator. This FAQ shows you how: How To Run AVTECH’s Device ManageR As An Administrator In Windows.

On networks without domains

Configure the same username and password in 4 places: in an administrator account on Device ManageR’s host system, in the Device ManageR action, in the Device ManageR service and in an administrator account on the target computer. (In our example, the username is ‘DeviceManageR.’)

On Device ManageR’s host system

1. Create an administrator user account that’s specifically for Device ManageR.

2. Enter the same user credentials into the Windows action you create in Device ManageR. See this FAQ for instructions on creating Windows actions: How To Configure A Windows Plugin Bundle Action In Device ManageR.

3. Enter the same credentials into the Device ManageR service to run it as an administrator. This FAQ shows you how: How To Run AVTECH’s Device ManageR As An Administrator In Windows.

On the target computer

4. Use the same credentials to create an administrator user account that’s specifically for Device ManageR to access the system.

Troubleshooting ‘access denied’ errors

Manually testing Device ManageR’s host system

If you get an ‘access denied’ error when attempting to shutdown, log off or reboot a Windows system from Device ManageR, first manually test whether Device ManageR’s host system can shutdown the target computer; then, if it can, run Device ManageR as an administrator with the host system’s username and password.

Step 1: Test the remote shutdown capability of Device ManageR’s host system

To check whether the computer that Device ManageR is installed on can shutdown the target computer, follow these steps:

1. Log on to Device ManageR’s host system with an administrator account.

2. Open Windows Command Prompt. You may find it at the following path:

Windows 7 & 8

Start → All Programs → Accessories → Command Prompt

Windows 10

Start → All Apps → Windows System → Command Prompt

3. At the prompt, enter the following command and then press Enter on your keyboard:

shutdown /i

4. When the Remote Shutdown Dialog box appears, enter the following:

a. In Computers, select Add.

b. In the Add Computers dialog box:

– Enter the IP address or the computer name of the target system. In our example, we’ve entered the IP address.

– Then select OK.

c. In What do you want these computers to do, select either Restart or Shutdown from the drop-down menu. In our example, we’ve chosen Shutdown.

d. You may leave the rest of the settings at defaults or reconfigure them as you like.

– Note, however, that the default reason for Shutdown—Other (Planned)—requires you to fill in the Comment field. We’ve entered ‘Testing whether remote shutdown works from Device ManageR’s host system.’

e. Select OK to initiate the remote shutdown.

Once you select OK, the target computer will (or will not) shutdown/restart.

Step 2: Run Device ManageR as an administrator

Once you’ve determined that Device ManageR’s host system has the ability to shutdown the other computer, give Device ManageR the administrator credentials you logged into Windows with.

This FAQ shows you how: How To Run AVTECH’s Device ManageR As An Administrator In Windows.

Checking your security software settings

You may also need to check security software settings on the target system and Device ManageR’s host system:

– Ensure that local anti-spyware and anti-virus programs on both the target computer and Device ManageR’s host system allow WMI connections.

– Ensure that the firewall on the target system allows incoming remote WMI connections.