* Added IsStub new node
* Updated tree diagram
* minor update
* Added a note
ATP doesn't need any specific diagnostic level.
Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/4824
* Update windows/security/threat-protection/microsoft-defender-atp/minimum-requirements.md
Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
* MDATP Get started 404: link Overview page instead
Description:
As reported by a new community user, the "Get started" link is broken
and causes a 404 error when trying to open that page.
As discussed in issue ticket #5053, it will be useful to make the link
point to the MDATP Overview page instead.
Proposed change:
- Rewrite the link name from
"Get started with Microsoft Defender Advanced Threat Protection" to
"Microsoft Defender Advanced Threat Protection overview"
(the name of the link can be changed depending on feedback from MS Docs
team members).
- Link the main page "Microsoft Defender Advanced Threat Protection"
instead of the non-existing "Get started" page that causes a 404 error.
issue ticket closure or reference:
Resolves#5053
* Added new IsStub node details
* Update hello-planning-guide.md + MD improvements
Description:
As agreed upon in issue ticket #4875, the line
"> This guide only applies to Windows 10, version 1511 or higher."
should be removed because it imposes an outdated build.
Thanks to mapalko for requesting this removal, and to poortom1004
for pointing out the version redundancy in the first place.
Proposed changes:
- Remove the aforementioned line, as agreed upon
- Add recommended single MarkDown quote spaces
- Replace a tab with standardized spacing
- Remove redundant white space in 3 blank lines
issue ticket closure or reference:
Closes#4875
* Updated the DDF with the latest version
* Update activate-forest-by-proxy-vamt.md
Updated markdown.
* Removed blank SKU tables for deprecated policies
* loc meta tag updates
* CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20191002143340 (#1258)
* Microsoft Defender ATP: amend broken link
The link "Get started" at the end of the page "Microsoft Defender
Advanced Threat Protection" points to a non-existing page. It may have
been renamed and the name "Get started" appropriated as one of the
expandable sections in the left hand side index/TOC section.
The suggested change is to replace the broken link `get-started.md`
with `minimum-requirements.md` found at the same directory level.
Broken link:
https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/security/threat-protection/microsoft-defender-atp/get-started.md
Replacement link:
https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/security/threat-protection/microsoft-defender-atp/minimum-requirements.md
Thanks to xNiklasJern for discovering the broken link.
Closes#4832
* Added update to run the task
Updated the document as suggested by the user to update the XML file created by GP preference.
Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/4797
* Update windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp.md
Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
* Update hello-faq.md: English grammar improvement
English grammar improvement is needed in one of the first sentences of
this document page: " but not date at this time."
Thanks to robhurt for noticing and reporting this malformed sentence.
Closes#4932
* MBAM 2.5 Service releases: add May 2019 to list
This is yet another page where the May 2019 Service release is missing
from the list of service releases of Microsoft Desktop Optimization Pack
(MDOP).
Proposed change: add May 2019 Service release at the end of the list.
Thanks to philschwan for noticing and reporting this detail.
Closes#4944
* fixed spelling error
* fixed spelling error
* CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190916173707 (#1123)
Customer pointed out that while they were following steps outlined in the article, they ran into some errors. Validation revealed that step 3 in the feature installation procedure is outdated as of Windows 10 1607. Added a note about that
