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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- Discussions
- General Topics
- Who rated this post
Who rated this post
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
10-07-2020 05:39 AM
We were running GlobalProtect 5.0.x for a while and just recently upgraded the clients to 5.2.2. And thats when this issue popped up for us. A workaround that I found is to launch ADUC from the command line with the /server switch, "dsa.msc /server=<ip of the dc>". When I specified the ip of the dc, ADUC was very responsive.
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks