cancel
Showing results for 
Search instead for 
Did you mean: 

KB00004286 - Applying a NEW license

EmilioB
06 Trekker

KB00004286 - Applying a NEW license

Windows Server

1. Stop the Prognosis Service (ensure Service comes to a FULL stop)

2. Navigate to :\Prognosis\Server\Configuration\

3. Rename your current license file at that location to license.old

4. Insert the new license

5. Start the Prognosis Service

 

Non-Stop Server (coming soon)

 

Linux Server (coming soon)

2 REPLIES 2
JeffBoothe
05 Base Camper

Re: KB00004286 - Applying a NEW license

NonStop and Linux Coming Soon??????? This post was updated last in MARCH of 2020... Soon??? When will there be an update to this KB???

Scott_Clement
Expert

Re: KB00004286 - Applying a NEW license

Hi @JeffBoothe,

 

We have included instructions in the Product Guide that outline how to update the license files on Prognosis, although these are fairly generic.

You can find these steps under the heading "Updated Licenses on an existing installation" on this page.

I would use a slightly different order if you're doing this while Prognosis is currently running, mainly to try and minimise any down-time:

 

NonStop

1. FTP your new license files in ASCII format to a temporary subvol on the NonStop - E.g. $<vol>.TMPLIC

2. Volume into the Prognosis subvol and rename any existing license files by adding an 'o' to the end of the file name by executing the following:

  • FUP RENAME LICENSE, LICENSEO
  • FUP RENAME LICEXT, LICEXTO
  • **Note: On the NonStop and Unix/Linux platforms, only the LICENSE and LICEXT files are required. The LICSTAT and LICVAR files might be provided in your license pack or you may have a previous copy of these in your Prognosis subvol. In this case, it will be safe to purge them unless you are running a much older version of Prognosis.

3. Volume into $<vol>.TMPLIC and copy your new license files into the Prognosis subvol:

  •     FUP DUP LIC*, <Prognosis Subvol>.*

4. Finally, volume into the Prognosis subvol and execute the following to Stop/Start Prognosis and pick up the new licensing:

  • RUN STOPPRG
  • RUN STARTPRG

 

Linux/Unix would be a similar process (just different commands):

 

1. FTP your new license files in ASCII format to a temporary directory (or copying them via SMB) - E.g. ~/temp

2. Rename any existing license files in the <path>/Prognosis/server/configuration directory by adding a '.old' file extension to the end e.g.:

  • mv license license.old
  • mv licext licext.old
  • **Note: On the NonStop and Unix/Linux platforms, only the LICENSE and LICEXT files are required. The LICSTAT and LICVAR files might be provided in your license pack or you may have a previous copy of these in your Prognosis subvol. In this case, it will be safe to purge them unless you are running a much older version of Prognosis.

3. Copy your new license files into the Prognosis subvol:

  •     cp ~.temp/lic* <path>/Prognosis/server/configuration/

4. Finally, cd into the <path>/Prognosis/server directory and exucute the following to Stop/Start Prognosis and pick up the new licensing:

  •  ./stopprog
  • ./startprog

If you would rather have a short video that demonstrates these steps, please let me know and we can include these in this post as well. I hope this helps!

 

Regards,

Scott Clement

IR Support

Webinar: Keep the modern workforce connected

Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.

Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.

Join webinar
Top Liked Members