KACE Product Support

If the MSI file is on a share that replicates like a DFS or the Netlogon folder some client may have issues because they are trying to lock the file when replication does not allow this.  You can reboot a client and look in the Event viewer for these GPO and installation events.  The event will mention that it could not find or access the file.

One of the ways to avoid this is put it on a non-dfs server share that allows access to Everyone.  Remember, the GPO install will run as the local computer account, not a domain user or anyone individual.  The draw back of this is when you are on a WAN and want to deploy from a single GPO.

At one point I worked around this by utilizing a GPO that had a startup script (Not user logon script).  I created a script that checked the registry key to see if the package was installed and if it was not it would copy the package down to the %TEMP% folder (Windows\Temp) and run the MSI silently.

-------------------

@Echo Off

REM check for the existence of some registry key.  If it is there go to All_Set

reg query HKLM\some\registry\key && goto All_Set || goto Install_This

:Install_This

REM Copy the file down to temp and run. Send N to the copy command if the file exists

echo n| copy %logonserver%\netlogon\mymsi.msi %TEMP%  

REM Run the command silently

msiexec.exe /i %TEMP%\mymsi.msi /qn /noreboot

:All_Set