/build/static/layout/Breadcrumb_cap_w.png

Windows is configuring

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

Answers (6)

Posted by: InterneToughGuy 16 years ago
Senior Purple Belt
0
Are you publishing or assigning the MSIs in Group Policy? Also, are these being installed to the computer objects or user objects?
Posted by: JK1150 16 years ago
Senior Yellow Belt
0
They are assigned and to the computers.
Posted by: anonymous_9363 16 years ago
Red Belt
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.
Posted by: Lindeberg IT 16 years ago
Senior Yellow Belt
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)
Posted by: anonymous_9363 16 years ago
Red Belt
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...
Posted by: Lindeberg IT 16 years ago
Senior Yellow Belt
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'.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ