McAfee Endpoint (ePO) Security offers various endpoint security solutions to managed devices. This article provides best practices recommendations to ensure smooth interoperability of Netskope Client and McAfee Endpoint Security installed in a managed device.
Recommended Reading
We recommend that you read these articles to gain a better understanding of how Client works and its interoperability with 3rd party apps.
This best practices and configurations are based on the following product versions.
McAfee Endpoint Security: 10.7
Netskope Client: 120.0.0
Microsoft Windows 10
Interoperability Configuration Requirements
We recommend the following configuration requirement to ensure Netskope Client is able to steer traffic to Netskope cloud and also allow McAfee to process their traffic without any conflicts.
Configurations in McAfee ePO Console
Default policies in McAfee ePO does not introduce restrictions on Netskope Client traffic. However, when creating a new policy ensure that the ports 80 and 443 are enabled and allowed in the McAfee Security Firewall rules.
Note
HTTP/HTTPS traffic (via 80 and 443) is enabled and allowed in default firewall policy
Login to McAfee MVISION ePO.
From the top menu bar, click Policy Catalog.
From the Products list, select Endpoint Security Firewall.
Client New Policy button.
For the new policy
Select Category.
Select McAfee Default for Create a policy based on this existing policy option.
Give a Name for the policy and Click OK to complete this step.
In the list of Rules, click the Edit button of the policy that you created.
Under Firewall Rules, expand Web/FTP. In the Remote Port column, ensure that ports 80, 443 are Enabled and Allowed for outbound HTTP/HTTPS traffic.
Note
If the ports are not allowed or enabled, click the Edit button open the Edit Rule page to select the Allow option listed under Actions and select Enable rule under Status.
Click Save. This process ensures that the Netskope Client can steer traffic from the managed device to Netskope cloud.
Configuration in Netskope Tenant WebUI
In the Netskope tenant WebUI, add McAfee Agent as a certificate pinned app exception and add a set of McAfee URLs as domain exception to the appropriate steering configuration.
Ati Es1000 Driver Windows Server — 2016 Top
The Ultimate Guide to the ATI ES1000 Driver on Windows Server 2016: Top Solutions & Best Practices
Introduction: The Legacy Challenge
In the world of enterprise IT, compatibility often walks a fine line between cutting-edge software and reliable legacy hardware. The ATI ES1000 is a perfect example. This venerable graphics chipset, originally launched in the mid-2000s, is frequently found on server motherboards from major brands like HP (ProLiant G5 series), Dell (PowerEdge 1950/2950), and Supermicro.
(also known as the RN50) is an aged graphics controller commonly found in older enterprise systems like the Dell PowerEdge SC1430 or HP ProLiant series, modern operating systems like Windows Server 2016 do not provide "in-box" native support for it. The Challenge of Legacy Compatibility ati es1000 driver windows server 2016 top
About the Author: Server hardware and driver compatibility specialist. Focused on extending the lifecycle of enterprise hardware through software optimization. The Ultimate Guide to the ATI ES1000 Driver
Working solutions (tested in real server labs)
1. Best: Use built-in VGA/SVGA console
If this is a headless server or used via iLO/iDRAC/IPMI, don’t bother – the basic driver is fine. Open Device Manager
Locate the Driver: Look for a 64-bit version of the ATI ES1000 driver. A reliable source is often the Dell or HPE ProLiant legacy archives for earlier Windows versions.
Open Device Manager.
Right-click the display adapter (it might show as "Video Controller (VGA Compatible)").
Select Update Driver.
Select Browse my computer for drivers.
Select Let me pick from a list of available drivers on my computer.
Click Have Disk.
Point to the folder containing the .inf files (e.g., CIS#1.inf or similar names inside the extracted folder).
Select ATI ES1000 from the list and click Next.
Running modern operating systems on legacy server hardware like the HP ProLiant G5 series often presents a major hurdle: display drivers. If you’ve just finished a fresh install of Windows Server 2016, you’ve likely noticed your resolution is locked at 1024 x 768 and identified as a "Microsoft Basic Display Adapter".
Interoperability Validation
Netskope Client Functions
Netskope Client is validated to work smoothly with McAfee ePO. To view the validation tests for Netskope Client, see Netskope Client Interoperability
McAfee Functions
McAfee functions were validated by executing the following tasks:
Security status of all products were verified to be up to date (OK) from the McAfee Mctray.
Security packages (V2 DAT, Extra DAT) updated successfully the McAfee agent.
Successfully installed McAfee ePO in the device that already had Netskope Client.
McAfee ePO console displayed appropriate status when McAfee products where uninstalled from devices.
