About Remo

HI @Stellinger According to the warning, you have a multi vsys firewall where the cert is located in shared context and therefore (in theory) should be visible in all vsys. You wrote that you checked locally and the new cert is there. Sorry for the dumb question but you did look for the cert name of the expiration warning? If the configuration is pushed from panorama as far as I understood) you need to execute "show config pushed-tenplate | match <certname>" instead of "show configuration". ... View more

Hi @tonyajit  Paloalto has already a very good admin guide where these things are explained 😉   Templates and Template Stacks: https://docs.paloaltonetworks.com/panorama/11-1/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/templates-and-template-stacks   Device Groups https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/device-groups   Device Group Hierarchy https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/device-groups/device-group-hierarchy ... View more

The troubleshooting goes on. So far support has multiple memory dumps and cortex logs. Unfortunately so far I don't know any result of the analysis. Next week we plan to have a call between Paloalto and Citrix in order to move on in this situation.   At least so far it looks like with version 8.6.0 the situation seem to be more stable.   ... View more

@Mahesh_Vankhede It should not be that bad, but you could request a case update. This way the support manager gets notified also about this 'escalation'. ... View more

It's about how @CosminM wrote. When the device is registered already, you only need the serial number to get a quote from the VAR. If there is a way to license it as you want then I am sure the VAR knows how to get there. ... View more

This also depends on the support level you have bought. Not every level requires you to open the case first - even thought it definately is useful if you provide some informations in order to hopefully get the right person on the phone. ... View more

@E.Jafarov to be honest, this does not really help. The issues we have seem to be quite complex as support so far is still analyzing the issue. It is not only the high cpu (even if disabling event collection is also not a solution as if you have cortex xdr you probably want this feature), the servers simply and then need to rebooted. Which results in hours of work lost for our customers every time it happens ... ... View more

... these waittimes are the reason why I no longer call tac support and only use the support portal to create a case first ... ... View more

Hi @jmazzeo  Thanks for your answer. Yes we installed cortex according to this document. But on server 2022 we still have big issues. At least until version 8.5.0. We actually always used the TS_ENABLED=1 param for these multi-user servers, but TAC told us to use the VDI_ENABLED=1 option for out installation, so since about 2 month. Which option would you recommend and are there other hints on how to successfully use cortex xdr on citrix servers?   ... View more

That's at least how it works for me. As far as I know every partner has an assigned account manager from paloaltonetworks (of cours every account manager has way more than one partner assinged). And there you need to send the information about the (potential) new customer. Thats how it works ... ... View more

This is not possible. You need to ask your Paloalto Networks account team to add a new customer. ... View more

That's a great solution for this use case. I think your not the only one with this "problem". Thanks for sharing 😊 ... View more