Hi,
Our application installs two virtual websites, databases, MSMQ queues and Windows Services (that makes the calculus).
Now, our install is allowing to install everything in one server; or install the databases on a different server.
Is there a way to install the IIS on a server, the databases on another, the Windows Services on another and the MSMQ on another server?
Besides, installing each feature on each server, can I do that from one single point of install?
Is there a way to install the same registry keys on every server, no matter what feature is installed?
Thanks a lot,
Arnau.
Suggested Articles
Re: Distributed install
Hi Arnau,
You cannot have one installer that will distribute parts of your application on different machines. This is because the websites, the MSMQ ques and the Windows Services are related to the system they will be installed on.
What you can do with Advanced Installer is to have a single installer with a custom dialog that will require user interaction. Depending on the user's choice in this dialog, the installation of certain parts of your application will be conditioned.
In this way, you can run the same installer on different machines and install only the part you are interested in for that particular machine.
For creating such a dialog, you can start from the How do I show a custom feature selection dialog? article.
Under the Service page, you can add your Windows Services. The Windows services cannot be conditioned separately, as for installing these services the InstallServices standard Windows Installer action is used. In order to condition (all of the services), you need to go to the InstallExecuteSequence table, in the Table Editor page, and change the condition from the InstallServices action.
You should create you websites in the IIS page. You can read the Configuring IIS Web Sites and Virtual Directories for further hints and guidance.
The databases are defined in SQL Database page.
You can find the MSMQ queues as Windows Feature Bundle in the Prerequisites page.
The websites, the databases and the MSMQ queues as prerequisites can be conditioned by the Conditon field found in each page.
Should you encounter any difficulties in implementing something, please do not hesitate to contact us and we will gladly assist.
Kind regards,
Irina
You cannot have one installer that will distribute parts of your application on different machines. This is because the websites, the MSMQ ques and the Windows Services are related to the system they will be installed on.
What you can do with Advanced Installer is to have a single installer with a custom dialog that will require user interaction. Depending on the user's choice in this dialog, the installation of certain parts of your application will be conditioned.
In this way, you can run the same installer on different machines and install only the part you are interested in for that particular machine.
For creating such a dialog, you can start from the How do I show a custom feature selection dialog? article.
Under the Service page, you can add your Windows Services. The Windows services cannot be conditioned separately, as for installing these services the InstallServices standard Windows Installer action is used. In order to condition (all of the services), you need to go to the InstallExecuteSequence table, in the Table Editor page, and change the condition from the InstallServices action.
You should create you websites in the IIS page. You can read the Configuring IIS Web Sites and Virtual Directories for further hints and guidance.
The databases are defined in SQL Database page.
You can find the MSMQ queues as Windows Feature Bundle in the Prerequisites page.
The websites, the databases and the MSMQ queues as prerequisites can be conditioned by the Conditon field found in each page.
Should you encounter any difficulties in implementing something, please do not hesitate to contact us and we will gladly assist.
Kind regards,
Irina
Re: Distributed install
Ok.
Our customer will have to execute the installation on every server and choose what he needs.
But, there are parts of the install that are common. For example, the registry keys. We need to install all the keys in all the servers. Right now, each key is associated to a feature and it's only installed with that feature. Can I associate the registry keys to all the features?
Thanks in advance,
Arnau.
Our customer will have to execute the installation on every server and choose what he needs.
But, there are parts of the install that are common. For example, the registry keys. We need to install all the keys in all the servers. Right now, each key is associated to a feature and it's only installed with that feature. Can I associate the registry keys to all the features?
Thanks in advance,
Arnau.
Re: Distributed install
Hi Arnau,
In order for those registry keys to be installed all the time, you need to put them in a feature that will always be installed.
So, it you already have such a feature, you can simply move all registry keys in that feature.
Or, if you would like, you can create another feature and put your registry keys in it.
In order for this feature not to appear in the feature selection dialog, you can choose "Not displayed" for the "Feature Tree" field in the General Feature Properties.
Kind regards,
Irina
In order for those registry keys to be installed all the time, you need to put them in a feature that will always be installed.
So, it you already have such a feature, you can simply move all registry keys in that feature.
Or, if you would like, you can create another feature and put your registry keys in it.
In order for this feature not to appear in the feature selection dialog, you can choose "Not displayed" for the "Feature Tree" field in the General Feature Properties.
Kind regards,
Irina