Access denied to PDQ Deploy background service
We are running PDQ Deploy Enterprise, we have licences covering two administrators at the same time. However, when I or my colleague try and log in whilst the other is using PDQ Deploy we get the following error:
In this case If I switch to local mode, I can put in my own credentials and log in, but if I do the application stops briefly and my colleague is kicked out. I am a domain administrator and have full control over the server pdq is running on, same goes for my colleague.
There are a couple of non-domain admins who use PDQ Deploy, this doesn't happen when either of them are logged in, only when my fellow domain admin is using PDQ deploy.
Can anyone help please? Thanks!
-
So I've been doing some digging, and I think I may have found a reason. The PDQ Deploy service on the server isn't running as a service account, but with my colleague's credentials. I'm guessing he did that because then the PDQ Service would have domain admin rights and can deploy to any machine? That colleague is uncontactable at the moment so I cannot just ask him.
I am new to PDQ, so would this be the reason for not using the Local System account? What are the repercussions of setting the service to log on as a Local System account please?
-
Thankfully I've found the source of the problem on my own. I will record it here to help anyone else who has the same issue, as PDQ's help on the background service doesn't help much at all, and I've had zero responses from here, so hopefully this information will come up if anyone has the same issue.
I didn't work for my company before PDQ was set up, and I have never dealt with it before, so this wasn't straightforward without any prior knowledge of PDQ or the local environment.
SOLUTION:
Anyway, this problem was being caused by myself and my colleague (the other domain administrator) not being in the console users list. Once I'd added us both in, I set the background service to use a local service account and now we can both log in at the same time. It was literally that simple, but having no prior knowledge of PDQ and how it was set up at my workplace, made this very simple issue take a while for me to discover without any help.
Please sign in to leave a comment.
Comments
4 comments