PDQ access denied to computer's service manager

Comments

10 comments

  • Colby Bouma

    This KB may help. If it doesn't please let me know.

    https://support.pdq.com/hc/en-us/articles/220533627-Windows-Firewall-Ports-and-Exceptions

    1
    Comment actions Permalink
  • Matthew Rowell

    Colby, 

    We are brand-new PDQ customers and are experiencing this same issue with our Windows 10 machines. We have tested using a GPO to modify the Firewall Ports and Exceptions and it is working perfectly for our Windows 7 machines. Unfortunately, applying the same solution, as well as the recommended UAC change, is not working for us. Are there perhaps any additional steps we should look into in order to resolve this Inventory scanning issue?

    0
    Comment actions Permalink
  • Colby Bouma

    Please contact support@pdq.com

    0
    Comment actions Permalink
  • Matthew Rowell

    Thanks, Colby! We actually, accidentally, stumbled upon the resolution no more than an hour ago. All of the documentation we found mentioned restarting the "Background" service. We weren't exactly sure what that was, but then we realized that service was both the PDQ Deploy and PDQ Inventory services on the server that we are using. We rebooted this server and, voila! Problem solved! Thanks again!

    0
    Comment actions Permalink
  • Joey Alain

    I just solved this in a way I hadn't seen mentioned before. In my case, I was using a domain admin on the PDQ server as the background service credential. It was suggested to me by PDQ Support to change the background service to use a local admin account (local to the PDQ server) instead and that immediately fixed the issue. I rescanned and the endpoints were available.

     

    2
    Comment actions Permalink
  • Johnrlevel

    Amazing. This just solved the same issue for me. I've been struggling with it on my secondary domain for months. Thanks!

    0
    Comment actions Permalink
  • Valmik Patel

    I dont know why this worked but this did the trick for me. THANK YOU.

    0
    Comment actions Permalink
  • Christian Eder

    worked also for me!!! THANKS!!

    it has to be a local user with admin rights (no default domain user with local admin rights).

    0
    Comment actions Permalink
  • Andy Langton

    Amazing, this worked for me as well, however I would still really like some resolution here.  How come a domain account which is local admin on the PDQ server gives this error, but when I use a local account which is local admin on the PDQ server, it functions correctly?

    0
    Comment actions Permalink
  • Jean Davis

    Joey, the bomb! That was our problem, all the domain controllers and a few others here and there were having the problems. Change the service to run as a local admin and all work now.

    0
    Comment actions Permalink

Please sign in to leave a comment.