How do I create installations for Terminal Server?
One of the most attractive features of Windows Installer-based installations confirms the existence of key files or registry keys at run time. Unfortunately, this feature is problematic when creating an installation targeted for Terminal Server as the separation of per-user and per-computer data on the operating system can cause self-repair during startup.
To minimize the constant self-repair, use one of the following procedures.
Enabling Terminal Services Support During Installation Development
- Open Wise for Windows Installer, Wise for Visual Studio .NET, or Windows Installer Editor in Wise Package Studio.
- Select File > Open and select the .wsi project to which to add Terminal Server support.
- Click the Installation Expert tab.
- Go to the Releases page.
- Select the release and click Details. The Release Details dialog appears.
- From Release Type, select Terminal Server Enabled.
- Click OK.
Converting an .msi to Support Terminal Server Component Rules
- In Wise for Windows Installer or Wise for Visual Studio .NET, select Tools > Package Validation. In Wise Package Studio, open the Package Validation tool. The Specify Target Installation File dialog appears.
- Select the .msi file and click Next. The Welcome dialog appears.
- Mark the Terminal Server Compatibility rule. Click Next.
- After the validation runs, the View/Correct dialog appears.
- Select any listed errors and click Correct to apply the component rule and prevent continuous self-repairs.
By either building or altering an installation to minimize the frequency of self-repairs with Terminal Server, you can ensure that Terminal Server end users benefit from the reliability of an .MSI-based application.