When I deploy some MSIs, upon opening the program I get this prompt and it will pull the rest of the MSI from the network. I am using Group Policy Software Deploy, and this prompt causes a lot of problems when the network is slow or for laptops that are off the network. I know this only runs the first time for each user account, but anyone have any tips on how to avoid these or prevent them when I build my MSI packages?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Are you publishing or assigning the MSIs in Group Policy? Also, are these being installed to the computer objects or user objects?
Answered 10/03/2008 by: InterneToughGuy
Senior Purple Belt

Please log in to comment
0
They are assigned and to the computers.
Answered 10/04/2008 by: JK1150
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: JK1150
anyone have any tips on how to avoid these or prevent them when I build my MSI packages?
If you want to avoid deployment to sites with restricted bandwidth and/or laptops, I'd suggest you make your OUs more granular and create the GPO links accordingly.

BTW, this post would probably be better in the 'Deployment' forum.
Answered 10/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Well, to be fair, he did ask specifically for tips on packaging.
From your post i gather your biggest problem lies with the auto-repair of usersettings in a package, so the obvious tip would be to avoid putting usersettings (registry and/or files) in your MSI. A lot of software will work without defining these settings in the MSI, just test this thorougly with different testuseraccounts.

Another tip is to include the usersettings in the main (single) feature of the MSI package. Or you can split the MSI in two separate packages, one for the machinebased install and one for the usersettings (shortcuts, registry etc)
Answered 10/06/2008 by: Lindeberg IT
Senior Yellow Belt

Please log in to comment
0
I thought about that before posting but, logically, either way, the package still has to be deployed and will thus prompt. If the prompt/progress dialog is to be avoided, then the entire deployment has to be avoided. You can't have one without the other. Even if you moved the user-specific stuff to, say, a push via some kind of script, the 'slow network/laptop' issue doesn't go away. Tricky...
Answered 10/06/2008 by: VBScab
Red Belt

Please log in to comment
0
True, true..
Maybe as last resort he could try some kind of local caching of the packaged MSI's. Still, with only AD deployment he would always have problems because of its lack of 'feaures'.
Answered 10/06/2008 by: Lindeberg IT
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity