That is what I'm thinking. Interesting point though, is that this occurs on clients that are local and not optimizing, supposedly. This is an occassional issue so I'm going to have fun catching this. Supposedly, this occurs about 50% of the time on Mobile Client laptops. :confused:
Could the mobile client optimisation of CIFS or HTTP prevent some of the MSI process from completing successfully? Might be interesting to get some packet captures during a failure.
I've submitted a case regarding this. Am working to see about disabling the client anytime an application has to get installed, including Mobile Client upgrades, either by group policy or updating the user_config.xml file
Has anyone seen an issue where you have to disable the Mobile Client in order for application MSIs to download and run. Our system administrators indicate that they have had to disable the mobile client for applications to be successfully loaded. No specific application, no repeatablility. We use Windows Installer 3.1. The issue seems to be occurring on Mobile Client versions 2.0.1.103 and 3.0.0. It also seems to be occurring both locally and remote.
