[Req] FortiGate ESXi VM 6/7 License

[tryllz]

I have tested HA on this and it does not work. Every device has a random Serial when 1st booted up, however, once licensed with this license all Fortigate's have the same Serial number. Serial number is one of the components of HA setup, and there is no way to change the serial Number without FortiManager. The Python script does not have anything relating to this either.

This is the hidden content, please

• Sign In
• or
• Sign Up

Edited January 13, 2024 by tryllz

[sillysatan]

8 hours ago, tryllz said:

I have tested HA on this and it does not work. Every device has a random Serial when 1st booted up, however, once licensed with this license all Fortigate's have the same Serial number. Serial number is one of the components of HA setup, and there is no way to change the serial Number without FortiManager. The Python script does not have anything relating to this either.

 

Hidden Content

 

 

 

Line 105 in the python script got the serial, just change that.

[tryllz]

15 hours ago, sillysatan said:

Line 105 in the python script got the serial, just change that.

Thanks @sillysatan for pointing that out, I did go through it yesterday, just did not think modification would result in an acceptble license.

Glad to say that it worked with some tinkering, currently testing HA, shows both Primary and Secondary, will update on how to get the licenses with different Serial Number in some time.

Edited January 14, 2024 by tryllz

[tryllz]

Here is how to get unique Serial Number for each VM (10 unique license file have been added for download at the end).

The Serial Number in line 105 has to be changed but only the last 9 characters, booting up a new VM will generate a new Serial number and its last 7 characters are to be used.

• Serial Number in line 105 - FGVMPGLICENSEDTOCATALPA
• New VM Serial - FGVMEVZQ002KI8CF
• Serial Number To Use - FGVMPGLICENSED02KI8CF (NOTE : I have removed TO from the original Serial Number)
• Save the Python file
• Now run the Python script to generate the license file to use.

This has to be repeated with a new Serial Number for each VM, I'm not a python guy so I don't know if the script can be edited to randomize this.

Also of note is that in some casses the license shows as below.

This is the hidden content, please

• Sign In
• or
• Sign Up

This is the hidden content, please

• Sign In
• or
• Sign Up

Below is a working HA setup, as you can see the Serial Numbers are now different.

This is the hidden content, please

• Sign In
• or
• Sign Up

If a Serial Number has an _ or - character in it, it can be removed and the characters can be used consecutively to use the Serial Number, tested only with _.

10 unique license files for use can be downloaded from below :

This is the hidden content, please

• Sign In
• or
• Sign Up

Edited January 14, 2024 by tryllz

[FaEDUar]

On 4/12/2023 at 2:55 AM, TonyQ said:

It looks like the chinese have figured it out:

  Reveal hidden contents

 

Hidden Content

• Give reaction or reply to this topic to see the hidden content.

 

THANKS

[Rapici]

Thanks bro!

[ciscosddc]

Hello tryllz

about

"

The Serial Number in line 105 has to be changed but only the last 9 characters, booting up a new VM will generate a new Serial number and its last 7 characters are to be used.

• Serial Number in line 105 - FGVMPGLICENSEDTOCATALPA
• New VM Serial - FGVMEVZQ002KI8CF
• Serial Number To Use - FGVMPGLICENSED02KI8CF (NOTE : I have removed TO from the original Serial Number)
• Save the Python file
• Now run the Python script to generate the license file to use.

This has to be repeated with a new Serial Number for each VM, I'm not a python guy so I don't know if the script can be edited to randomize this.

"

tested with 7.4.2 but not working: have you tested it ?


p.s.: I have not understand why you indicate "changed but only the last 9 characters" when after you use last 7 characters ...


For example

FTGVM-7.2.4# diag debug vm-print-license
FGVMEVAA2S1KLX8A

so taken the latest 7 characters S1KLX8A
and copied on the Python file on line 105
FGVMPGLICENSEDS1KLX8A
run the Python script to generate the license file to use

but not working....

[tryllz]

3 hours ago, ciscosddc said:

tested with 7.4.2 but not working: have you tested it ?

p.s.: I have not understand why you indicate "changed but only the last 9 characters" when after you use last 7 characters ...

For example

FTGVM-7.2.4# diag debug vm-print-license
FGVMEVAA2S1KLX8A

so taken the latest 7 characters S1KLX8A
and copied on the Python file on line 105
FGVMPGLICENSEDS1KLX8A
run the Python script to generate the license file to use

but not working....

Its clarified in earlier comments this license does not work with 7.4.2..

When you say not working, what is not working, the script does not generate a license file, or the license file generated is not accepted by Fortigate, or something else.

Your question is not clear..

Can you share screenshots of what is not working..

Edited January 21, 2024 by tryllz

[ciscosddc]

Hello,

"
its clarified in earlier comments this license does not work with 7.4.2..
"
Ok

and on the 7.0.13 is working ?

"
When you say not working, what is not working, the script does not generate a license file, or the license file generated is not accepted by Fortigate, or something else.
"

On 7.2.4 if I try to upload the license is not accepted on the FortiGate

[tryllz]

9 hours ago, ciscosddc said:

and on the 7.0.13 is working ?

On 7.2.4 if I try to upload the license is not accepted on the FortiGate

I have tested this only on 7.4.1, works fine on it..

[kechik]

Hi,

 

 May i know whether we can make this license permanent? I means after we apply license then we commit the image. So if the image is corrupt then we juat deploy back the image that has been included the license. Appreciate someone feedback

[tryllz]

10 hours ago, kechik said:

Hi,

 

 May i know whether we can make this license permanent? I means after we apply license then we commit the image. So if the image is corrupt then we juat deploy back the image that has been included the license. Appreciate someone feedback

The best way is to take back up of configuration, create a new VM, license it, then import configuration..

The license cannot be changed once its added..

[paulierco]

Thanks

[samguan]

cool for it

[dallali]

thanks

[ciscosddc]

Hello,

anyone have tested on lastest releases ?
7.4.3
7.2.7
7.0.14

[ieuqcoqve35s]

thanks +1

[alexandrei17]

Nice

[l1v1u]

nice

 

[fkdr]

thanks

[digidumb]

On 2/25/2024 at 6:30 AM, ciscosddc said:

Hello,

anyone have tested on lastest releases ?
7.4.3
7.2.7
7.0.14

Can confirm 7.4.2 and 7.4.3 do NOT work.

Latest in the 7.4.X line is 7.4.1.
Updating a licenced 7.4.1 will break the licence too.

[Mohamedjoker]

done

[lion2021]

....

[che2n]

thanks

[naonline]

thanks