Troubleshooting access denied errors<\/a><\/p>\n When a remote computer attempts to shut down, reboot or log off a target\u00a0Windows 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:<\/p>\n – Enter the username and password for a domain admin into the Windows action you create in Device ManageR.\u00a0See this FAQ for instructions on creating Windows actions: How To Configure A Windows Plugin Bundle Action In Device ManageR<\/a>.<\/p>\n – Typically, you’ll also\u00a0need 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<\/a>.<\/p>\n Configure\u00a0the 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.’)<\/p>\n 1. Create an administrator user account that’s specifically for Device ManageR.<\/p>\n 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<\/a>.<\/p>\n 3. Enter the same credentials into the Device ManageR service to run it as an administrator.\u00a0This FAQ shows you how: How To Run AVTECH’s Device ManageR As An Administrator In Windows<\/a>.<\/p>\n 4. Use the same credentials to create\u00a0an administrator user account that’s specifically for Device ManageR to access the system.<\/p>\n If you get an ‘access denied’ error when attempting to shutdown, log off or reboot a Windows system from Device ManageR, first manually test\u00a0whether 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.<\/p>\n To check whether the computer that Device ManageR is installed on can shutdown the target computer, follow these steps:<\/p>\n 1. Log on to Device ManageR’s host system with an administrator account.<\/p>\n 2. Open Windows Command Prompt.\u00a0You may find it\u00a0at the following path:<\/p>\n Windows 7 & 8<\/em><\/p>\n Start<\/strong> \u2192 All Programs<\/strong> \u2192 Accessories<\/strong> \u2192 Command Prompt<\/strong><\/p>\n Windows 10<\/em><\/p>\n Start<\/strong> \u2192 All Apps<\/strong> \u2192 Windows System<\/strong> \u2192 Command Prompt<\/strong><\/p>\n 3. At the prompt, enter the following command and then press Enter on your keyboard:<\/p>\n shutdown \/i<\/p>\n 4. When the\u00a0Remote Shutdown Dialog<\/em> box\u00a0appears, enter the following:<\/p>\n a. In Computers<\/em>,\u00a0select Add.<\/strong><\/p>\n b. In\u00a0the\u00a0Add Computers<\/em> dialog box:<\/p>\n – Enter the IP address or the computer name of the target\u00a0system. In our example, we’ve entered the IP address.<\/p>\n – Then select OK<\/strong>.<\/p>\n c. In What do you want these computers to do<\/em>, select either Restart<\/strong> or Shutdown<\/strong> from the drop-down menu. In our example, we’ve chosen Shutdown<\/strong>.<\/p>\n d. You may leave the rest of the settings at defaults\u00a0or reconfigure them as you like.<\/p>\n – Note, however, that the default reason for Shutdown\u2014Other (Planned)<\/em>\u2014requires you to fill in the Comment<\/em> field. We’ve entered ‘Testing whether remote shutdown works from Device ManageR’s host system.’<\/p>\n e. Select OK<\/strong> to\u00a0initiate the remote shutdown.<\/p>\n Once you select OK<\/strong>, the target computer will (or will not) shutdown\/restart.<\/p>\n<\/a>Recommendations\u00a0for user credentials<\/h3>\n
On networks with domains<\/h4>\n
![](\"http:\/\/avtech.com\/articles\/wp-content\/uploads\/2017\/01\/ADM_Windows_Shutdown_Action_Credentials_DomainAdmin.png\")
<\/a><\/p>\n![](\"http:\/\/avtech.com\/articles\/wp-content\/uploads\/2017\/01\/ADM_Service_Properties_LogOn_DomainAdmin.png\")
<\/a><\/p>\nOn networks without domains<\/h4>\n
On\u00a0Device ManageR’s host system<\/strong><\/h5>\n
![](\"http:\/\/avtech.com\/articles\/wp-content\/uploads\/2017\/01\/Windows_Settings_ADM_Admin_Account_ADM.png\")
<\/a><\/p>\n![](\"http:\/\/avtech.com\/articles\/wp-content\/uploads\/2017\/01\/ADM_Windows_Shutdown_Action_Credentials_ADM.png\")
<\/a><\/p>\n![](\"http:\/\/avtech.com\/articles\/wp-content\/uploads\/2017\/01\/ADM_Service_Properties_LogOn_ADM.png\")
<\/a><\/p>\nOn the target computer<\/strong><\/h5>\n
<\/a><\/p>\n<\/a>Troubleshooting ‘access denied’ errors<\/h3>\n
Manually testing Device ManageR’s host system<\/h4>\n
Step 1: Test the\u00a0remote shutdown capability of Device ManageR’s host system<\/strong><\/h5>\n
![](\"http:\/\/avtech.com\/articles\/wp-content\/uploads\/2017\/01\/Windows_Command_Prompt_Remote_Shutdown_Dialog.png\")
<\/a><\/p>\n