DFS Share for Deploy - Copy Pull Failure

Comments

7 comments

  • Mike Kercher

    I would look at a couple of things.  One being DFS referrals.  Are your Active Directory Sites/subnets configured properly?  Are your successful deployments on a particular subnet and failures on a different subnet? (I'm the guy you wanted to pick their brain on the live feed last week).

     

    0
    Comment actions Permalink
  • Brad Barfoot

    AD sites and subnets are fine.

    As for the failures and success, one site has both: Citrix Workspace update package was sucsessful, but the Chrome update package failed on the same device.

    I've only enabled the new schedules on three sites at this point.

    0
    Comment actions Permalink
  • Mike Kercher

    Take a look at the namespace referrals and see if you are excluding targets outside of client's site.  On a test machine, you should be able to browse the DFS share (e.g. \\contoso.com\repo) and see the entire folder structure.

     

    You can also look at the properties on a DFS folder, click the DFS tab and see which DFS server is active.

     

    0
    Comment actions Permalink
  • Brad Barfoot

    I can browse to the DFS share, set the problem site as active, and still see all the package files and be able to copy them under the deploy user login.

    As for referrals, nothing is changed from default:

    0
    Comment actions Permalink
  • Brad Barfoot

    Just for clarification, I'm trying to deploy the pre-built app packages.. not custom created.

    0
    Comment actions Permalink
  • Colby Bouma

    If you click the blue ? next to the "Pull copy failure" message, then "Submit this issue to PDQ Support", it will bring up a detailed error message.

    If you're willing to share it, make sure to look through it for any information you may want to redact, such as usernames. I recommend using the "Code block" button in this editor to format it.

    0
    Comment actions Permalink
  • Brad Barfoot

    Turns out it wasnt a PDQ issue after all.... deeper investigation revealed it was a DFS replication issue. Once I took care of that, deployments began working.

    Thanks to all 

    0
    Comment actions Permalink

Please sign in to leave a comment.