Https checking P0 items from CATS report: https://contentqacats.azure…

…websites.net/CheckResults/2019090300007/Report/

ThirdPartyNotices

@@ -7,7 +7,7 @@ see the [LICENSE](LICENSE) file, and grant you a license to any code in the repo
 Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
 may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
 The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
-Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
+Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653.
 
 Privacy information can be found at https://privacy.microsoft.com/en-us/
 

sccm/apps/deploy-use/learn-script-security.md

@@ -64,7 +64,7 @@ Best practices for preventing malicious parameters or script injection are:
 
 ## Environment Recommendations
 General recommendations for PowerShell administrators.
-1. Deploy latest version of PowerShell, such as version 5 or greater, built into Windows 10. Alternatively, you can deploy the [Windows Management Framework](https://www.microsoft.com/en-us/download/details.aspx?id=54616), available down to, and including Windows 7 and Windows Server 2008 R2. 
+1. Deploy latest version of PowerShell, such as version 5 or greater, built into Windows 10. Alternatively, you can deploy the [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=54616), available down to, and including Windows 7 and Windows Server 2008 R2. 
 2. Enable, and collect PowerShell logs, optionally including Protected Event Logging. Incorporate these logs into your signatures, hunting, and incident response workflows.
 3. Implement Just Enough Administration on high-value systems to eliminate or reduce unconstrained administrative access to those systems.
 4. Deploy Device Guard/Application Control policies to allow pre-approved administrative tasks to use the full capability of the PowerShell language, while limiting interactive and unapproved use to a limited subset of the PowerShell language.

sccm/apps/deploy-use/management-tasks-applications.md

@@ -35,7 +35,7 @@ For help creating applications and deployment types, see [Create applications](.
 |**Update Statistics**|Updates the information that is displayed in the **Deployments** node of the **Monitoring** workspace about the deployments of this application.<br /><br /> See [Monitor applications from the System Center Configuration Manager console](../../apps/deploy-use/monitor-applications-from-the-console.md).|  
 |**Reinstate**|Reinstates an application that was retired by using the **Retire** management task.|  
 |**Retire**|When you retire an application, it is no longer available for deployment, but the application and deployments of the application are not deleted. Existing copies of this application that were installed on client computers will not be removed. Any revisions to the application will be deleted from Configuration Manager after 60 days. But, installed copies of the application are not removed.<br /><br /> To delete an application, you must first retire the application, delete all deployments, remove references to the application by other deployments, and then delete all of the application's revisions.<br /><br /> See [Revise and supersede applications](../../apps/deploy-use/revise-and-supersede-applications.md).|  
-|**Export**|Opens the **Export Application Wizard** that lets you export the selected applications to a .zip file that you can then archive or install on another site. If you choose to export application content, a folder that has the content will be created.<br /><br /> You can also export application dependencies, supersedence relationships and conditions, and content for the application and its dependencies.<br /><br /> The Windows PowerShell cmdlet, **Export-CMApplication**, does the same function. For more information, see [Export-CMApplication](http://go.microsoft.com/fwlink/p/?LinkID=258880) in the Microsoft System Center 2012 Configuration Manager SP1 cmdlet reference documentation.|  
+|**Export**|Opens the **Export Application Wizard** that lets you export the selected applications to a .zip file that you can then archive or install on another site. If you choose to export application content, a folder that has the content will be created.<br /><br /> You can also export application dependencies, supersedence relationships and conditions, and content for the application and its dependencies.<br /><br /> The Windows PowerShell cmdlet, **Export-CMApplication**, does the same function. For more information, see [Export-CMApplication](https://go.microsoft.com/fwlink/p/?LinkID=258880) in the Microsoft System Center 2012 Configuration Manager SP1 cmdlet reference documentation.|  
 |**Delete**|Deletes the currently selected application.<br /><br /> You cannot delete an application if other applications are dependent on it, if it has an active deployment, or if it has dependent task sequences.|  
 |**Simulate Deployment**|Opens the **Simulate Application Deployment Wizard** where you can test the results of an application deployment to computers without installing or uninstalling the application.<br /><br /> See [Simulate application deployments](../../apps/deploy-use/simulate-application-deployments.md).|  
 |**Deploy**|Opens the **Deploy Software Wizard** where you can deploy the selected application to collections of computers in your hierarchy.<br /><br /> See [Deploy applications](../../apps/deploy-use/deploy-applications.md).|  

sccm/apps/get-started/deploying-app-v-virtual-applications.md

@@ -53,7 +53,7 @@ In addition to the other System Center Configuration Manager requirements and pr
 
 -   **App-V 4.6**: To use virtual applications in Configuration Manager, client computers must have the App-V 4.6 SP1, App-V 4.6 SP2, or App-V 4.6 SP3 client installed.  
 
-     Before you can successfully deploy virtual applications, you must also update the App-V 4.6 SP1 client with the hotfix that is described in the Knowledge Base article [2645225](http://go.microsoft.com/fwlink/p/?LinkId=237322).  
+     Before you can successfully deploy virtual applications, you must also update the App-V 4.6 SP1 client with the hotfix that is described in the Knowledge Base article [2645225](https://go.microsoft.com/fwlink/p/?LinkId=237322).  
 
 -   **App-V 5, App-V 5.0 SP1, App-V 5.0 SP2, App-V 5.0 SP3, and App-V 5.1**: For App-V 5.0 SP2, you must install [Hotfix Package 5](https://support.microsoft.com/en-us/kb/2963211) or use App-V 5.0 SP3.  
 -   **App-V 5.2**: This is built into Windows 10 Education (1607 and later), Windows 10 Enterprise (1607 and later), and Windows Server 2016.

sccm/compliance/deploy-use/import-configuration-data.md

@@ -24,7 +24,7 @@ In addition to creating configuration baselines and configuration items in the S
 
 - Configuration data that was externally authored and that conforms to the SML schema.  
 
-  For an example Configuration Pack that helps you manage compliance for System Center 2012 Configuration Manager site server roles, see [System Center 2012 Configuration Manager Configuration Pack](http://www.microsoft.com/en-us/download/details.aspx?id=30710&WT.mc_id=rss_alldownloads_all).  
+  For an example Configuration Pack that helps you manage compliance for System Center 2012 Configuration Manager site server roles, see [System Center 2012 Configuration Manager Configuration Pack](https://www.microsoft.com/download/details.aspx?id=30710&WT.mc_id=rss_alldownloads_all).  
 
 When you import a configuration baseline, some or all of the configuration items that are referenced in the configuration baseline might also be included in the cabinet file. During the import process, Configuration Manager verifies that all of the configuration items that are referenced in the configuration baseline are either also included in the cabinet file or already exist in the Configuration Manager site. The import process fails if you attempt to import a configuration baseline that references configuration data that Configuration Manager cannot locate.  
 

sccm/compliance/plan-design/scap/about-scap.md

@@ -148,11 +148,11 @@ The SCAP extensions for Configuration Manager include Windows command-line tools
 
 - The command-line parameters `-help` and `-?` for each tool print the usage to the screen. These usage details are then available to screen readers and other assistive technology.  
 
-- For more information, see [Windows Accessibility](http://windows.microsoft.com/windows/help/accessibility).
+- For more information, see [Windows Accessibility](https://windows.microsoft.com/windows/help/accessibility).
 
 The SCAP extensions also make use of accessibility features in Configuration Manager. For more information, see [Accessibility features in Configuration Manager](/sccm/core/understand/accessibility-features).
 
-For more information about Microsoft accessibility products and services, see the [Microsoft Accessibility website](http://go.microsoft.com/fwlink/p/?LinkId=9212).
+For more information about Microsoft accessibility products and services, see the [Microsoft Accessibility website](https://go.microsoft.com/fwlink/p/?LinkId=9212).
 
 
 

sccm/compliance/plan-design/scap/install-configure-scap.md

@@ -46,10 +46,10 @@ Depending on your environment, you may not need all the SCAP data stream files l
 
 ### Install the SCAP data streams
 
-1. Visit the [NVD Web site](http://nvd.nist.gov/) to identify the SCAP data streams that are required by your organization.
+1. Visit the [NVD Web site](https://nvd.nist.gov/) to identify the SCAP data streams that are required by your organization.
 The SCAP data streams published by NIST are organized into multiple bundles, which are also called _checklists_.  
 
-2. Download the SCAP data streams from the [NVD Web site](http://nvd.nist.gov/home.cfm), which are stored in compressed files with a .zip file name extension or marked as DataStream XML file.  
+2. Download the SCAP data streams from the [NVD Web site](https://nvd.nist.gov/home.cfm), which are stored in compressed files with a .zip file name extension or marked as DataStream XML file.  
 
     > [!IMPORTANT]  
     > There are many SCAP data stream files with the .xml extension that you can download from the NVD. However, only .xml files that include XCCDF (SCAP1.0 and 1.1)/DataStream (SCAP1.2) content are appropriate for use with the SCAP extensions.  

sccm/core/clients/deploy/deploy-clients-to-unix-and-linux-servers.md

@@ -32,7 +32,7 @@ Before you can manage a Linux or UNIX server with Configuration Manager, you mus
  After you install the client, you specify Client Settings in the Configuration Manager console to configure the client agent in the same way you would Windows-based clients. For more information, see  [Client settings for Linux and UNIX servers](../../../core/clients/manage/manage-clients-for-linux-and-unix-servers.md#BKMK_ClientSettingsforLnU).  
 
 ##  <a name="BKMK_AboutInstallPackages"></a> About client installation packages and the universal agent  
- To install the client for Linux and UNIX on a specific platform, you must use the applicable client installation package for the computer where you install the client. Applicable client installation packages are included as part of each client download from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the **install** script that manages the installation of the client on each computer.  
+ To install the client for Linux and UNIX on a specific platform, you must use the applicable client installation package for the computer where you install the client. Applicable client installation packages are included as part of each client download from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184). In addition to client installation packages, the client download includes the **install** script that manages the installation of the client on each computer.  
 
  When you install a client, you can use the same process and command-line properties regardless of the client installation package you use.  
 

sccm/core/clients/deploy/plan/planning-for-client-deployment-to-windows-embedded-devices.md

@@ -41,11 +41,11 @@ ms.collection: M365-identity-device-management
 
  Configuration Manager supports managing the following types of write filters:  
 
-- File-Based Write Filter (FBWF) -  For more information, see [File-Based Write Filter](http://go.microsoft.com/fwlink/?LinkID=204717).  
+- File-Based Write Filter (FBWF) -  For more information, see [File-Based Write Filter](https://go.microsoft.com/fwlink/?LinkID=204717).  
 
-- Enhanced Write Filter (EWF) RAM - For more information, see [Enhanced Write Filter](http://go.microsoft.com/fwlink/?LinkId=204718).  
+- Enhanced Write Filter (EWF) RAM - For more information, see [Enhanced Write Filter](https://go.microsoft.com/fwlink/?LinkId=204718).  
 
-- Unified Write Filter (UWF) - For more information, see [Unified Write Filter](http://go.microsoft.com/fwlink/?LinkId=309236).  
+- Unified Write Filter (UWF) - For more information, see [Unified Write Filter](https://go.microsoft.com/fwlink/?LinkId=309236).  
 
   Configuration Manager does not support write filter operations when the Windows Embedded device is in EWF RAM Reg mode.  
 

sccm/core/clients/deploy/prepare-to-deploy-mac-clients.md

@@ -23,7 +23,7 @@ Follow these steps to make sure that you're ready to [deploy the Configuration M
 
 ## Mac prerequisites
 
-The Mac client installation package isn't supplied with the Configuration Manager media. Download the **Clients for additional operating systems** from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkID=525184).  
+The Mac client installation package isn't supplied with the Configuration Manager media. Download the **Clients for additional operating systems** from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkID=525184).  
 
 For the list of supported versions, see [Supported operating systems for clients and devices](/sccm/core/plan-design/configs/supported-operating-systems-for-clients-and-devices#mac-computers).
 

sccm/core/clients/manage/asset-intelligence/configuring-asset-intelligence.md

@@ -134,7 +134,7 @@ In addition to downloading new Asset Intelligence catalog information, the Asset
 4.  On the **Import** page, specify whether you are importing a Microsoft Volume Licensing (MVLS) file (.xml or .csv) or a General License Statement file (.csv). For more information about creating a General License Statement file, see [Create a general license statement information file for import](#BKMK_CreateGeneralLicenseStatement) later in this topic.  
 
     > [!WARNING]  
-    >  To download an MVLS file in .csv format that you can import to the Asset Intelligence catalog, see [Microsoft Volume Licensing Service Center](http://go.microsoft.com/fwlink/p/?LinkId=226547). To access this information, you must have a registered account on the website. You must contact your Microsoft account representative for information about how to get your MVLS file in .xml format.  
+    >  To download an MVLS file in .csv format that you can import to the Asset Intelligence catalog, see [Microsoft Volume Licensing Service Center](https://go.microsoft.com/fwlink/p/?LinkId=226547). To access this information, you must have a registered account on the website. You must contact your Microsoft account representative for information about how to get your MVLS file in .xml format.  
 
 5.  Enter the UNC path to the license statement file or choose **Browse** to select a network shared folder and file.  
 

sccm/core/clients/manage/asset-intelligence/prerequisites-for-asset-intelligence.md

@@ -37,4 +37,4 @@ Asset Intelligence in System Center Configuration Manager has external dependenc
 |Hardware Inventory Client Agent Dependencies|To collect inventory data required for some Asset Intelligence reports, the Hardware Inventory Client Agent must be enabled. In addition, some hardware inventory reporting classes that Asset Intelligence reports depend on must be enabled on primary site server computers.<br /><br /> For information about enabling the Hardware Inventory Client Agent, see [How to extend hardware inventory in System Center Configuration Manager](../../../../core/clients/manage/inventory/extend-hardware-inventory.md).|  
 |Software Metering Client Agent Dependencies|A number of Asset Intelligence software reports depend on the Software Metering Client Agent for data. For information about enabling the Software Metering Client Agent, see [Monitor app usage with software metering in System Center Configuration Manager](../../../../apps/deploy-use/monitor-app-usage-with-software-metering.md).<br /><br /> The following Asset Intelligence reports depend on the Software Metering Client Agent to provide data:<br /><br /> -   Software 07A - Recently Used Executables by Number of Computers<br />-   Software 07B - Computers that Recently Used a Specified Executable<br />-   Software 07C - Recently Used Executables on a Specific Computer<br />-   Software 08A - Recently Used Executables by Number of Users<br />-   Software 08B - Users that Recently Used a Specified Executable<br />-   Software 08C - Recently Used Executables by a Specified User|  
 |Asset Intelligence Hardware Inventory Reporting Class Prerequisites|Asset Intelligence reports in Configuration Manager depend on specific hardware inventory reporting classes. Until the hardware inventory reporting classes are enabled and clients have reported hardware inventory based on these classes, the associated Asset Intelligence reports do not contain any data. You can enable the following hardware inventory reporting classes to support Asset Intelligence reporting requirements:<br /><br /> -   SMS_SystemConsoleUsage<sup>1</sup><br />-   SMS_SystemConsoleUser<sup>1</sup><br />-   SMS_InstalledSoftware<br />-   SMS_AutoStartSoftware<br />-   SMS_BrowserHelperObject<br />-   Win32_USBDevice<br />-   SMS_InstalledExecutable<br />-   SMS_SoftwareShortcut<br />-   SoftwareLicensingService<br />-   SoftwareLicensingProduct<br />-   SMS_SoftwareTag<br /><br /> <sup>1</sup> By default, the **SMS_SystemConsoleUsage** and **SMS_SystemConsoleUser** Asset Intelligence hardware inventory reporting classes are enabled.<br /><br /> You can edit the Asset Intelligence hardware inventory reporting classes in the Configuration Manager console, in the **Assets and Compliance** workspace, when you click the **Asset Intelligence** node. For more information, see the [Enable Asset Intelligence hardware inventory reporting classes](../../../../core/clients/manage/asset-intelligence/configuring-asset-intelligence.md#BKMK_EnableAssetIntelligence) section in the [Configuring Asset Intelligence in System Center Configuration Manager](../../../../core/clients/manage/asset-intelligence/configuring-asset-intelligence.md) topic.|  
-|Reporting services point|The reporting services point site system role must be installed before software updates reports can be displayed. For more information about creating a reporting services point, see [Configuring Reporting in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=232661).|  
+|Reporting services point|The reporting services point site system role must be installed before software updates reports can be displayed. For more information about creating a reporting services point, see [Configuring Reporting in Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=232661).|