I have a strange issue going on in my environment that has me beating my head against the wall.
Windows 2003 Domain - 3 2003 Domain controllers running DNS & WINS.
DFS Root - 3 domain controllers all as root replicas
DFS Target - 1 2003 Windows server hosting all software to be deployed
Affected Clients - any OS I've deployed software to - XP, 7, 2003, 2008
Software installation has worked fine, but stopped working abruptly in the past week or so.
The error in the logs of the clients who fail to install the software is event ID 105: the install of %software% from policy %GPO-NAME% failed - the error was %1612. This indicates that the share is unavailable for whatever reason. I can login to the machine and access the share fine. We also have other DFS targets that appear to be working correctly for our User home directories and other shared files for the orginization.
I do not think it is permissions on the shares/ntfs, but as a troubleshooting step I added everyone full control to the share and NTFS permissions. This caused no change in the problem.
I think the problem is DFS related because I created a new test GPO and pushed some software from it using the straight UNC path to the share on the server (\\server\sjare) and the software installed correctly.
Does anyone have any ideas for me to start looking at? I am majorly confused because the DFS environment seems to be working correctly since we have 8 total DFS targets on this single root and they all work correctly.
I have used PSEXEC to open a remote command prompt as SYSTEM from a problematic computer to the share via DFS name and I get access denied. This tells me that is my problem, but I don't know how to manipulate the permissions to be correct in this instance, nor do I understand why I would need to do that. It has worked in the past with no problems. There were no changes to the permissions (to my knowledge).
From the command prompt as SYSTEM, I can start an install of any of the software on the share using msiexec /i \\server\share\software\installer.msi - but not using the DFS path.
I don't think this is a permissions problem, rather a DFS problem.
Can anyone lend a hand here? I would be most grateful. Thank you!