- 
Automated HotFix installation
Category Domino
Bookmark :
The customer I am currently working for is very strict in rolling-out Domino hotfixes, especially security hotfixes. Security hotfixes have to be installed on all server within 72 hours and untill now this meant that administrators had to either work late or very early in order to install the hotfix during the service window.
So I thought, let's see if I can automate the installation. And guess what....
Bookmark :
The customer I am currently working for is very strict in rolling-out Domino hotfixes, especially security hotfixes. Security hotfixes have to be installed on all server within 72 hours and untill now this meant that administrators had to either work late or very early in order to install the hotfix during the service window.
So I thought, let's see if I can automate the installation. And guess what....
I can, well, at least on Windows servers (which is the only operating system used by this customer).
I created a database where you simply create a configuration document with the hotfix to be de-installed (if any), the hotfix to be installed and the servers to install the hotfix on.
At 6 AM an agent kicks-off, detaching the hotfix files, searching through the registry to see which servers are running on the machine (yes, it also works for partitioned servers), creating a batch file, creating a program document in the Domino directory* and starting that batch file or sned out an email if anything went wrong during the process.
The batch file will:
- Stop all servers
- De-install the previous hotfix
- Install the new hotfix
- Start all servers that were running
All servers in the domain are up and running again at around 6.05 AM.
* If the ID file that was used to sign the agent has create access to the Domino directory a program document will be created that will start 10 minutes after the agent has run. The program document will kick-off another agent that will send a notification messages to user(s) defined in the configuration of the tool with the new Domino server version in the subject. The agent will also remove the program document that was previously created.
I created a database where you simply create a configuration document with the hotfix to be de-installed (if any), the hotfix to be installed and the servers to install the hotfix on.
At 6 AM an agent kicks-off, detaching the hotfix files, searching through the registry to see which servers are running on the machine (yes, it also works for partitioned servers), creating a batch file, creating a program document in the Domino directory* and starting that batch file or sned out an email if anything went wrong during the process.
The batch file will:
- Stop all servers
- De-install the previous hotfix
- Install the new hotfix
- Start all servers that were running
All servers in the domain are up and running again at around 6.05 AM.
* If the ID file that was used to sign the agent has create access to the Domino directory a program document will be created that will start 10 minutes after the agent has run. The program document will kick-off another agent that will send a notification messages to user(s) defined in the configuration of the tool with the new Domino server version in the subject. The agent will also remove the program document that was previously created.