CAT Auto Pulish for Windows Release Messages - 20191002152638 (#1259)

* 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)

windows/deployment/volume-activation/activate-forest-by-proxy-vamt.md

@@ -9,7 +9,8 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: activation
-audience: itpro
+audience: itpro
+author: greg-lindsay
 ms.date: 04/25/2017
 ms.topic: article
 ---
@@ -18,13 +19,13 @@ ms.topic: article
 
 You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate by proxy an Active Directory (AD) forest for an isolated workgroup that does not have Internet access. ADBA enables certain volume products to inherit activation from the domain.
 
-
-**Important**  
+> [!IMPORTANT]
+> ADBA is only applicable to *Generic Volume License Keys (GVLKs)* and *KMS Host key (CSVLK)*. To use ADBA, one or more KMS Host keys (CSVLK) must be installed on the AD forest, and client keys (GVLKs) must be installed on the client products.
 
 In a typical proxy-activation scenario, the VAMT host computer distributes a product key to one or more client computers and collects the installation ID (IID) from each computer. The VAMT host computer sends the IIDs to Microsoft on behalf of the client computers and obtains the corresponding Confirmation IDs (CIDs). The VAMT host computer then installs the CIDs on the client computer to complete the activation. If you use this activation method, only the VAMT host computer needs to have Internet access.
 
-
-**Note**  
+> [!NOTE]
+> For workgroups that are isolated from any larger network, you can still perform an AD forest activation. This requires installing a second instance of VAMT on a computer in the isolated group and using removable media to transfer activation data between that computer and another VAMT host computer that has Internet access. You can also activate by proxy a KMS Host key (CSVLK) in the core network if you do not want the host computer to connect to Microsoft over the Internet.
 
 ## Requirements