Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolverApplication Conflict Evaluators (ACEs)1174 ADS-0950-UG00 AdminStudio 9.5 User GuideWTS05This ACE examines a Windows Installer package for compatibility with Windows Terminal Server. WindowsTerminal Server generally requires installation components to be installed for all users, rather than on a per-userbasis.Note • If your package is not targeting the Windows Terminal Server environment, then you do not need to run thisACE.WTS05 checks for any environment strings installed to per-user specific locations. The WTS05 warning string isdisplayed in the following format:The component '[COMPONENT]' in package '%s'('%s') has a per-user Environment Setting'[NAME]'('[VALUE]'). This value affects deployment of this package in a terminal serverenvironment.SummaryUser-Defined ACEsIn addition to business rules (ACEs) shipped with ConflictSolver, you can also create your own company-specificbusiness rules to use when detecting conflicts. For example, your organization may want to identify (and change)any VBScript custom actions that have a hard-coded drive letter, any applications that create desktop or uninstallshortcuts, any applications that have Startup registry entries, or any applications that place files in the systemdirectory. You can create custom rules to identify these (and many more company-specific situations) usingConflictSolver.Creation of user-defined ACEs is done using the Rules Wizard.Table 13-53 • WTS05 SummaryTopic DescriptionConflict Type: Best Practice Rule / Windows Terminal Server CompatibilityDescription: WTS05 checks for any environment strings installed to per-user specific locations.Result: If an environment string is installed to a per-user specific locations, a warning isgenerated.Resolution Type: ManualResolution: Duplicate the per-user Environment table entries and conditionalize the installation ofthese new Environment table entries to only be installed if the ALLUSERS property is setto 1.
