a following fix has been deployed to all EMEA portals already and will be deployed to Apac and Amer portals during today:
You cannot assign Server Protection profile for a server that has domain controller role. Profile actually gets delivered to device, but portal UI will never change out of the pending state and it shows the previous profile.
a new PSB release is being rolled out with following changes:
new release will be rolled out to all portals in next few days with folloging changes:
new release will be rolled out to all portals today evening and tomorrow with folloging changes:
we noticed after release that some customers actually cannot migrate the profiles, as the profile is already migrated to Computer Protection profiles. And if you enable channel upgrade in this scenario, it actually assigns also this wrong profile into use.
Only way to get it working correctly in this situation is to delete first the profile from Computer Protection profiles, migrated it then to Server Protection profile and run channel upgrade after this.
We are working on a proper fix, but most likely it will go till weekend.
We are sorry for this problem,
fix for these 2 problems is now rolled to all EMEA portals. We'll roll it to AMER portal during tomorrow and this new feature will come to APAC on Sunday or Monday.
PS. This hotfix also added following improvement:
We have released new version to all environments. This release brings some usability improvements to Firewall tab in profile editor, and it also fixes several other minor issues across profile editor.
In case of any problems please contact our community, as usual.
Your PSB Teams
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support and get answers to your questions