06-06-2018 09:34 PM
Hello
ISE 2.4 patch 1
Anybody know why this shows up every time I login to the admin portal?
I click on OK and the (1) disappears. But after I login again, the same nag message is there again. I don't use client provisioning, nor do I use posturing. I have not changed any of the Client Provisioning settings because that feature is left disabled.
For Posture, I clicked on the "Set to Default" button
I don't have internet access on this deployment. And I can't trick ISE into staying offline either because I don't have a file to feed it.
So what exactly is this nag message telling me to do?
Solved! Go to Solution.
06-09-2018 12:47 PM
I have two 2.4p1 deployments on the go right now, one upgraded from 2.1 and the other upgraded from 2.3. Both had URLs with the pmbu rather than spa. Once I had set both of them to default the warning stopped. Both of these deployments have internet access, just through a proxy config. As mentioned, looks like one of your url's is using the pmbu still?
old urls
https://www.cisco.com/web/secure/pmbu/provisioning-update.xml
https://www.cisco.com/web/secure/pmbu/posture-update.xml
new
https://www.cisco.com/web/secure/spa/provisioning-update.xml
06-08-2018 05:36 PM
I've been seeing this, too. I will check with the teams.
06-09-2018 12:27 PM
Unless the screenshot is wrong, the feed URL for Client Provisioning is the older one. Please set it to the default URL, and see whether it continues prompting afterwards.
06-09-2018 12:47 PM
I have two 2.4p1 deployments on the go right now, one upgraded from 2.1 and the other upgraded from 2.3. Both had URLs with the pmbu rather than spa. Once I had set both of them to default the warning stopped. Both of these deployments have internet access, just through a proxy config. As mentioned, looks like one of your url's is using the pmbu still?
old urls
https://www.cisco.com/web/secure/pmbu/provisioning-update.xml
https://www.cisco.com/web/secure/pmbu/posture-update.xml
new
https://www.cisco.com/web/secure/spa/provisioning-update.xml
06-10-2018 03:12 PM
thanks Damien. The issue in my case was that the old provisioning-update.xml was still in place. The posture was already the new one but I think I fixed that earlier by clicking the very handy "Set to Default" button.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: