Requiring signature validation for custom detection scripts

Published: April 8, 2010

Updated: July 31, 2012

Applies To: Unified Access Gateway

The Forefront Unified Access Gateway (UAG) Client Endpoint Detection component uses a script to detect applications on a client endpoint, based on the presence of files and registry keys. If the Forefront UAG administrator creates a custom detection script, end users can require that the custom script be signed.

  1. On the client endpoint, click Start, and in the Start Search box, type regedit, and then press ENTER.

  2. Open the key HKEY_CURRENT_USER\Software\WhaleCom\Client\Detection. On 64-bit computers, the key is HKEY_CURRENT_USER\Software\Wow6432Node\WhaleCom\Client\Detection.

  3. Set the REG_DWORD entry SignedAllScripts to 1.

    If the SignedAllScripts or Detection keys do not exist, create the keys.

    Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method, requiring that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.