Access denied with PDQ Deploy 2.1.1.0

Comments

7 comments

  • SelfMan

    do you have the same account on the computer nad the NAS? Is this a Domain network?

    0
    Comment actions Permalink
  • Luca Cortese

    Yes, it's a domain network and the username is known from a NAS point of view, but doesn't have "execute" privileges

    0
    Comment actions Permalink
  • SelfMan

    Just teoretically, could it be that it som hidden issue of the NAS? Try to create a shared folder on a computer and deploy from that.

    0
    Comment actions Permalink
  • Luca Cortese

    Thanks for the help, SelfMan. I've tried saving the msi to a proper shared folder hosted in a server and it works. THe only difference I can see is that, in this last case, the deployment user had full privileges on the file. The strange thing is that it used to work smoothly before updating PDQ Deploy to 2.1.1

    0
    Comment actions Permalink
  • Adam Ruth

    Luca,

    See if the Log On of the PDQDeploy service has changed to Local System (use the Windows services control panel).  If it has you can fix it by stopping the service and then starting the PDQ Deploy console. We've had a couple reports of this happening and have implemented a fix for the next update.  

    0
    Comment actions Permalink
  • Luca Cortese

    Thanks Adam, that was exactly what happened. After switching back to a network account, everything worked again. Thank you for the support!

    0
    Comment actions Permalink
  • Jens Lindgren

    Had the same issue, it had to do with a change of password and the need to restart the background service once the password was corrected in credentials.

    0
    Comment actions Permalink

Please sign in to leave a comment.