Forum Discussion
Solved
Microsoft Defender for Identity and Npcap
Hi everyone,
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.
https://docs.microsoft.com/en-us/defend...
- Yes. you might need to plan for a reboot between winpcap and npcap, not sure.
Also, not that you might need to upgrade .net, as the Gateway worked with 4.6.1. + and the sensor needs 4.7+. and this might also need a reboot, so if you need to, it's best practice to upgrade .net separately from installing the sensor.
Thanks for the quick reply. 🙏
So my order is:
1. Deinstall ATA Agent
2. Deinstall WinPcap (if installed)
3. Install NPcap
4. Install MDI Agent
Correct?
So my order is:
1. Deinstall ATA Agent
2. Deinstall WinPcap (if installed)
3. Install NPcap
4. Install MDI Agent
Correct?
EliOfek
Microsoft
MicrosoftYes. you might need to plan for a reboot between winpcap and npcap, not sure.
Also, not that you might need to upgrade .net, as the Gateway worked with 4.6.1. + and the sensor needs 4.7+. and this might also need a reboot, so if you need to, it's best practice to upgrade .net separately from installing the sensor.
Also, not that you might need to upgrade .net, as the Gateway worked with 4.6.1. + and the sensor needs 4.7+. and this might also need a reboot, so if you need to, it's best practice to upgrade .net separately from installing the sensor.
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?
- EliOfekNo, please use the exact install parameters in the docs.
Admin only mode will fail and might even cause hangs.- We just learned that a reboot after deinstalling the ATA agent is needed to allow the MDI installation. We had no winpcap installed and .Net was already >4.7 so I can't comment if there are additional reboots needed.
