Jul 25 2021 01:06 AM - last edited on Nov 30 2021 01:41 PM by Allen
Note that starting from MDI version 2.156, we are including the 1.0 OEM version of the Npcap executable in the Sensor deployment package file.
So all you have to do is download the new package and extract the file from the ZIP archive.
The Microsoft Defender for Identity team is currently recommending that all customers deploy the Npcap driver before deploying the sensor on a domain controller or AD FS server. This will ensure that Npcap driver will be used instead of the WinPcap driver.
For more information on MDI and NPCAP, please refer to our FAQ
Jul 30 2021 07:31 AM - edited Jul 30 2021 07:47 AM
Will the auto-upgrade install the npcap driver or do we need to follow the manual procedures? Additionally is there a deadline to swap out the drivers or will defender for identity continue to support the wincap until a bug is found?
Jul 30 2021 03:05 PM
Aug 26 2021 12:34 AM
Hi @Eli Ofek ,
do we need to deploy Npcap manual for a new deployment or is the current installation package on a clean DC enough?
What is about migrations from ATA? Do we only have to deinstall the ATA sensor and install the current MDI package?
Thanks in advance
Aug 26 2021 12:55 AM
Aug 26 2021 12:59 AM
Aug 26 2021 01:19 AMSolution
Aug 31 2021 11:34 AM
Will Npcap work in Admin-only mode with Defender for Identity? Is there any documentation on securing this to only work with Defender for Identity on AD and ADFS servers?
Aug 31 2021 01:17 PM
Sep 08 2021 02:22 AM