Wednesday 21 August 2013

GPO Software Deployment with DFS Shares Failing [Solved]

Applies to: Microsoft Server 2008R2, 2012


Deploying out software using group policy fails on client because it doesn't have the correct permissions to the DFS Share Source.

Fixes you've probably tried

You've given full everybody permissions to all shares in relation to where you store your MSIs.

You've played with the controls in DFS and both on the root files on your data drive.

You've tested the install when logged in and it works, yet the it still doesn't deploy out via GPO automatically

You've googled endlessly and everyone has different solutions to the problem and yet none apply to you.

You've considered throwing yourself off a bridge knowing that the only fix you can find is to specify the actual server path, making DFS pointless.

The Actual Fix

The cause is normally a combination of Windows Firewall and indeed the permissions on the DFS Share.

Windows firewall in its on state will not recognise your namespace as a safe destination and prevent your computer access to it, quick fix is to turn it off and give it a try. 

Never do both fixes without testing one before applying the other, don't want to over fix it.

If it still doesn't work.

Open up DFS Management

  1. Click on the Namespace and expand it.
  2. Click on the folder you use for your MSIs.
  3. On the LEFT hand pane still, right click and choose properties.  Do not choose properties from the central pane in the DFS manager.
  4. Click on the Advanced Tab
  5. Click Set Explicit view permissions on the DFS Share
  6. Click on configure view permissions
  7. Set Read Permissions to Authenticated Users and SYSTEM.
  8. Press Ok and give it another go.
Hopefully this works for you happily, if it does please say thank you.

After endless googling this resolution has never been published in this way before, need to bump this topic upwards to save the headaches of all technicians that have had this problem.

Thanks for reading,

1 comment:

  1. 2 years i've had this issue and only now someone posts the fix. Brilliant. Thank you.


Please enter your comment here, all comments are subject to moderation