System Warning Customization

I think what you are looking for is under Users->Groups->Master Group->User Experience. set the "System Warning" to "Don't Use"

 

 

 

HTH

 

Fuzz

Fuzz has got the place to disable the system warning which is triggered by the protected configuration failure, but if you looking to modify the message that appears when you fail the AV check, you have to do that in the Pre-Logon sequence. User > Endpoint Security > Pre-logon sequence. Then find the flow that has the AV check in it and there are boxes that says Access Denied and click on the link for that and you can modify the message to say whatever you want. Hope that help

 

 

Thank you everyone for your quick responses. Unfortunately, neither option really does what I need it to. The system warning is from a protect configuration that uses session variables. Changing the pre-login message doesn't affect the system warning.

 

 

It is true that I could disable the System Warning, but I was hoping to provide end users with a reason why they are missing items. If they just don't see an item on their webtop they will call the HelpDesk, but if they have something that tells them that their definitions are out of date, they might try updating those before opening the ticket.

 

 

We do currently alert users in the pre-login sequence that their AV was detected to be out of date, but in my experience, no one reads the message before they can login (but they do click on the System Warnings icon).

 

 

Thanks again for the help, and I would still love to hear other ideas.

Just to close this thread out:

 

 

I have confirmed from Support that this is not an available option.

 

 

I have put in a feature request.

 

 

Oh well, can't have everything I guess.

I was having the same problem with this. What I ended up doing was adding steps to the pre-login sequence to check all the variables I checked in the protected configuration and fire off e-mails, write to the logon log and/or post a message to the screen depending on if something was out of spec. The other thing you can do is turn on system variable logging under "Device Management->Management->Troubleshooting Tools" check the box that says Save user's session variables to Logon Reports. This way you can find the particular user that is failing and search their logon log for failures. Hope that gives you some ideas.

I am having the same issue,

 

How is a user supposed to know what failed.

 

I too Put in a feature Request..

 

Does anyone know if this has changed in 6.0.3 code?

My organization's approach is to put custom error codes in the pre-logon inspection at points where logon fails. To be clear, the user doesn't even get to a logon page if they don't meet policy; we do not use protected configurations to accomplish policy-based access since the person should not even be logging on if their computer is out of compliance.