| Policy | More information
- | | Device restriction / Password policy
- | When certain DeviceLock policies, such as minimum password length and password complexity, or any similar group policy settings, including any that disable auto-logon, are applied to a device, and that device reboots during the device Enrollment Status Page (ESP), the out-of-box experience or user desktop auto-logon could fail unexpectantly.
+ |
| Device restriction / Password Policy |
+When certain DeviceLock policies, such as minimum password length and password complexity, or any similar group policy settings, including any that disable auto-logon, are applied to a device, and that device reboots during the device Enrollment Status Page (ESP), the out-of-box experience or user desktop auto-logon could fail unexpectantly. This is especially true for kiosk scenarios where passwords are automatically generated. |
+
+
Windows 10 Security Baseline / Administrator elevation prompt behavior
+
Windows 10 Security Baseline / Require admin approval mode for administrators |
+When modifying user account control (UAC) settings during the out-of-box experience (OOBE) using device Enrollment Status Page (ESP), additional UAC prompts may result, especially if the device reboots after these policies are applied enabling them to take effect. To work around this issue, the policies can be targeted to users instead of devices so that they apply later in the process. |
+
## Related topics
diff --git a/windows/security/threat-protection/microsoft-defender-atp/linux-exclusions.md b/windows/security/threat-protection/microsoft-defender-atp/linux-exclusions.md
index 5d04bf7089..2c56cd3ef7 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/linux-exclusions.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/linux-exclusions.md
@@ -64,7 +64,7 @@ For more information on how to configure exclusions from Puppet, Ansible, or ano
Run the following command to see the available switches for managing exclusions:
```bash
-$ mdatp --exclusion
+$ mdatp exclusion
```
Examples:
@@ -72,29 +72,29 @@ Examples:
- Add an exclusion for a file extension:
```bash
- $ mdatp --exclusion --add-extension .txt
- Configuration updated successfully
+ $ mdatp exclusion extension add --name .txt
+ Extension exclusion configured successfully
```
- Add an exclusion for a file:
```bash
- $ mdatp --exclusion --add-folder /var/log/dummy.log
- Configuration updated successfully
+ $ mdatp exclusion file add --path /var/log/dummy.log
+ File exclusion configured successfully
```
- Add an exclusion for a folder:
```bash
- $ mdatp --exclusion --add-folder /var/log/
- Configuration updated successfully
+ $ mdatp exclusion folder add --path /var/log/
+ Folder exclusion configured successfully
```
- Add an exclusion for a process:
```bash
- $ mdatp --exclusion --add-process cat
- Configuration updated successfully
+ $ mdatp exclusion process add --name cat
+ Process exclusion configured successfully
```
## Validate exclusions lists with the EICAR test file
diff --git a/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md b/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md
index 31656eeae6..ef65ef7094 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md
@@ -268,7 +268,7 @@ Download the onboarding package from Microsoft Defender Security Center:
Initially the client machine is not associated with an organization. Note that the *orgId* attribute is blank:
```bash
- mdatp --health orgId
+ mdatp health --field org_id
```
2. Run MicrosoftDefenderATPOnboardingLinuxServer.py, and note that, in order to run this command, you must have `python` installed on the device:
@@ -280,17 +280,20 @@ Download the onboarding package from Microsoft Defender Security Center:
3. Verify that the machine is now associated with your organization and reports a valid organization identifier:
```bash
- mdatp --health orgId
+ mdatp health --field org_id
```
4. A few minutes after you complete the installation, you can see the status by running the following command. A return value of `1` denotes that the product is functioning as expected:
```bash
- mdatp --health healthy
+ mdatp health --field healthy
```
> [!IMPORTANT]
- > When the product starts for the first time, it downloads the latest antimalware definitions. Depending on your Internet connection, this can take up to a few minutes. During this time the above command returns a value of `0`.