locked
Add new script for endpoint detection in UAG RRS feed

  • Question

  • Hi,

    I made a script for endpoint detection in UAG.
    The step I made are:
    1. copy script into \von\internalsite\customupdate and name it myscript.vbs
    2. Create custom “detect.inc” file in \von\internalsite\inc\customupdate and the content of this file is:
    <% g_scriptList("/InternalSite/CustomUpdate/myscript.vbs") = false %>
    3. Create custom “PolicyTemplate.xml” in \von\conf\customupdate and the content of this file is:
    <Policies>		
    	<Policy>
    		<Name>MyScript</Name>
    		<ID>MyScript</ID>
    		<Type>0</Type>
    		<Value></Value>
    		<Description>Check something.</Description>
    		<Section>Variables\System</Section>
    	</Policy>
    </Policies>
    After activate UAG, I can see this in policy editor. I also made a policy to use this detection. For some reason, I did not use this policy now. I only create this policy. I think I can see value of my detection in Web Monitor but not.

    Anything wrong? I reference steps of IAG.

    BTW, client trace seems different with IAG component. Any document for this?
    邁格行動 技術顧問 George 小顧 部落格: http://www.magg.com.tw/blog/
    Wednesday, March 17, 2010 12:12 AM

Answers

  • Hi George,

     

    The error lies in your custom PolicyTemplate.xml, in the <Name> and in the <ID> attributes. These should contain the variable that your custom VBS script populates with some value, and not the name of the script itself.

    The <Name> attribute is the name of the variable that will appear in the Policy Editor, and the <ID> is the actual variable that you will use within the policy.

     

    Let’s say, for example, that you want to check the existence of a Windows Registry key on the client machines, and your script therefore uses a variable MyRegKeyExists. The relevant piece of PolicyTemplate.xml would be something like this:

     

    <Name>Corp Client Registry Key</Name>

                <ID>MyRegKeyExists</ID>

     

    Do not forget to restart the UAG Management console after you have created this XML, so that it will be loaded by the console and the new policy variable will be displayed in the policy editor.

     

    Then, using the Endpoint Detection Policy Editor, you should change an already existing detection policy or create a new one which will make use of this new variable, and, obviously, assign this policy to one of your trunks or your applications published through a trunk.

     

    HTH,
    -Ran

    • Marked as answer by George 小顧 Thursday, March 18, 2010 3:50 AM
    Wednesday, March 17, 2010 7:43 AM

All replies

  • Hi George,

     

    The error lies in your custom PolicyTemplate.xml, in the <Name> and in the <ID> attributes. These should contain the variable that your custom VBS script populates with some value, and not the name of the script itself.

    The <Name> attribute is the name of the variable that will appear in the Policy Editor, and the <ID> is the actual variable that you will use within the policy.

     

    Let’s say, for example, that you want to check the existence of a Windows Registry key on the client machines, and your script therefore uses a variable MyRegKeyExists. The relevant piece of PolicyTemplate.xml would be something like this:

     

    <Name>Corp Client Registry Key</Name>

                <ID>MyRegKeyExists</ID>

     

    Do not forget to restart the UAG Management console after you have created this XML, so that it will be loaded by the console and the new policy variable will be displayed in the policy editor.

     

    Then, using the Endpoint Detection Policy Editor, you should change an already existing detection policy or create a new one which will make use of this new variable, and, obviously, assign this policy to one of your trunks or your applications published through a trunk.

     

    HTH,
    -Ran

    • Marked as answer by George 小顧 Thursday, March 18, 2010 3:50 AM
    Wednesday, March 17, 2010 7:43 AM
  • TKS. I know what's going on. I need to assign this variable to one policy which assign to trunk or application.

    But here is a script problem. My script does not work as I think. I need to trace it. In IAG, there is client trace. But it is gone in UAG.

    So how to trace it on client computer?

    邁格行動 技術顧問 George 小顧 部落格: http://www.magg.com.tw/blog/
    Wednesday, March 17, 2010 9:30 AM
  • TKS. I know what's going on. I need to assign this variable to one policy which assign to trunk or application.

    But here is a script problem. My script does not work as I think. I need to trace it. In IAG, there is client trace. But it is gone in UAG.

    So how to trace it on client computer?

    邁格行動 技術顧問 George 小顧部落格: http://www.magg.com.tw/blog/

    Have a look here: http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/thread/c8e4538b-47e3-4355-9ccc-52cf7e84a36e

    Cheers

    JJ
    Jason Jones | Forefront MVP | Silversands Ltd
    Wednesday, March 17, 2010 11:27 AM