Accepted Solutions
Prognosis has a feature called "File Transfer and Execution" which will allow you to distribute your file to online nodes and perform a Prognosis restart to apply the license file. This can be performed both from a Windows Client command execution, or from command line and even a batch file to perform this on all nodes at once.
IR Support have also added an easily accessible link to this in the free "Prognossis Self Monitoring" extended solution they make available to customers on request.
PSM Example:
Batch File Example:
Online help with syntax and pre-reqs: https://help.prognosis.com/server/119/operations/file-transfer-and-execution
Support Tips on using this:
1. Once the node goes offline due to expired license you cannot use this feature.
2. You do require a COMMAND:TEA entry in the Password Configuration on the manager node with credentials that have permissions to all the other nodes.
Note: If inidividual logons and passwords are required, then an extry in the Password Configuration for each node will allow this: COMMAND:TEA:NODENAME
3. The value to put in the command section will perform both a NET STOP and a NET START of the prognosis service:
"C:\Prognosis\server\Configuration\RestartPROGNOSISforWindows.bat"
Note: You need to put the drive letter/path specific for your Prognosis installation on the lower node here. The NET variant with && will not complete and run the start so this batch file is the best option as it exists on all Prognosis for windows servers.
Once the pre-reqs are in place, you can use the GUI document, PSM link, commandline syntax, or batch file containing 1 or more instances of the command to deploy licenses to any windows monitoring node.
Prognosis has a feature called "File Transfer and Execution" which will allow you to distribute your file to online nodes and perform a Prognosis restart to apply the license file. This can be performed both from a Windows Client command execution, or from command line and even a batch file to perform this on all nodes at once.
IR Support have also added an easily accessible link to this in the free "Prognossis Self Monitoring" extended solution they make available to customers on request.
PSM Example:
Batch File Example:
Online help with syntax and pre-reqs: https://help.prognosis.com/server/119/operations/file-transfer-and-execution
Support Tips on using this:
1. Once the node goes offline due to expired license you cannot use this feature.
2. You do require a COMMAND:TEA entry in the Password Configuration on the manager node with credentials that have permissions to all the other nodes.
Note: If inidividual logons and passwords are required, then an extry in the Password Configuration for each node will allow this: COMMAND:TEA:NODENAME
3. The value to put in the command section will perform both a NET STOP and a NET START of the prognosis service:
"C:\Prognosis\server\Configuration\RestartPROGNOSISforWindows.bat"
Note: You need to put the drive letter/path specific for your Prognosis installation on the lower node here. The NET variant with && will not complete and run the start so this batch file is the best option as it exists on all Prognosis for windows servers.
Once the pre-reqs are in place, you can use the GUI document, PSM link, commandline syntax, or batch file containing 1 or more instances of the command to deploy licenses to any windows monitoring node.
