Important Notice: On February 29th, this community will be put into read-only mode. All existing posts will remain but customers will be unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Not Found - Failed to create target directory even after syncing Active Directory.

 I have one new PC deployment that has been driving me nuts!  If I try to push out software to the PC by name, it comes back with the error.  I even manually added PDQ as a local admin on the PC.  I get the verification mark for the PC before deploying showing it is in AD, but it fails almost immediately.  Now, if I deploy to that same PC with the IP address, rather than the name, it goes through without any problem.  Suggestions?

0

Comments

36 comments
Date Votes
  • Official comment

    Hey guys.  This is fixed in a new development build that we can get to you through Support.  Email us there and send us as much information and screenshots of errors you're seeing and we'll get you taken care of.  

  • what happens when you do an nslookup of that machine's hostname from the pdq deploy server? Does it return the IP address that works for the deployment?

    0
  • Yes, that's actually where I pulled the IP address from to try deploying by that. 

    0
  • Failed to create target directory sounds more of a permissions issue.  First check in Preferences -> Background Services and make sure you have current admin credentials entered.  After that check Services.msc and make sure you have current admin credentials entered there and not Local System.  If that all looks ok but you're still having the issue, go back to Services.msc and stop the Deploy service and change it to local system and then select and re-enter your credentials and start the service again.

    0
  • Can you post screenshots of the nslookup and a ping result to the hostname? And perhaps what settings you are using for the deployment. (if you don't have greenshot installed, I recommend it. You can blur confidential info using their edit tool before you post it up)

    0
  • If he can deploy via IP address but not hostname, I'm curious to see if it is permissions related. One would think that both methods would fail if that were the case. But, stranger things have happened in my life!

    0
  • Thanks, Jason.  I thought permissions too until it worked with the IP address.  Everything is set exactly as it is on other computers that are working fine.  I'm wondering if it might be a hiccup in AD.  Perhaps I will try disjoining and rejoining the domain.

    0
  • Do you have a local administrator account configured on that machine? Could you try using that account as the deploy user in PDQ? 

     

    Also, in Powershell run Test-ComputerSecureChannel on that machine. If it returns false, it means their is an issue communicating with AD. running the same command with the -repair switch as well as -credentials and supply domain admin credentials there (just a username, it'll pop a box for the password after you press enter to execute the command) will attempt a repair of the communication and return true if it works. Saves you from having to remove a machine and readd it!

    0
  • Thanks, Stephen.  I will give that a shot.  I should also add, this is the 4th Windows 10 PC I am pushing out, the others went oddly easy.  This one is making me pay for it. 

    0
  • Powershell came back as true, but I went ahead and disjoined and rejoined the domain anyway.  All is well with the world again.  Hard telling exactly what happened, but it is working normally now.  Thanks for your help guys!

    0
  • Glad to hear! It's pretty hard to tell what's going on sometimes. The important thing is it works now.

    0
  • Have the same problem; disjoining and rejoining didn't work. Deploying by IP address works. The strangest thing is that is does create C:\Windows\AdminArsenal\PDQDeployRunner\service-1 when succesfully running, but deploying by DNS only creates the PDQDeployrunner directory, no levels beyond that. Never had this before, is it a PDQ 9 bug?

    0
  • Jason will hit you up off-list. I had the same issue crop up when I moved to 9. he sent me a beta build that resolved the issue.

    0
  • Having the same error, PDQ 9.2.0.0 Pro.

    Sending various deployments to 13 PCs, suddenly one PC no longer works by the PC name, so I switch to IP address. Then 3 PCs more stop working, so I switch to IP address. Then suddenly the first PC no longer works by IP address either -- so I cannot deploy to that PC at all anymore via PDQ.

    0
  • +1 having the same error, changing the targets to IP address instead works OK

    Would be great to get this fixed!

    0
  • +1  -  9.2.0.0 - Just started using PDQ Deploy and this happening on one of my laptops that is a "loaner" with settings wiped out regularly.

    0
  • I'm having this issue and removing and rejoing it to the domain hasn't helped.  The powershell command came back true.  The remote repair shows all green.  I also see the C:\Windows\AdminArsenal\PDQDeployRunner\service-1 directory, but still get this error.  This is a Dell Laptop that I just performed a fresh clean reload of Windows 7 64bit to get an clean environment after a user left.  I am also running 9.2.0.0 Pro.

    0
  • Email support@adminarsenal.com. They'll send you a beta build that fixes this issues. I'm still have some sporadic issues with one of my labs, but on the whole, the beta build has resolved my issues.

    0
  • Same Problem here with Windows10. Running 9.2.0.0. Enterprise.
    Deployment with IP Adress is fine.

    0
  • Jason's suggestion 'check Services.msc and make sure you have current admin credentials entered there' fixed it for me.

     

    I have an AD environment running PDQ Deploy 9 (Release 2) in Enterprise Mode. I was able to deploy to all workstations by hostname until suddenly, one stopped working. For a short time, I was able to deploy using its IP address until that too stopped working. In Services.msc, my admin credentials were entered (I don't recall doing that myself) but I thought reentering the password wouldn't hurt. It fixed the issue for me. I currently have no issues.

     

    Thank you!

    0
  • I have PDQ Deploy 9.2.. I have 10 old laptops from different companies. I freshly installed Windows 10 on 7 PCs, Windows 7 on 3 PCs, nothin else, same user and password on all machines, but no server, no active directory. All 3 PCs with Windows 7 worked succesfully, but only 2 with Windows 10. 5 with Windows 10 failed with the above error. Using the IP address also didn't work.

    0
  • Still seeing this problem occur on some PCs after upgrading PDQ to version 10.1.0.0.

     

    0
  • Hi David,

    This was fixed in the latest release build of Deploy 10 (Release 2) that came out earlier this morning.

    http://support.adminarsenal.com/hc/en-us/articles/224334127-Version-10-Release-2-of-PDQ-Deploy-Released

    0
  • I actually experienced this issue with Deploy 10 (Release 2) but the suggestion of switching the service account to Local System and back to my Deploy user account fixed it for me.

    0
  • Thank you Brian.

    >but the suggestion of switching the service account to Local System and back to my Deploy user account fixed it for me

    Thats the solution for me too.

    0
  • I had the same issue with Deploy 10 Release 2, I tried the suggested workaround above but this did not work. In the end I manually created the "service-1" folder on the remote machine and redeployed the package with the default credentials and then it worked.

    0
  • I have the same issue loading to some of our new Windows 10 machines.  I did notice that the laptop rebooted during the deployment.  I then had to continue using the IP address.

    0
  • same issue here as OP. PDQ deploy 10.2.0.0  installing by computer name doesn't work but by ip address does. I ping the computer from the pdqdeploy machine to get the ip.

    0
  • I had to change the services from my admin account back to local system and back to admin account like mentioned above. Then, my issue with "failed to create" went away. That was a little frustrating, not sure why this happened all of sudden on about 10 domain-joined computers.

    0
  • Hey guys,

    Can't stress this enough but these errors were fixed in newer development builds available from support@adminarsenal.com  Please send us the error you're seeing with your email address and we'll get you taken care of.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post