Help Center

Follow

File Access Authorization

Purpose:
You receive an error indicating access has been denied to a file or directory.

Resolution:
This error can occur if the user is not a member of the Administrators group or a file is in use by another process and cannot be accessed. If the source file resides on a network share, it is possible that the deployment user does not have permissions to access the remote share.

Ensure that the user account being used is an administrator on the target computer. The target computer may also need to be rebooted to clear up any file locks.

Access to the local ADMIN$ share might also be an issue, especially on computers not joined to a domain. For guidance on how to remedy ADMIN$ share access issues, please see, Can't Access ADMIN$ Share Using a Local User Account.

If the error message points to a remote share (e.g. Access Denied - Failed to copy directory to target. Access to the path '\\Scranton\Deploy\Techsmith\Snagit' is denied.) then verify that the deployment user has access to the remote files.

See Also:
Under The Hood: How PDQ Deploy Installs Software To Remote Computers
Can't Access ADMIN$ Share Using a Local User Account

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

16 Comments

  • 0

    Hi,

    I get a message saying:

    Access Denied - failed to create lock file on target.

    Access to the path "\xxx.xxx.xxx.xxx\ADMIN$\PDQDeployRunner\service-1.lock" is denied.

    The account I am using is already part of the local admin group of the PC.

  • 0

    This error can mean that something is blocking access to the file such as anti-virus software.  You can try to create the file manually (just and empty text file would do) and see if perhaps something like anti-virus is getting in the way.

  • 0

    I tried to create a file or folder but it says access denied. I'll check the antivirus if its blocking it. Is there any possible reason why?

  • 0

    It could be locking the file in order to scan it, that would be my first guess.  It may be a problem in the software's disk driver locking the file when it doesn't need to.  Depending on the software there may be a way to exclude a directory from scanning.

  • 0

    Hi Adam Ruth,

    I have a question and hopefully you can help me.

    I'm trying to pass an exe to another desktop but its always failed and here are the error.

     

    Thank you.

  • 0

    The first is to try with this type of error is to open the ADMIN$ share using Windows Explorer and the same credentials used for the deployment.  This will help narrow down whether the issue is with the share, with the credentials, with some conflicting software (such as anti-virus) or with the way that PDQ Deploy is connecting.  

    If you can connect with Windows Explorer then it's time to dig deeper and you can submit the error to support with the link under the "More Actions" section in the window (this will include some diagnostic information that might be helpful).

  • 0

    Hi Adam Ruth,

    I have a question, regards to the PDQ Deploy:

    1. If it is possible for PDQ Deploy to install software or pass an exe to another desktop which is the desktop is in the another place.

    2. If its possible for PDQ Deploy to pass only a file not exe?

    Thank you for the reply.

  • 0

    PDQ Deploy can be used to run a batch file on the target computer, which will be able to copy files to or do a number of different tasks.  For example see here:   http://support.adminarsenal.com/entries/21514081

  • 0

    Im planning to create a vbscript that would copy the installer to the local PC on a different folder location and run the installer via script.Will PDQ Deploy execute scripts? Will this work?

  • 0

    It should work fine.  The main thing to keep in mind is to ensure that the script and installer doesn't have an interface that waits for user input, including clicking an OK button, or the script will hang waiting for input that won't come.  Otherwise, you should be good to go.  There are some considerations that you may need to take into account since the script is running from within a service, but they're not very common and we should be able to help if you get stuck with any of them.

  • 0

    That's great! I'll just post comment if I get any issues. Thanks for your help!

  • 0

    I would like to chip in, that if the target is a Windows server 2012 or 2012 R2 or Windows 8. AND it is NOT a member of a doamin. You might want to set this regestry setting (on the target):

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system]

    "LocalAccountTokenFilterPolicy"=dword:00000001

     

     

  • 0

    1) Verify user is part of LocalAdmins.

    2) Turn off User access control. 

    3) Turn on File and Printer sharing.

  • 0

    Thank you DoesNotCompute!

    This worked for Windows 10 PCs not joined to the domain.

     

  • 0

    Thank you DoesNotCompute!.

    This little trick did it for me on Windows 10 not member of a domain.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system]

    "LocalAccountTokenFilterPolicy"=dword:00000001

     

     

  • 0

    Thank you DoesNotCompute!.

    This was exactly what I was looking for. Windows 10 Home machine not connected to the domain.

Article is closed for comments.
Powered by Zendesk