During any change like token assignment, FAC/FGT unit tells FortiGuard (that directregistration server) that certain token was assigned and someone will come from mobile device to pick it. And that applies also to FortiToken Mobile. Other units are unable to use same license.
Fortigate vm license file generator serial number#
Mobile tokens are bond to license and license is always bond to serial number of the unit where it was activated. Sorry, I assumed, wrongly, that when you have converted HW to VM unit (and got new serial number for that VM unit), that someone from Fortinet support (who made conversion) also handled tokens. It appears to be a GUI bug and TAC is looking into it.
Fortigate vm license file generator password#
Entering a proper password allows one to browse Remote Sync Rule definitions OUs, but not for the LDAP server definition. If we put a known bad password in this setting it broke the ability to browse in both locations. We have remote sync rules setup, and those DO allow you to browse the LDAP/AD directory so the Remote LDAP server definition is correct. We wasted a lot of time on this until realizing it will NEVER work. If you press it, it will indicate "failed query due to invalid credentials". Once they did that, the free tokens became assignable and things started working again.Īnother issue we discovered is the LDAP Browse for Remote LDAP servers definition DOES NOT WORK in 5.1.2, 5.2.2 and 5.3.1. There was some trepidation that this would kill all of our FTMs (nearly 200 issued), but it does not appeared to have done so. This can only be done by customer service. So resolution was Tech Support had to re-assign my FTMs to my new FACVM serial number.
0 kommentar(er)
