Add Prisma Access Agent known and addressed issues
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
---
|
||||
type: Known
|
||||
product: Prisma Access Agent
|
||||
version: 25.1
|
||||
---
|
||||
|
||||
## EPM-4848
|
||||
|
||||
As ring mappings for Prisma Access Agents are calculated during
|
||||
configuration time, the ring mappings might not always be accurate.
|
||||
Some potential causes are new agent enrollments, changes in
|
||||
directory binding, or host operating system updates.
|
||||
|
||||
Workaround: Before initiating a staged upgrade rollout of the
|
||||
agent, perform a commit push. This action ensures all agents are
|
||||
correctly mapped to their designated upgrade rings. If new agents
|
||||
are enrolled after you run the commit push, the new agents are
|
||||
always mapped to the default ring until the next commit push.
|
||||
|
||||
## EPM-4821
|
||||
|
||||
The ConnectPre-logon option is present in the Prisma Access Agent Settings
|
||||
page for Panorama Managed Prisma Access and NGFW deployments, even
|
||||
though it's not functional.
|
||||
|
||||
Workaround: Ignore this option as it won’t work.
|
||||
Reference in New Issue
Block a user