Repository directory is missing
Well, I recently got a prompt to upgrade my version of PDQ Deploy and now after upgrading it is not working properly. I am getting a prompt at EVERY start of the application with a window into my "preferences" settings with a complaint about the "Repository directory is missing" although it does.
Ironically all my deployments are working after I click CLOSE on the dialog so I do not actually change anything or do anything, so technically it is still working as-is but it is VERY ANNOYING that every time I start up the application I keep getting this popup about my repository directory. I can ping the server. I can view the share through networking place. I can even browse the location through PDQ Deploy. But for some reason, the application complains at every startup so please turn this OFF...
I am attaching a screenshot with all the proof... :P
The repository directory needs to be visible to the background service and it sounds like the credentials used by the background service have been reset to "Local System" so that it's not able to see the share. We've seen this happen a few times with the latest version when upgrading and we've got a fix for it in the next update to restore the credentials to the proper user. You can check to see if that's the issue you're having by checking the "Log on" for the PDQDeploy service using the Windows services control panel. If that's the issue, switch the Log on back to your background service user and you should be fine.
Ok, cool beans.
I was checking the CREDENTIALS settings and that was set to an admin user, but I guess that is for deployments and not the service itself so I never thought to check the Windows Services MSC. I guess the upgrade did change this, because it has been changed to the "Local System" account under the "Log On" tab, so now I changed it back to the admin account.
Thanks and hope the new updates leave this alone during upgrade.
You were correct in thinking that Preferences -> Background Service shows the credentials for the service itself but what it's actually showing is what PDQ Deploy thinks the service *should* be set to not what it actually is. PDQ Deploy is supposed to change the service if the credentials are different, but the latest version has a bug in it where this doesn't always work so that the Preferences just cluelessly reports the wrong information.
Unfortunately, as you found out, when this happens PDQ Deploy seems to *almost* work correctly and doesn't give any help as to what's wrong. Sorry about the frustration, I know how annoying it can be.
Please sign in to leave a comment.