mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-27 16:23:36 +00:00
Merge pull request #4180 from nschonni/fix--MD033/no-inline-html
fix: MD033/no-inline-html
This commit is contained in:
Daniel Simpson
GitHub
@ -193,7 +193,7 @@ The DSMA is a well-known user account type.
|
||||
It is a user neutral account that can be used to run processes that are either multi-user aware or user-agnostic.
|
||||
The DSMA is disabled by default on the desktop SKUs (full windows SKUs) and WS 2016 with the Desktop.
|
||||
|
||||
The DSMA has a well-known RID of 503. The security identifier (SID) of the DSMA will thus have a well-known SID in the following format: S-1-5-21-<ComputerIdentifier>-503
|
||||
The DSMA has a well-known RID of 503. The security identifier (SID) of the DSMA will thus have a well-known SID in the following format: S-1-5-21-\<ComputerIdentifier>-503
|
||||
|
||||
The DSMA is a member of the well-known group **System Managed Accounts Group**, which has a well-known SID of S-1-5-32-581.
|
||||
|
||||
|
||||
@ -182,7 +182,7 @@ The User Portal and Mobile Application web services need to communicate with the
|
||||
|
||||
1. Open **Active Directory Users and Computers**.
|
||||
2. In the navigation pane, expand the node with the organization’s Active Directory domain name. Right-click the **Users** container, select **New**, and select **User**.
|
||||
3. In the **New Object – User** dialog box, type **PFWSDK_<computerName>** in the **First name** and **User logon name** boxes, where *<computer>* is the name of the primary MFA server running the Web Services SDK. Click **Next**.
|
||||
3. In the **New Object – User** dialog box, type **PFWSDK_\<computerName>** in the **First name** and **User logon name** boxes, where *\<computer>* is the name of the primary MFA server running the Web Services SDK. Click **Next**.
|
||||
4. Type a strong password and confirm it in the respective boxes. Clear **User must change password at next logon**. Click **Next**. Click **Finish** to create the user account.
|
||||
|
||||
#### Add the MFA SDK user account to the Phonefactor Admins group
|
||||
@ -192,7 +192,7 @@ Adding the WebServices SDK user account to the Phonefactor Admins group provides
|
||||
1. Open **Active Directory Users and Computers**.
|
||||
2. In the navigation pane, expand the node with the organization’s Active Directory domain name. Select **Users**. In the content pane. Right-click the **Phonefactor Admins** security group and select Properties.
|
||||
3. Click the Members tab.
|
||||
4. Click **Add**. Click **Object Types..** Type the PFWSDK_<computerName> user name in the **Enter the object names to select** box and then click **OK**.
|
||||
4. Click **Add**. Click **Object Types..** Type the PFWSDK_\<computerName> user name in the **Enter the object names to select** box and then click **OK**.
|
||||
* The computer account for the primary MFA Server
|
||||
* The Webservices SDK user account
|
||||
* Group or user account that will manage the User Portal server.
|
||||
@ -507,7 +507,7 @@ Sign in the primary AD FS server with _local administrator_ equivalent credentia
|
||||
|
||||
Sign in the primary AD FS server with _local administrator_ equivalent credentials.
|
||||
|
||||
Edit the **Register-MultiFactorAuthenticationAdfsAdapter.ps1** script adding `-ConfigurationFilePath <path>` to the end of the `Register-AdfsAuthenticationProvider` command where **<path>** is the full path to the **MultiFactorAuthenticationAdfsAdapter.config** file.
|
||||
Edit the **Register-MultiFactorAuthenticationAdfsAdapter.ps1** script adding `-ConfigurationFilePath <path>` to the end of the `Register-AdfsAuthenticationProvider` command where **\<path>** is the full path to the **MultiFactorAuthenticationAdfsAdapter.config** file.
|
||||
|
||||
### Run the AD FS Adapter PowerShell cmdlet
|
||||
|
||||
|
||||
@ -182,7 +182,7 @@ The User Portal and Mobile Application web services need to communicate with the
|
||||
|
||||
1. Open **Active Directory Users and Computers**.
|
||||
2. In the navigation pane, expand the node with the organization’s Active Directory domain name. Right-click the **Users** container, select **New**, and select **User**.
|
||||
3. In the **New Object – User** dialog box, type **PFWSDK_<computerName>** in the **First name** and **User logon name** boxes, where *<computer>* is the name of the primary MFA server running the Web Services SDK. Click **Next**.
|
||||
3. In the **New Object – User** dialog box, type **PFWSDK_\<computerName>** in the **First name** and **User logon name** boxes, where *\<computer>* is the name of the primary MFA server running the Web Services SDK. Click **Next**.
|
||||
4. Type a strong password and confirm it in the respective boxes. Clear **User must change password at next logon**. Click **Next**. Click **Finish** to create the user account.
|
||||
|
||||
#### Add the MFA SDK user account to the Phonefactor Admins group
|
||||
@ -192,7 +192,7 @@ Adding the WebServices SDK user account to the Phonefactor Admins group provides
|
||||
1. Open **Active Directory Users and Computers**.
|
||||
2. In the navigation pane, expand the node with the organization’s Active Directory domain name. Select **Users**. In the content pane. Right-click the **Phonefactors Admin** security group and select Properties.
|
||||
3. Click the Members tab.
|
||||
4. Click **Add**. Click **Object Types..** Type the PFWSDK_<computerName> user name in the **Enter the object names to select** box and then click **OK**.
|
||||
4. Click **Add**. Click **Object Types..** Type the PFWSDK_\<computerName> user name in the **Enter the object names to select** box and then click **OK**.
|
||||
* The computer account for the primary MFA Server
|
||||
* The Webservices SDK user account
|
||||
* Group or user account that will manage the User Portal server.
|
||||
@ -507,7 +507,7 @@ Sign in the primary AD FS server with _local administrator_ equivalent credentia
|
||||
|
||||
Sign in the primary AD FS server with _local administrator_ equivalent credentials.
|
||||
|
||||
Edit the **Register-MultiFactorAuthenticationAdfsAdapter.ps1** script adding `-ConfigurationFilePath <path>` to the end of the `Register-AdfsAuthenticationProvider` command where **<path>** is the full path to the **MultiFactorAuthenticationAdfsAdapter.config** file.
|
||||
Edit the **Register-MultiFactorAuthenticationAdfsAdapter.ps1** script adding `-ConfigurationFilePath <path>` to the end of the `Register-AdfsAuthenticationProvider` command where **\<path>** is the full path to the **MultiFactorAuthenticationAdfsAdapter.config** file.
|
||||
|
||||
### Run the AD FS Adapter PowerShell cmdlet
|
||||
|
||||
|
||||
@ -515,7 +515,7 @@
|
||||
##### [Planning and deploying advanced security audit policies](auditing/planning-and-deploying-advanced-security-audit-policies.md)
|
||||
##### [Advanced security auditing FAQ](auditing/advanced-security-auditing-faq.md)
|
||||
###### [Which editions of Windows support advanced audit policy configuration](auditing/which-editions-of-windows-support-advanced-audit-policy-configuration.md)
|
||||
###### [How to list XML elements in <EventData>](auditing/how-to-list-xml-elements-in-eventdata.md)
|
||||
###### [How to list XML elements in \<EventData>](auditing/how-to-list-xml-elements-in-eventdata.md)
|
||||
|
||||
###### [Using advanced security auditing options to monitor dynamic access control objects](auditing/using-advanced-security-auditing-options-to-monitor-dynamic-access-control-objects.md)
|
||||
####### [Monitor the central access policies that apply on a file server](auditing/monitor-the-central-access-policies-that-apply-on-a-file-server.md)
|
||||
|
||||
@ -41,7 +41,7 @@ MpCmdRun.exe [command] [-options]
|
||||
| Command | Description |
|
||||
|:--------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------|
|
||||
| \-? **or** -h | Displays all available options for this tool |
|
||||
| \-Scan [-ScanType #] [-File <path> [-DisableRemediation] [-BootSectorScan]] [-Timeout <days>] [-Cancel] | Scans for malicious software |
|
||||
| \-Scan [-ScanType #] [-File \<path> [-DisableRemediation] [-BootSectorScan]] [-Timeout \<days>] [-Cancel] | Scans for malicious software |
|
||||
| \-Trace [-Grouping #] [-Level #] | Starts diagnostic tracing |
|
||||
| \-GetFiles | Collects support information |
|
||||
| \-GetFilesDiagTrack | Same as Getfiles but outputs to temporary DiagTrack folder |
|
||||
@ -49,11 +49,11 @@ MpCmdRun.exe [command] [-options]
|
||||
| \-RemoveDefinitions [-DynamicSignatures] | Removes only the dynamically downloaded Security intelligence |
|
||||
| \-RemoveDefinitions [-Engine] | Restores the previous installed engine |
|
||||
| \-SignatureUpdate [-UNC \| -MMPC] | Checks for new Security intelligence updates |
|
||||
| \-Restore [-ListAll \| [[-Name <name>] [-All] \| [-FilePath <filePath>]] [-Path <path>]] | Restores or lists quarantined item(s) |
|
||||
| \-Restore [-ListAll \| [[-Name \<name>] [-All] \| [-FilePath \<filePath>]] [-Path \<path>]] | Restores or lists quarantined item(s) |
|
||||
| \-AddDynamicSignature [-Path] | Loads dynamic Security intelligence |
|
||||
| \-ListAllDynamicSignatures | Lists the loaded dynamic Security intelligence |
|
||||
| \-RemoveDynamicSignature [-SignatureSetID] | Removes dynamic Security intelligence |
|
||||
| \-CheckExclusion -path <path> | Checks whether a path is excluded |
|
||||
| \-CheckExclusion -path \<path> | Checks whether a path is excluded |
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -83,7 +83,7 @@ Open the Intune management portal either by searching for Intune on https://port
|
||||
1. Description: *Optional*
|
||||
1. OMA-URI: **./Vendor/MSFT/Defender/SharedSignatureRoot**
|
||||
1. Data type: **String**
|
||||
1. Value: **\\<sharedlocation>\wdav-update\** (see the [Download and unpackage](#download-and-unpackage-the-latest-updates) section for what this will be)
|
||||
1. Value: **\\<sharedlocation\>\wdav-update\** (see the [Download and unpackage](#download-and-unpackage-the-latest-updates) section for what this will be)
|
||||
1. Click **Ok** to close the details blade, then **OK** again to close the **Custom OMA-URI Settings** blade. Click **Create** to save the new profile. The profile details page now appears.
|
||||
1. Click **Assignments**. The **Include** tab is automatically selected. In the drop-down menu, select **Selected Groups**, then click **Select groups to include**. Click the **VDI test VMs** group and then **Select**.
|
||||
1. Click **Evaluate** to see how many users/devices will be impacted. If the number makes sense, click **Save**. If the number doesn’t make sense, go back to the groups blade and confirm the group contains the right users or devices.
|
||||
@ -94,7 +94,7 @@ Open the Intune management portal either by searching for Intune on https://port
|
||||
1. In the **Group Policy Management Editor** go to **Computer configuration**.
|
||||
1. Click **Administrative templates**.
|
||||
1. Expand the tree to **Windows components > Windows Defender Antivirus > Security Intelligence Updates**
|
||||
1. Double-click Define security intelligence location for VDI clients and set the option to Enabled. A field automatically appears, enter *\\<sharedlocation>\wdav-update *(see the [Download and unpackage](#download-and-unpackage-the-latest-updates) section for what this will be). Click **OK**.
|
||||
1. Double-click Define security intelligence location for VDI clients and set the option to Enabled. A field automatically appears, enter *\\<sharedlocation\>\wdav-update *(see the [Download and unpackage](#download-and-unpackage-the-latest-updates) section for what this will be). Click **OK**.
|
||||
1. Deploy the GPO to the VMs you want to test.
|
||||
|
||||
#### Use PowerShell to enable the shared security intelligence feature:
|
||||
|
||||
@ -57,8 +57,7 @@ The table in this section lists the main Windows Defender Antivirus event IDs an
|
||||
|
||||
|
||||
|
||||
<style type='text/css'> table.oridealign td,th { vertical-align: top; text-align: left; } </style>
|
||||
<table class="oridealign">
|
||||
<table>
|
||||
<tr>
|
||||
<th colspan="2" >Event ID: 1000</th>
|
||||
</tr>
|
||||
@ -2716,7 +2715,7 @@ This section provides the following information about Windows Defender Antivirus
|
||||
Use the information in these tables to help troubleshoot Windows Defender Antivirus error codes.
|
||||
|
||||
|
||||
<table class="oridealign">
|
||||
<table>
|
||||
<tr>
|
||||
<th colspan="2">Error code: 0x80508007</th>
|
||||
</tr>
|
||||
@ -2916,7 +2915,7 @@ The following error codes are used during internal testing of Windows Defender A
|
||||
If you see these errors, you can try to [update definitions](manage-updates-baselines-windows-defender-antivirus.md) and force a rescan directly on the endpoint.
|
||||
|
||||
|
||||
<table class="oridealign">
|
||||
<table>
|
||||
<tr>
|
||||
<th colspan="3">Internal error codes</th>
|
||||
</tr>
|
||||
|
||||
@ -75,5 +75,5 @@ Note that "ResetPolicyId" reverts a supplemental policy to a base policy, and re
|
||||
|
||||
### Merging policies
|
||||
|
||||
When merging, the policy type and ID of the leftmost/first policy specified is used. If the leftmost is a base policy with ID <ID>, then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID <ID>.
|
||||
When merging, the policy type and ID of the leftmost/first policy specified is used. If the leftmost is a base policy with ID \<ID>, then regardless of what the GUIDS and types are for any subsequent policies, the merged policy will be a base policy with ID \<ID>.
|
||||
|
||||
|
||||
@ -65,7 +65,7 @@ If you do not have a code signing certificate, see the [Optional: Create a code
|
||||
` Add-SignerRule -FilePath $InitialCIPolicy -CertificatePath <Path to exported .cer certificate> -Kernel -User –Update`
|
||||
|
||||
> [!NOTE]
|
||||
> <Path to exported .cer certificate> should be the full path to the certificate that you exported in step 3.
|
||||
> \<Path to exported .cer certificate> should be the full path to the certificate that you exported in step 3.
|
||||
Also, adding update signers is crucial to being able to modify or disable this policy in the future.
|
||||
|
||||
6. Use [Set-RuleOption](https://docs.microsoft.com/powershell/module/configci/set-ruleoption) to remove the unsigned policy rule option:
|
||||
|
||||
@ -27,7 +27,7 @@ Dynamic Code Security is not enabled by default because existing policies may no
|
||||
Additionally, a small number of .NET loading features, including loading unsigned assemblies built with System.Reflection.Emit, are not currently supported with Dynamic Code Security enabled.
|
||||
Microsoft recommends testing Dynamic Code Security in audit mode before enforcing it to discover whether any new libraries should be included in the policy.
|
||||
|
||||
To enable Dynamic Code Security, add the following option to the <Rules> section of your policy:
|
||||
To enable Dynamic Code Security, add the following option to the `<Rules>` section of your policy:
|
||||
|
||||
```xml
|
||||
<Rule>
|
||||
|
||||
Reference in New Issue
Block a user