Users Guide

748 | OnGuard Dissolvable and Native Agents Dell Networking W-ClearPass Policy Manager 6.6 | User Guide
9. From the Services page, click Reorder, then place the service for the V4 SDK before the service for the V3
SDK.
This ensures that WebAuth requests with the V4 SDK are evaluated by the service configured for the V4
SDK.
Important Points
1. After installing W-ClearPass 6.6.7, OnGuard Agent is configured to use the OnGuard plugin version 2.0:
OESIS V4 SDK by default. Thus, to fully configure the OnGuard plugin version 2.0, you must follow the
procedure described above in Creating a WebAuth Service for OnGuard Plugin v2.0 Agents.
2. To locate the support charts for OnGuard plugin version 2.0, navigate to Administration > Support >
Documentation > OnGuard Agent Support Charts for Plugin Version 2.0.
3. The Plugin Version field in the Posture Policy > Summary tab indicates the version and related SDK as
follows (see Figure 742):
n Plugin Version 1.0: OESIS V3 SDK
n Plugin Version 2.0: OESIS V4 SDK
4. The names of some of the third-party products (for example, AntiVirus, Firewall, and Patch Management)
have changed in the OnGuard plugin version 2.0, so be sure to test the OnGuard plugin version 2.0 Service
and Posture policies in your lab before applying them in a production environment.
5. In OnGuard plugin version 2.0 Posture Policy for Windows and MacOS, AntiVirus and AntiSpyware
health classes are merged into the AntiVirus health class.
6. The following features/checks are not supported with the OnGuard plugin version 2.0:
n AntiVirus health class: Engine Version Check, Display Update URL, Disable RTP Check (see AntiVirus on
page 302).
n Patch Management health class: Selected On Server and Security options in the Install Level Check
Type (see Patch Management on page 308).
7. Note that new posture policies created on W-ClearPass Policy Manager 6.6.7 and later will be for OnGuard
plugin version 2.0: OESIS V4 SDK.
8. W-ClearPass Policy Manager 6.6.7 and later does not allow creating a new Posture Policy for OnGuard
plugin version 1.0: OESIS V4 SDK. However, you can import a Posture Policy for OnGuard plugin version 1.0
from the previously released versions of W-ClearPass.
9. Make sure that the Agent Enforcement profile has the required SDK Type configured—V3 or V4 (see
Modifying an Existing Enforcement Policy for OnGuard Plugin v2.0 on page 742).
10.Make sure to use the posture policy having Plugin Version 2.0, if V4 SDK is enabled. Similarly for V3 SDK, use
the posture policy with Plugin Version 1.0 (see Creating a New Posture Policy for OnGuard Plugin v2.0
Agents on page 743).
11.You can change the SDK Type from V4 to V3 by modifying the Agent Enforcement profile to have V3 as
the SDK Type. In this case, be sure to configure the service posture policy is set to Plugin Version 1.0 (see
Creating a New Enforcement Profile to Set the SDKType on page 740).
12.OnGuard Agent sends two WebAuth requests when the SDK Type is changed on a client. The first request
uses the previously configured SDK Type, and the second request is for the new SDK Type.
13.If an Agent Enforcement Profile without the SDK Type attribute is applied, it will not reset the SDK Type on
the client; that is, once the SDK Type is changed on the client by the Agent Enforcement profile, it will not
change until a new Agent Enforcement profile having a different SDK Type is applied.
14.If the Host:SDK Type attribute is missing in WebAuth Requests, it indicates that OnGuard Agent is using
the V3 SDK as versions prior to OnGuard Agents version 6.6.7 do not send the Host:SDK Type attribute.