I quickly set up an EAP 19 test machine yesterday.1. obviously the whole thing does not work with Central!No template task is created and therefore nothing is pushed to the firewall.2. login restrictions to the Advanced shell is absolutely unacceptable until Sophos fixes the issues that have been known for a long time and can only be fixed via Advanced Shell (WAF, complete log, etc).To follow later...... ;-)Not the first time that Sophos promises things that are never delivered.E.g. the APX 320X should already be manageable via the XG from Q1/2021 (17.5.15).Regards Gerd
What do you mean by "No template task is created"? Do you get an error?
__________________________________________________________________________________________________________________
I just added a fresh Firewall EAP 19 to an existing Central Group with Template.
Nothing happens.
No Task ist generated in Task Queue, no Error Promt, just nothing.
The device stays connected, but not synchronized.
Sorry Lucar,
I have to come back to this point.Here the problem is not EAP 19, but the error seems to be in Central.All of our groups in Central work with EAP 19, but of all things, our initial staging group does not.I haven't found the problem yet, but am investigating further.The problem is that I don't get an error message in Central.
But this has nothing to do with EAP 19 now.Sorry, Gerd
Did you create the group based on a initial Firewall and could it import the config?
I am still investigating.So far I can only conclude that I can't import any of our firewalls configs as a new group.And that's bad, because it means I have to recreate our staging group - a lot of work.
But as I said, now I work with official releases and not with EAP!First impression: The problem is bigger than suspected yesterday in relation to EAP 19. But we should leave the EAP channel
You can mouse over the icon, indicating an issue. And check what is actually causing the problem.
Hi LucaMouse over I did of course, but it doesn't say anything.Test scenario:1. setup of a fresh machine2. downgrade to 18.5.1 (because on fresh setup now 18.5.2 mandatory .3. integration into a new Central Group = ok.4. upgrade to 18.5.2 5. move the new firewall into this group = ok.And here it comes!6. moving the same firewall into our staging firewall into our staging group = ok!So our staging rule is not the problem!!!!!But point 6 this already didn't work with brand new firewalls XGS 2300 today!
I'm a bit tired to do some more troubleshooting for you, so that's it for today.I am not paid by Sophos.
and again, it is not a problem of EAP 19, it is unfortunately much worse!
Sorry i am not able to follow your processes.
Could you give some screenshot of what you actually are seeing?