User Guide

Component Rules

! Add all files to their own components

If the added resource is a file, create a new component.

! Put registry keys associated with files or components in matching

components

If the added resource is a registry key, and the registry value name or value refers to

a file or component, add the resource to an existing component that contains the

same type of resource.

! Put Current User registry keys in their own component

If the added resource is a registry key under HKEY_CURRENT_USER, add the

resource to the component matching the conditions and set the component key base

to CurrentUser. The component key base will be incremented for each new

component matching this condition. Example: CurrentUser1, CurrentUser2, and so

on.

! Put non-Current user registry keys in their own component

If the added resource is a registry key NOT under HKEY_CURRENT_USER, add the

resource to an existing component that contains the same type of resource.

! Name new non-advertised shortcuts by destination directory

If the added resource is a shortcut, add it to an existing component containing non-

advertised shortcuts in the same destination directory.

! Group non-keypath resources by resource type

If the added resource cannot be set to the keypath, that is, if it is not a file, registry

key, or ODBC data source, add the resource to an existing component that contains

the same type of resource.

! Create new components for resources not matching other criteria

For all other resources that do not match the criteria above, create a new component

for the resource and set the component key to the table name of the keypath or the

first resource. If multiple components are named for the same table, an incremental

number is added to the component name. Example: File1, File2, and so on.