by RogueSpear » Wed Jan 30, 2008 7:47 pm
This is one of the "problems" with GPO deployment in general and this installer in particular. So long as you're connected to the network the first time the OS needs to invoke msiexec, you're all set. This happens to me with a good number of installer when they are deployed via GPO and they're a full file .msi vs. an AIP.
It's nothing much to worry about, and even if it were, there wouldn't be anything I could do about it. I suppose you could attempt to convert all of your full file .msi files into AIPs and attempt to deploy those, but realistically speaking if you want the benefit and convenience of managing your applications network wide this is about the best you're going to get.