FortiEMS: Is changing FQDN Name affecting current invitations/registrations?

Forum|Forum|10 months ago
November 27, 2025
5 replies
823 views

Hello.

We want to change our EMS-Server to be reachable from Public and not only from internal network.

At the moment users connect to an internal FQDN-Name while on internal network or connected via VPN.

When changing the FQDN name of EMS-Server to a public reachable name, is this affecting the current connected users?

The current users are connected through an invitation code and registered via LDAP to EMS-Server. Do they need a new invitation code after changing the FQDN Name?

Thank you.

Best answer by funkylicious

hi,

i did a test in my lab but be careful in production.

when changing the EMS FQDN (in EMS Settings > Use FQDN) for which the invitation code was created, you would get a This invitation code is disabled as EMS stopped listening to address ems.company.local under the invitations already generated, but my endpoint would still remain connected using the old FQDN, assuming that the old FQDN would still exist/resolve to the IP of EMS.

also, in Configure EMS Server List the old FQDN would disappear and the new one would be available for choosing, a newly created invitation you could choose the new one and then select/mark the endpoints ( in bulk i think also works ) Action > Switch EMS > Switch by invitation and then insert the newly generated bulk one with the new FQDN.

a idea would be to have a FQDN resolvable from the Internet in the public IP and internally in the private IP

funkyliciousAnswer

SuperUser

hi,

i did a test in my lab but be careful in production.

when changing the EMS FQDN (in EMS Settings > Use FQDN) for which the invitation code was created, you would get a This invitation code is disabled as EMS stopped listening to address ems.company.local under the invitations already generated, but my endpoint would still remain connected using the old FQDN, assuming that the old FQDN would still exist/resolve to the IP of EMS.

also, in Configure EMS Server List the old FQDN would disappear and the new one would be available for choosing, a newly created invitation you could choose the new one and then select/mark the endpoints ( in bulk i think also works ) Action > Switch EMS > Switch by invitation and then insert the newly generated bulk one with the new FQDN.

a idea would be to have a FQDN resolvable from the Internet in the public IP and internally in the private IP

"jack of all trades, master of none"