Share via

Customizing the IAG Client Endpoint Detection component

  • Article

Applies To: Intelligent Application Gateway (IAG)

Whale Communications Intelligent Application Gateway (IAG) 2007 Client Endpoint Detection component uses the default script WhaleDetection.vbs to detect applications on a client endpoint based on the presence of files and registry keys. This file is located in the folder C:\Whale-Com\e-Gap\von\InternalSite. You should not customize this default file because it is signed.

Creating a customized detection file

Instructions to add a separate customized detection file are included as comments in the C:\Whale-Com\e-Gap\von\InternalSite\Detect.inc file. You can also reuse code from whaledetection.vbs when creating a customized file.

IAG Service Pack 2 includes changes first provided by e-GAP Appliance 3.6 and IAG Update 1. For more information, see Microsoft article 948280: Description of Update 1 for e-Gap Appliance 3.6 and for IAG 2007. IAG no longer requires signature validation for custom detection scripts. You can set validation to be required. Note that the instructions in Detect.inc do not reflect changes made in signature behavior.

To require signature validation for custom scripts

  1. Click Start, and type Regedit in the Search box.

  2. Navigate to HKEY_CURRENT_USER\Software\WhaleCom\Client\Detection

  3. To enforce signature checking for custom scripts, set the REG_DWORD entry SignedAllScripts to 1.

Note

This task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see Microsoft article 322756: How to back up and restore the registry in Windows.

Note

IAG Service Pack 1 Update 5, and IAG Service Pack 2 introduce two new client detection APIs that enable the creation of advanced endpoint detection scripts. After you apply this update, you can create custom detection scripts to retrieve information about the Windows updates that are applied on a client computer. Because this data can be compared with a list of required updates, it can be used in a detection policy. Information that can be retrieved includes computer name, computer SID, domain name, domain membership status, and workgroup name. These APIs are implemented by querying WMI on the client computers. For more information about WMI detection, see Microsoft article 955123: Description of Update 3 for e-Gap Appliance 3.6 and Update 4 for Intelligent Application Gateway 2007.