Since upgrading our EMS server to 7.2.5 and our clients to FC 7.2.5, the
clients Web Filter, Video Filter, Vulnerability, and System Events no
longer populate in EMS at all. These events don't update under the
Endpoint Views for the clients and there...
I can not get this figured out. I’ve got a FortiGate running v7.2.9
(also tried with v7.2.8) and I’m trying to configure our SSL VPN to use
an external DHCP Server to assign our clients IP addresses. I followed
the instructions outlined here:
https:/...
After upgrading from FortiClient 7.0.10 to 7.2.3, I've noticed that the
exclusion list in the Web Filter no longer works. No changes were made
to the web filter policies, web browser plug-in is enabled in the policy
and installed on the client, what ...
I upgraded our FortiClient EMS server from 7.2.2 to 7.2.3 on Friday, but
the new FortiClient 7.2.3 patch is not available to push out to clients
even though "Keep updated to the latest patch" is selected for the
deployment package. I know I could cre...
We have a web application firewall (WAF) profile applied to incoming
traffic to our web application server. This server hosts several
different applications all using the same FQDN (and IP) but they are
accessed by different sub directories as shown ...
To resolve this issue, I had to have all of my users re-register to EMS
by sending them an invitation. Once the users clicked the register link,
event information started populating in EMS again. The upgrade to 7.2.5
must have broke something. It's j...
Try re-syncing your FortiClient EMS License: In EMS go to:Dashboard ->
Status -> Config License -> Edit Account -> Login & Sync License Now
config system ftm-push > set server-cert "Fortinet_Factory" > set server
XXX.XXX.XXX.XXX (Our Fortigate's Public IP Address) > set status
enableend Our Fortigate's IP does not change when restarting.
Nope, still have the same issue. Anytime I have to reboot the Firewall
(either due to a new firmware update or other reason), the same users
always immediately start receiving the same error again and I have to
re-assign them a different token to get...
EMS was on 7.2.4 and most clients were on FC 7.2.4 with a few others on
FC 7.0.11. Clients were all updated using the official FC 7.2.5
installer package that was automatically downloaded by EMS. I simply
updated the deployment to use the official FC...