<p>Man, I can hardly imagine how many things in your environment must be broken if remote WMI can’t be used, even from domain controllers, SCCM servers, etc. Sounds painful. But anyway,</p>
<p>According to this article:</p>
<p><a href="http://technet.microsoft.com/en-us/library/cc782152(v=WS.10).aspx">http://technet.microsoft.com/en-us/library/cc782152(v=WS.10).aspx</a></p>
<p>No it doesn’t rely on WMI. As long as the Group Policy client can access Sysvol, and access the software distribution point (which may or may not also be in Sysvol,) and the Windows Installer is in good working order on le client, that’ll do. Also notez que software deployment doesn’t work over a slow link - so assurez-vous a fast link was detected.</p>
<p>Modification : Also check this question for some other basic tips for troubleshooting software deployment failures:</p>
<p><a href="https://serverfault.com/questions/345395/deploying-msi-application-through-gpo-doesnt-work">Deploying .msi application through GPO doesn’t work</a></p>
<p>Oh, and finally… try turning off your AV and see if it works then. Then you’ll know if your AV is breaking it or not.</p>
