This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About rtruyers
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About rtruyers
01-30-2023
1Post
1Like
0Solutions
Jan 30, 2023Last Visited
User
Activity
User
Profile
Latest posts by rtruyers
| Subject | Views | Posted |
|---|---|---|
| 7394 | 06-11-2021 05:50 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 06-11-2021 05:50 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 7 Likes |
User Badges
Community Statistics
| Member Since | 09-08-2020 12:48 AM |
| Date Last Visited | 01-30-2023 01:44 PM |
| Posts | 1 |
| Total Likes Received | 1 |
06-30-2021
07:25 AM
having the same issues here. we have 22 pa-220's sending to cortex data late and iot security(zingbox) using 9.1.6 and this has been an abysmal experience to say the least. had a tac case open. after fighting with it for almost a month, they finally went into root and reset the custid from there, then relicense the firewall, then delete/re-add the certificate. seems that doing the last two steps without tac resetting the custid doesn't always help as the cert won't pull in. I just brought up another box and it's having the same issue as a lot of the other ones I had. Beware, this is not a seemless setup, very cumbersome and quite frankly makes me hate palo a little bit for their poor implementation of this. I'm opening up yet another case to get this one fixed.
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
01-30-2023
01:44 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks