Blank target installs to local host

Comments

6 comments

  • Emily

    Hi, 

    We have not seen the behavior you are describing, however, we did just release PDQ Deploy 6.2 yesterday that allows importing from Spiceworks 7.4.00065 and later.  We suggest you upgrade to this latest version of PDQ Deploy to see if this corrects the issues you are having.  If that does not fix what you are experiencing we will need to get more information in order to troubleshoot.  What version of Spiceworks are you using?

    Emily

    0
    Comment actions Permalink
  • Infosend Admin

    Hi,

     

    I confirmed this was a bug with PDQ Deploy 6.1.0.0. Upgraded to 6.2.0.0 which was just released, but the issue remains. Spiceworks 7.4.00059. http://support.adminarsenal.com/requests/37777?flash_digest=a9e2237cb19112725561bdf42ac1cb64bc574636

     

    Thanks

    0
    Comment actions Permalink
  • Emily

    Thank you for the update, I will leave this to our Support team to work for you.

    0
    Comment actions Permalink
  • Shane Corellian

    It looks like some of these computers have a null value in the servername field in the Spiceworks database. There appear to be two fields where a computer name can exist. If this is the case then we will grab a value from one of the other field is null.

    There is a second issue that is very disconcerting. This is the behavior that you described which causes a null value to be read as LocalHost. We will try and duplicate this behavior. If we can verify this behavior then we will get it fixed ASAP.

    0
    Comment actions Permalink
  • Infosend Admin

    Hi Shane,

    I can 100% verify that what I was deploying was from the Workstations group, that the local host was not part of that group since it is a server, and that the software being deployed did get installed on the local host then a reboot was initiated, and the package being deployed does not, nor ever has initiated a reboot. Been using PDQ Deploy for 2 years now and it is a great program, so I know it was not an accidental selection on my end.

    I don't want to test even a simply file-copy deploy to the blank target which would in turn install to local host in the off chance that besides it incorrectly installing to local host, it initiates a reboot after the install.

    Thanks

    0
    Comment actions Permalink
  • Jason Hanks

    Just to update this post, there was no response from the customer on the Support Ticket but this has been resolved in the latest release of Deploy 7 that you can download from this link.

    0
    Comment actions Permalink

Please sign in to leave a comment.