NetScaler customers gateway check their version of the EPA installed software is the same as that installed on the NetScaler appliance. And any changes in version NetScaler, even a minor construction changes, ask the customer to download and install the new client software. The aim is to ensure that remote users always have the current and compatible client software. However, it is not always necessary. And when the customer fails to install because the user is not authorized local administrative privileges (set of privileges) to the workstation, this can create a real headache for the support and deny access to users .
Good news ... you can control the check version EPAs with AppExpert policy
There are several advantages to this change with AppExpert instead of hand editing the policy EPA file system:
- changes are persistent between reboots
- archiving and documentation are simplified because the change is stored in the configuration rather than a separate system file
- policies AppExpert extend the flexibility to better define when and to whom, the changes are applicable
- Several versions of the amendment may exist to facilitate the disparate use cases simultaneously
- and Rollback troubleshooting is easier because the source files remain unchanged
Configuration
add the action of EPA-NoCheckA insert_before_all rewriting "HTTP.RES.BODY (14000)" q / "nsversion epaPlugin.getEPAVersion = ();"! + " N" / -search "text (" if (epaPlugin.getEPAVersion () = nsversion) ")" -bypassSafetyCheck YES
add the rewriting action EPA-NoCheckB insert_before_all "HTTP.RES.BODY ( 14000) "q /" nsversion epaActiveX.getEPAVersion = (); " " N" / text + -search "(" if (epaActiveX.getEPAVersion ()! = Nsversion) ")" -bypassSafetyCheck YES
add EPA-A rewrite policy "HTTP.REQ.URL.PATH .EQ ( "/ epa / epa.html ") "EPA-NoCheckA
add EPA-B rewriting policy" HTTP.REQ.URL.PATH.EQ ( "/ epa / epa.html " ) "EPA-NoCheckB
bind rewrite global EPA-A 100 -type NEXT RES_DEFAULT
bind rewrite global EPA 110-B type NEXT RES_DEFAULT
what he does
source file location system: /netscaler/ns_gui/epa/epa.html
Whenever HTTP.REQ.URL.PATH.EQ ( "/ epa / epa.html")
it inserts a directive that tells the client that the build number NetScaler exactly matches the version customers by inserting nsversion epaActiveX.getEPAVersion = ();
and nsversion epaPlugin.getEPAVersion = ();
What the EPA
Endpoint analysis is a process that scans a user device and detects information such as the presence and level of a system operating version and the antivirus, firewall, or Web browser software. You can use endpoint analysis to verify that the user device meets your requirements before allowing it to connect to your network and stay connected after users connect. You can monitor files, processes and registry entries on the user's device when the user's session to ensure that the device continues to meet requirements.
Warnings
If you do not see the change take place, check built Caching delivers a cached copy.
Thanks
Special thanks to Adam M. Fabian W. B. and Jeff for their contribution to this solution.
0 Komentar