Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Troubleshoot "Access Denied" errors in Patch Manager

Troubleshoot "Access Denied" errors in Patch Manager

Created by Interspire Import, last modified by Laura C on Mar 07, 2018

Views: 3,929 Votes: 2 Revisions: 20

Overview

Troubleshoot Access Denied error messages when trying to connect Patch Manager to a remote computer. These errors occur when deploying updates to remote computers or executing other tasks on a remote computer, such as, when opening Computer Explorer.

Environment

All Patch Manager versions

Cause

These errors signify mounting or permissions issues.

Resolution


Notes:

  • Verify that you can ping the remote computer by name from the Patch Manager server.
  • Verify that the account specified in the error is a local administrator on the remote computer.
  • Verify that you can connect to the remote computer's admin$ share with the account specified in the error.


 

  1. Open a command prompt on the Patch Manager server.

     

  2. Run net use z: \\remoteComputer\admin$ /user:domain\username password
    Where:

    remoteComputer is the remote computer's name

    domain is the domain for the account specified in the error

    username is the account specified in the error

    password is the password for the account specified in the error

     

  3. If the command returns the following error: The server is not configured for remote administration, check the following:

    • Make sure that the File and Print Sharing option is enabled on the remote computer by opening port 445 TCP/UDP on the computer's firewall for communication from the Patch Manager server. 

    • Your group policy allows your account to access the computer from the network (open the Group Policy editor and go to Computer configuration > Policies > Windows Settings > Security Settings > user rights assignment > access this computer from the network).

       

  4. If the command returns Error 1326, configure the remote computer to use the Classic sharing and security model:
    1. Open the computer's Local Security Settings.

    2. Expand Local Policies, and then select Security Options.

    3. Select Network access: Sharing and security model for local accounts, and then click Action > Properties.

    4. Select Classic - local users authenticate as themselves from the menu, and then click OK.
       
  5. Rerun the net use command if necessary.

 

 

 

Verify that you can make a WMI connection to the remote computer using wbemtestwbemtest.png

  1. Launch wbemtest.exe from the Patch Manager server using a command prompt or the Run dialog.

     

  2. Click Connect.

     

  3. On the Namespace field, enter \\remoteComputer\root\default wbemtest3.png
    where remoteComputer is the remote computer's name.

     
  4. Enter the credentials for the account specified in the error in the Credentials section.

     

  5. Click Connect.

 

 

 

Troubleshooting the WMI connection to the remote computer:

 

  1. Make sure that the firewall on the remote computer is not blocking the connection:

    1. If permissible, disable the firewall on the remote computer and test the connection again.

    2. Open the ports necessary to establish communication from the Patch Manager server to remote computers.

       

  2. Enable DCOM on the remote computer:

    1. On the remote computer, launch dcomcnfg using a command prompt or the Run dialog.

    2. In the navigation pane, expand Component Services > Computer and then click My Computer.

    3. Click the Action menu, and then select Properties.

    4. Click the Default Properties tab.

    5. Select Enable Distributed COM on this computer if necessary.

    6. Click OK.

       

  3. If the remote computer is running Windows XP, disable the simple file sharing option:

    1. Click Start > My Computer on the remote computer.

    2. Click the Tools menu, and then select Folder Options.

    3. Click View.

    4. Under Advanced settings, clear Use simple file sharing (Recommended) at the bottom of the list.

    5. Click OK.

Last modified

Tags

Classifications

Public