Naturally, just having a custom script is not going to accomplish anything. It's the endpoint policy integration that's the point of all of this. However, one must understand how endpoint policies work to take full advantage of this. We recommend you read Chapter 8, Endpoint Policies, from Packt Publishing's Microsoft Forefront UAG 2010 Administrator's Handbook, which discusses endpoint policies, to get the basics of creating and assigning policies.
As we illustrated earlier, the way the detection script sends information to UAG is with the results
function. Each detection function makes a decision, and runs a command similar to the following:
Results("Screen_Saver_Running") = True
So, throughout running the entire script, several hundreds of these are run. Some return Boolean values of true
or false
, and other deliver strings. All of these are collected by UAG for that session, and so the endpoint policy evaluation engine has access to...