The Best Practices Recommended by Microsoft in Creation of a Package
Updated: 11 Nov 2008 | 1 comment
The following are the best practices recommended by Microsoft in creation of a package. It's a good list to keep handy.
- Match Components in previous versions of the .MSI
- Add all executable files to their own components
- Add all .TLB Files to their own components
- Group Matching .HLP and .CNT Files together
- Group Matching .CHM and .CHI Files together
- Put registry keys associated with files or components in matching component
- Put Current user registry keys in their own component
- Put non-Current User registry keys in their own component
- Group all non-executable files to their own component
- Name new non-advertised shortcuts by destination directory
- Group non-keypath resources by resource type
- Create new components for resources not matching other criteria
blog entry Filed Under:
About Endpoint Management Community Blog
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog. Filter by:
Blog Tags
Configuring Altiris Client Management Suite Altiris Deployment Solution Symantec Management Platform (Notification Server) Wise Packaging Basics Altiris Server Management Suite Best Practice Compatibility Tip/How to Helpdesk Solution Altiris IT Asset Management Installing Workflow Solution Ghost Solution Suite Windows Reporting Performance Upgrade Features ServiceDesk 7.x Database Agents Dell Management Products
Comments
Simliar techtip on guidelines..
Similar techtip has been posted already on juice.
http://juice.altiris.com/tip/2675/microsoft-best-p...
Check this link for other general related info.,
http://juice.altiris.com/tip/2490/points-to-rememb...
Also read below for File versioning rules:
Highest Version Wins -- All other things being equal, the file with the highest version wins, even if the file on the computer has the highest version.
Versioned Files Win -- A versioned file gets installed over a nonversioned file.
Favor Product Language -- If the file being installed has a different language than the file on the computer, favor the file with the language that matches the product being installed. Language-neutral files are treated as just another language so the product being installed is favored again.
Mismatched Multiple Languages -- After factoring out any common languages between the file being installed and the file on the computer, any remaining languages are favored according to what is needed by the product being installed.
Preserve Superset Languages -- Preserve the file that supports multiple languages regardless of whether it is already on the computer or is being installed.
Nonversioned Files are User Data -- If the Modified date is later than the Create date for the file on the computer, do not install the file because user customizations would be deleted. If the Modified and Create dates are the same, install the file. If the Create date is later than the Modified date, the file is considered unmodified, install the file.
Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com
Would you like to reply?
Login or Register to post your comment.