Requiring a SQL Server-Side Installation for a Windows Installer-Based Project
InstallShield 2016
Project • This information applies to the following project types:
One way to configure your installation so that it runs only on SQL Server machines is to perform a system search for registry information, store the result in a property, and then use the property in a condition that you set. The following step-by-step instructions show how to do this.
To configure a Windows Installer–based installation to run only on SQL Server machines:
|
1.
|
In the View List under Behavior and Logic, click System Search. |
|
2.
|
Right-click the grid and click Add. The System Search Wizard opens. |
|
3.
|
In the What do you want to find panel, click Registry entry and click Next. |
|
4.
|
In the How do you want to look for it panel, do the following: |
|
a.
|
In the Registry Root list, click HKEY_LOCAL_MACHINE. |
|
b.
|
In the Registry Key box, type the following text: |
Software\Microsoft\Microsoft SQL Server
|
c.
|
In the Registry Value box, type the following text: |
InstalledInstances
|
5.
|
In the What do you want to do with the value panel, do the following: |
|
a.
|
In the Store the value in this property box, type the following: |
SQLSERVERFOUND
|
b.
|
In the Additional Options area, select the Store the value in the property and use the property in an Install Condition option. |
|
c.
|
Click Finish. The Condition Builder opens. |
|
6.
|
Verify the condition, and type a message that you want end users to see if the registry entry is not found on the system. For example, you can type the following message: |
Microsoft SQL Server was not found on this machine. This installation was designed to run only on the server machine.
InstallShield adds an entry to the System Search grid.
See Also
Requiring a Server-Side Installation for an InstallScript Project
SQL Scripts View
Open topic with navigation