| Solution | As a prerequisite, a minimum ESAP version 3.4.2 is required for supporting migration of OPSWAT SDK from v3 to v4 version. A warning message is displayed if the minimum version is not present.
By enabling the option “Enable migration of OPSWAT SDK from old to new version (V3 to V4)”, the clients start downloading the V4 SDK and migrate to newer SDK. However, the server still remains on SKDv3 version.
Customers can check if the end points have migrated to SDKv4. To do so please navigate to the below directory:
C:\Program Files (x86)\Common Files\Pulse Secure\TNC Client Plugin\OPSWAT\UnifiedSDK.ini
Open the UnifiedSDK.ini file:
[SDK]
ESAP_VERSION=3.7.4
SDK_CATEGORY=4
FILE_LIST=wa_3rd_party_host_32.exe,wa_3rd_party_host_64.exe,libwalocal.dll,libwavmodapi.dll,libwaapi.dll,libwautils.dll,libwaaddon.dll,libwaheap.dll,libwaapi_v3.dll,libwaresource.dll,vmod.dat,doSilent.txt
RUNTIME_DEPS=
Clear/Uncheck the “Enable migration of OPSWAT SDK from old to new version (V3 to V4)” option once the migration is complete.
To migrate the server from SDKv3 to SDKv4 admin can change the following option.
Uncheck “Activate Older OPSWAT SDK in ESAP for host checker policy evaluation” >> Save Changes >> Confirm the changes.
Post migration, an administrator can remap the configured products in the policies to map to the newer SDK using the Post Migration window. For example, in the below screenshot, the Product/Vendor Name for the policy has been changed from Microsoft Corp. to Microsoft Corporation for successful migration.
 |
|
|---|
