Hi All,

I'm trying to get a picture of what components you typicaly include in your base build - starting with a clean XP SP3 install. I'm not concerned with the base applications (Adobe Reader, Office, AV etc) but pretty much everything else you include. I have the following list:

Latest .Net Framework version
Visual C++ 2005 Redistributable
Visual C++ 2008 Redistributable
MSXML 6.0 (I know this is included with XP SP3)
Latest Java Runtime version
Any required Jinitiator versions
Latest Flash Player
Latest Shockware Player

You could argue the list is subjective but I'd say these are pretty common.

Any comments / additions?

Cheers,
Rob.
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
Presumably you mean for client PC build, rather than a packaging box.

If so, InstallShield drivers/engines up to 12 sprint to mind...
Answered 06/03/2009 by: VBScab
Red Belt

Please log in to comment
0
Yes Client build - sorry should have been more specific. Then again anyone with this stuff on their packaging build should be certified [;)]

Good shout about the InstallShield engines though...
Answered 06/03/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Hi,
Latest Shockware Player

But I don't have this on my PC and it is only on the Shockwave testing site that I got a message. My autoplay CDs just use html etc.

I really don't see this plugin around me.
Answered 06/03/2009 by: dvdzonenz
Purple Belt

Please log in to comment
0
Rob,

I typically don't include Java or the Adobe flash/shockwave products in the image file since they change every other months, lol. Usually just have a post deployment script that lets me quickly update those applications. I tend to only include apps that are too large to effeciently install post deployment and those that hardly ever get updates.

Looks like you've pretty much got the pieces of a vanilla image along with VBS iss engine. Seems like you'll be reaching into client specific apps at that point.

Cheers,
Jay
Answered 06/03/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
0
I do not include any applications in our base installs except for specific MS components and updates. All other applications are deployed afterward through Zenworks. This allows for a single clean base to deploy to all desktops and portables.
Answered 06/04/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
I keep my base image as clean possible. Only Windows Updates and .NET.
Answered 06/04/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
Thanks for the responses, i'm not trying to say you should have a thick or thin base image as there are arguements for and against.

Just trying to compile a list of components (over and above the OS and patches) which go to all machines by default. Wheather they in the base image, post build scripts or delivered by SMS, zenworks or whatever is up to you.

Thanks,
Rob.
Answered 06/04/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
VB runtimes 3 to 6?
Answered 06/04/2009 by: VBScab
Red Belt

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