Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Overview of this book

While UAG is built to integrate with many environments and publish dozens of application types, many organizations require a certain level of customization to meet their needs. With this book in hand, you will be equipped to deal with these types of customization scenarios, and you will be confident in using such workarounds without hassle and trial and error. Written by some of the leading experts on UAG, "Mastering Microsoft Forefront UAG 2010 Customization" covers the most complex and challenging options for customizing UAG in a way that is friendly and easy to follow. It walks you through various customization tasks, including explanations and code samples, as well as creative ideas for troubleshooting your work. Until now, only a few of the extensions to UAG's services have been publicly available, and most were only known to a select few. Now, this can include you! Throughout this book, you will tackle how to change the system's look-and-feel, deal with advanced authentication schemes and write special functions that need to be executed as part of the client interaction. With "Mastering Microsoft Forefront UAG 2010 Customization", you too can learn how to customize various aspects of UAG's functionality to enhance your organization or customers' experience.
Table of Contents (16 chapters)
Mastering Microsoft Forefront UAG 2010 Customization
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

How does endpoint detection work?


First and foremost, endpoint detection relies on the endpoint client components. Some companies disable these, not realizing what they are missing, but you haven't, right? The detection process itself is initiated by the ASP page InstallAndDetect.asp, which fires up the detection module on the client and sends over the core detection logic (<UAG Path>\von\InternalSite\Detection.vbs) via a special JavaScript (<UAG Path>\von\InternalSite\scripts\detection.js). The detection VBScript is executed on the client itself, collects the various parameters, and then sends them back to the server as value sets.

As you can see in the following screenshot, this is the function that checks if Norton 360 (an Antivirus product) is installed. It checks this by using the function Whale. FileSystem.Exist, which checks for the existence of a file on the endpoint's hard drive.

If the file is found, the result value AV_Norton360_Installed is set to true, a Boolean value...