Hey guys,

I've been asked here at work to write a guide entitled "PACKAGING GUIDELINES FOR MACHINE AND OS INDEPENDENCY"

Basically the idea is to put down some guidelines on how to make sure you make clean, non-interfering packages that won't cause blue screens when you (un)ininstall them and won't need a redesign when some server name changes. You know, for posterity aka the guys that'll still be here after my escape ...

I made my "coat-rack" for this thing (I hope this term translates into english OK) and this would be it:



INTRO


REPACKAGING USING SNAPSHOTS

SNAPSHOTTING METHODOLOGY

FILE CLEANUP

REGISTRY CLEANUP

HARD-CODED PATHS / USING PROPERTIES

MERGE MODULES


VENDOR MSI'S - BEST PRACTICES

BASIC RULES

INSTALL TAILORING

MST'S

CUSTOM ACTIONS

MSI EXECUTION SEQUENCES

CUSTOM ACTION TYPES

POTENTIAL PITFALLS


WINDOWS XP VS. WINDOWS 2000 ENVIRONMENTS

CUSTOM ACTIONS AND WMI

INSTALLER VERSION

PREREQUISITES AND COMPLIANCE


PACKAGE DEPLOYMENT

PACKAGE SECURITY

USER SETTINGS

MSI SELF-HEALING VS. ACTIVE-SETUP

SHORTCUTS



Some of this will be company-specific, but I'm sure you guys have an idea of what the different sections would encompass.
I know this is a bit of a silly question, but it's due friday and I'm lazy (always found it a good quality for IT'ers) [:D], so if anyone has some good reference materials, or suggestions about outline/what to add/remove... Any input is welcome

Thanks in advance

PJ
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

1
You might look at this though it is a bit dated. http://nexus.realtimepublishers.com/dgwit.php

It still has a good overview of what an MSI is and the basics
Answered 10/27/2009 by: LB3
Senior Yellow Belt

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