fedora-intune: Defender script also turns on behavior monitoring

Behavior monitoring is off by default and the repair script never
checked it, so on devices without the image's managed config (another
distro, a plain install) it stayed off and the compliance rule failed.
Enable it, and cloud-delivered protection, when they're off and not
managed.

Only start mdatp-firstboot where the image installed it; elsewhere every
run logged that first-boot setup hadn't completed and tried to start a
unit that doesn't exist.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

images/fedora-intune/intune/defender-compliance.sh

@@ -2,20 +2,26 @@
 # Intune custom compliance discovery script for Linux: is Microsoft Defender
 # for Endpoint (mdatp) installed, onboarded, licensed and protecting?
 #
-# Upload in Intune > Devices > Compliance > Scripts (Linux), and pair it with
-# defender-compliance.json in a Linux compliance policy (Custom compliance).
-# Himmelblau runs it as root inside himmelblaud-tasks.service and sends the
-# JSON on stdout to Intune, which evaluates it against the rules. Every setting
-# is always emitted, so a missing or stopped Defender reads as non-compliant
-# instead of as a script error.
+# Upload in Intune > Endpoint security > Device compliance > Scripts (Linux),
+# and pair it with defender-compliance.json in a Linux compliance policy
+# (Custom compliance). Himmelblau runs it as root inside
+# himmelblaud-tasks.service and sends the JSON on stdout to Intune, which
+# evaluates it against the rules. Every setting is always emitted, so a missing
+# or stopped Defender reads as non-compliant instead of as a script error.
 
 MDATP=/usr/bin/mdatp
 
-# Print one `mdatp health` field without quotes or a trailing " [managed]".
-# Unlicensed or unonboarded, mdatp prints "ATTENTION: ..." lines first.
+# Defender won't answer `mdatp health` started from inside himmelblaud-tasks
+# (it can't read that process while checking the caller), so ask through
+# systemd, which runs mdatp as its own child. Elsewhere, ask mdatp directly.
+health="$(systemd-run --quiet --wait --pipe --collect "${MDATP}" health 2>/dev/null)"
+grep -q '^healthy' <<< "${health}" || health="$("${MDATP}" health 2>/dev/null)"
+
+# Print one field of the `mdatp health` output ("name : value") without
+# quotes or a trailing " [managed]".
 field() {
-  "${MDATP}" health --field "$1" 2>/dev/null | grep -v '^ATTENTION' | tail -n1 \
-    | sed -e 's/ \[managed\]$//' -e 's/^"//' -e 's/"$//'
+  grep -m1 "^$1 *:" <<< "${health}" \
+    | sed -e 's/^[^:]*: *//' -e 's/ \[managed\]$//' -e 's/^"//' -e 's/"$//'
 }
 
 bool() {

images/fedora-intune/intune/defender-remediation.sh

@@ -56,7 +56,7 @@ if [[ ! -x "${MDATP}" ]]; then
 fi
 
 # The image finishes the Defender install on first boot (mdatp-firstboot).
-if [[ ! -f /var/lib/mdatp-firstboot.done ]]; then
+if [[ -x /usr/libexec/mdatp-firstboot && ! -f /var/lib/mdatp-firstboot.done ]]; then
   log "Defender first-boot setup has not completed; starting it."
   systemctl start mdatp-firstboot.service
 fi
@@ -93,18 +93,30 @@ if [[ -z "$(field org_id)" ]]; then
   fi
 fi
 
-# Settings Defender's own policy manages show " [managed]" and can't be
-# changed locally; this only fixes a locally disabled real-time protection.
+# Settings a managed config (mdatp_managed.json) sets show " [managed]" and
+# can't be changed locally; these fix devices without one, where behavior
+# monitoring is off by default. Behavior monitoring needs real-time
+# protection, so that goes first.
 if [[ "$(field real_time_protection_enabled)" != true ]]; then
   log "Real-time protection is off; enabling it."
   "${MDATP}" config real-time-protection --value enabled
 fi
 
+if [[ "$(field behavior_monitoring)" != enabled ]]; then
+  log "Behavior monitoring is off; enabling it."
+  "${MDATP}" config behavior-monitoring --value enabled
+fi
+
+if [[ "$(field cloud_enabled)" != true ]]; then
+  log "Cloud-delivered protection is off; enabling it."
+  "${MDATP}" config cloud --value enabled
+fi
+
 if [[ "$(field definitions_status)" != up_to_date ]]; then
   log "Definitions are not up to date; updating them."
   "${MDATP}" definitions update
 fi
 
 healthy="$(field healthy)"
-log "healthy=${healthy} licensed=$(field licensed) org_id=$(field org_id) rtp=$(field real_time_protection_enabled) definitions=$(field definitions_status)"
+log "healthy=${healthy} licensed=$(field licensed) org_id=$(field org_id) rtp=$(field real_time_protection_enabled) behavior_monitoring=$(field behavior_monitoring) cloud=$(field cloud_enabled) definitions=$(field definitions_status)"
 [[ "${healthy}" == true ]]