This message was deleted.

Hi, you have to unbind all your classic policies and bind your advanced. Do it in CLI and one shoot. 👍

i have unbound the classic ones from the gateway and when i check the bindings from the classic one there aren't bindings even in the ns.config. CLI gives me the same error

no other gateway or other vserver with a classic on the same netscaler ?

yes sure there are other vserver with other classic one but not this gateway i wanted to start first. I wanted to replace one by one to test every single one.

This is your problem. For me you have to unbind all your classic policies from all your vserver. You can’t mix on the same netscaler std and adv pol.

ok this sounds crazy, i have 40 productive gateways, I have to remove all at the same time and then add the advanced ones that i can't test before cause i can't mix them 😲

This is the reason I built new Netscalers and migrated services one by one. It took a while (about a year, but could have been done faster), but it was much safer.

yeah you can’t bind anything to the advanced policy engine until the classic engine is completely unbound.

This is effectively only the case with the session policies, they can't be mixed. I have now started to replace the classic ldaps policies, they don't have problems with a mixed environment. I have now on the same netscaler some gw with advanced policies and some with classic ones.

yeah it’s funny where it actually complains, you can have classic auth policies bound globally and it’ll still work