mde_installer.sh not working. It always finds itself as conflicting application.

[SvenMarquardt5772]

sudo ./mde_installer.sh --install --channel prod --onboard onboarding.py --tag GROUP <generic_name> --min_req --yes
--- mde_installer.sh v0.5.9 ---
./mde_installer.sh: Zeile 369: [: -lt: Einstelliger (unärer) Operator erwartet.
[v] minimal requirements met
[>] detected: ubuntu 20.04 focal (debian)
[>] scaled: 20.04
[v] set package manager: apt
/usr/bin/wget
[final] connected=OK
[v] connected
./mde_installer.sh: Zeile 401: Warnung: Kommansosubstitution: NULL byte in der Eingabe ignoriert.
[S] MDE not installed.
[x] found conflicting applications: [/opt/microsoft/mdatp/sbin/wdavdaemon], aborting
[*] exiting (5)

The script finds its binaries and thinks that these are conflicting binaries.

Furthermore, because set -euo pipefail is not set, the script ignores some errors.

[SvenMarquardt5772]

The error with blocking its installation is the same as #51

[SvenMarquardt5772]

Resolved this with sudo ./mde_installer.sh --remove and afterwards dpkg --remove mdeatp.

[agarwalneetu]

Hi @SvenMarquardt5772, I was working on #51, and saw you mentioned #51 issue here. So, can I go assume "mdatp blocking his own installation issue" is resolved and if yes, can you please close this issue #51?

[SvenMarquardt5772]

Yes, I resolved it as described above.

[agarwalneetu]

can you please close it then issue #51, I can't close it.

---

From: SvenMarquardt5772 @.> Sent: Wednesday, January 11, 2023 12:43 PM To: microsoft/mdatp-xplat @.> Cc: Neetu Agarwal @.>; Comment @.> Subject: Re: [microsoft/mdatp-xplat] mde_installer.sh not working. It always finds itself as conflicting application. (Issue #68)

Yes, I resolved it as described above.

— Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fmdatp-xplat%2Fissues%2F68%23issuecomment-1378325932&data=05%7C01%7Cneetuagarwal%40microsoft.com%7C81e2a7f58bf14d9e3a1d08daf3a3630c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638090180336963619%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=s%2BfYzdaawt8OvKHb9NT%2Bo6ooPauhbBpLteJKTKiB%2Bgs%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA5C5JJKUEZOY6ZHWQCGNTWLWRZMSZANCNFSM6AAAAAASWURJII&data=05%7C01%7Cneetuagarwal%40microsoft.com%7C81e2a7f58bf14d9e3a1d08daf3a3630c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638090180337120274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BNVptD0cPmB8rjXfecA8EJG%2BlFuLhd%2FbunZnx6GNpKQ%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>

[agarwalneetu]

---

From: Neetu Agarwal Sent: Thursday, February 9, 2023 5:37 PM To: Deepti Bhardwaj @.>; Amit Arora @.>; Mati Goldberg @.>; Luba Zlochin @.> Subject: Onboarding failing after offboarding

Hi all,

I need your help in understanding the scenario below.

Problem Statement:

If try to onboard mdatp right after offboarding; onboarding is failing. This is happening because after offboarding, mdatp_offboard.json file is present at /etc/opt/microsoft/mdatp location which is blocking the onboarding process.

Though, this same thing is not happening during offboarding, the offboarding script automatically first delete the mdatp_onboard.json file and replaces it with mdatp_offboard.json file.

I need to understand two things:

      1. How offboarding is replacing mdatp_onboard.json file with mdatp_offboard.json file?

            I didn't find such code in the offboarding script. Also, in edr.cpp, I found that during offboarding we are only setting orgID to null and not deleting any file.

      2. What could be the possible reason that mdatp_offboard.json file is blocking onboarding and not getting deleted?

Testing:

I tested this issue on multiple vms using both manual and automatic method; it's giving the same error.

Mitigation:

Issue is getting resolved after we manually delete mdatp_offboard.json file and then onboard the device.

Thanks, Neetu