Merge pull request #6832 from MicrosoftDocs/main

Publish 02/16/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/configmgr/comanage/how-to-prepare-Win10.md

@@ -5,7 +5,7 @@ description: Learn how to prepare your Windows internet-based devices for co-man
 author: mestew
 ms.author: mstewart
 manager: dougeby
-ms.date: 10/05/2021
+ms.date: 02/16/2022
 ms.topic: how-to
 ms.prod: configuration-manager
 ms.technology: configmgr-comanage
@@ -77,26 +77,26 @@ Decide which command-line properties you require for your environment:
 
 - The following command-line properties are required in all scenarios:
 
-  - **CCMHOSTNAME**
+  - `CCMHOSTNAME`
 
-  - **SMSSITECODE**
+  - `SMSSITECODE`
 
 - If a device uses Azure AD for client authentication and also has a PKI-based client authentication certificate, specify the following properties to use Azure AD:<!-- MEMDocs#1483 -->
 
-  - **AADCLIENTAPPID**
+  - `AADCLIENTAPPID`
 
-  - **AADRESOURCEURI**
+  - `AADRESOURCEURI`
 
-- If the client roams back to the intranet, use the **SMSMP** property.
+- If the client roams back to the intranet, use the `SMSMP` property.
 
-- If you use your own PKI certificate, and your CRL isn't published to the internet, use the **/NoCRLCheck** parameter. For more information, see [About client installation properties: /NoCRLCheck](../core/clients/deploy/about-client-installation-properties.md#nocrlcheck).
+- If you use your own PKI certificate, and your CRL isn't published to the internet, use the `/NoCRLCheck` parameter. For more information, see [About client installation properties: /NoCRLCheck](../core/clients/deploy/about-client-installation-properties.md#nocrlcheck).
 
   > [!IMPORTANT]
   > Microsoft recommends publishing the CRL. For more information, see [Planning for CRLs](../core/plan-design/security/plan-for-certificates.md#pki-certificate-revocation).<!-- memdocs#1942 -->
 
-- To bootstrap a task sequence immediately after client registration, use the **PROVISIONTS** property. For more information, see [About client installation properties: PROVISIONTS](../core/clients/deploy/about-client-installation-properties.md#provisionts).
+- To bootstrap a task sequence immediately after client registration, use the `PROVISIONTS` property. For more information, see [About client installation properties: PROVISIONTS](../core/clients/deploy/about-client-installation-properties.md#provisionts).
 
-The site publishes other Azure AD information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it's joined. This behavior further simplifies enrolling devices to co-management in an environment with more than one Azure AD tenant. The only two required ccmsetup properties are **CCMHOSTNAME** and **SMSSITECODE**.<!--3607731-->
+The site publishes other Azure AD information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it's joined. This behavior further simplifies enrolling devices to co-management in an environment with more than one Azure AD tenant. The only two required ccmsetup properties are `CCMHOSTNAME` and `SMSSITECODE`.<!--3607731-->
 
 > [!NOTE]
 > If you're already deploying the Configuration Manager client from Intune, update the Intune app with a new command line and new MSI.<!-- SCCMDocs-pr issue 3084 -->

memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md

@@ -2,7 +2,7 @@
 title: Client settings
 titleSuffix: Configuration Manager
 description: Learn about the default and custom settings for controlling client behaviors
-ms.date: 01/11/2022
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: reference
@@ -458,7 +458,7 @@ Choose one of the following options for this setting:
 > [!IMPORTANT]
 > The client always permits software installations from Software Center, regardless of the metered internet connection settings. If the user requests a software installation while the device is on a metered network, Software Center honors the user's intent.<!-- MEMDocs#285 -->
 
-Client install and update both work when you configure this client setting to **Allow** or **Limit**. This behavior allows the client to stay current, but still manage the client communication on a metered network. You can control this behavior during client install with the ccmsetup parameter **/AllowMetered**. For more information, see [About client installation parameters and properties](../../clients/deploy/about-client-installation-properties.md#allowmetered).<!--6976145-->
+Client install and update both work when you configure this client setting to **Allow** or **Limit**. This behavior allows the client to stay current, but still manage the client communication on a metered network. You can control this behavior during client install with the ccmsetup parameter `/AllowMetered`. For more information, see [About client installation parameters and properties](../../clients/deploy/about-client-installation-properties.md#allowmetered).<!--6976145-->
 
 ## Power management  
 

memdocs/configmgr/core/clients/deploy/about-client-settings.md

@@ -2,7 +2,7 @@
 title: Install the client with Azure AD
 titleSuffix: Configuration Manager
 description: Install and assign the Configuration Manager client on Windows devices using Azure Active Directory for authentication
-ms.date: 10/01/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: conceptual
@@ -88,18 +88,18 @@ The following example shows the general structure of the command line:
 
 For more information, see [Client installation properties](about-client-installation-properties.md).
 
-The **/mp** parameter and **CCMHOSTNAME** property specify one of the following, depending upon the scenario:
+The `/mp` parameter and `CCMHOSTNAME` property specify one of the following, depending upon the scenario:
 
-- On-premises management point. Only specify the **/mp** parameter. The **CCMHOSTNAME** property isn't required.
+- On-premises management point. Only specify the `/mp` parameter. The `CCMHOSTNAME` property isn't required.
 - Cloud management gateway
 - Internet-based management point
 
-The **SMSMP** property specifies the on-premises management point. It's not required. It's recommended for Azure AD-joined devices that roam onto the intranet, so they can find an on-premises management point.
+The `SMSMP` property specifies the on-premises management point. It's not required. It's recommended for Azure AD-joined devices that roam onto the intranet, so they can find an on-premises management point.
 
 This example uses a cloud management gateway. It replaces sample values:
 `ccmsetup.exe /mp:https://CONTOSO.CLOUDAPP.NET/CCM_Proxy_MutualAuth/72186325152220500 CCMHOSTNAME=CONTOSO.CLOUDAPP.NET/CCM_Proxy_MutualAuth/72186325152220500 SMSSITECODE=ABC SMSMP=https://mp1.contoso.com AADTENANTID=daf4a1c2-3a0c-401b-966f-0b855d3abd1a AADCLIENTAPPID=7506ee10-f7ec-415a-b415-cd3d58790d97 AADRESOURCEURI=https://contososerver`
 
-The site publishes additional Azure AD information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it's joined. This behavior further simplifies installing the client in an environment with more than one Azure AD tenant. The only two required ccmsetup properties are **CCMHOSTNAME** and **SMSSITECODE**.<!--3607731-->
+The site publishes additional Azure AD information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it's joined. This behavior further simplifies installing the client in an environment with more than one Azure AD tenant. The only two required ccmsetup properties are `CCMHOSTNAME` and `SMSSITECODE`.<!--3607731-->
 
 To automate the client install using Azure AD identity via Microsoft Intune, see [How to prepare internet-based devices for co-management](../../../comanage/how-to-prepare-Win10.md#install-the-configuration-manager-client).
 

memdocs/configmgr/core/clients/deploy/deploy-clients-cmg-azure.md

@@ -2,7 +2,7 @@
 title: Token-based authentication for CMG
 titleSuffix: Configuration Manager
 description: Register a client on the internal network for a unique token or create a bulk registration token for internet-based devices.
-ms.date: 07/23/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: conceptual
@@ -63,7 +63,7 @@ To create a bulk registration token for use during client installation on intern
 
 1. Copy the token and save it in a secure location.
 
-1. Install the Configuration Manager client on an internet-based device. Include the client installation parameter: [**/regtoken**](about-client-installation-properties.md#regtoken). The following example command line includes the other required setup parameters and properties:
+1. Install the Configuration Manager client on an internet-based device. Include the client installation parameter: [`/regtoken`](about-client-installation-properties.md#regtoken). The following example command line includes the other required setup parameters and properties:
 
     `ccmsetup.exe /mp:https://CONTOSO.CLOUDAPP.NET/CCM_Proxy_MutualAuth/72186325152220500 CCMHOSTNAME=CONTOSO.CLOUDAPP.NET/CCM_Proxy_MutualAuth/72186325152220500 SMSSiteCode=ABC /regtoken:eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik9Tbzh2Tmd5VldRUjlDYVh5T2lacHFlMDlXNCJ9.eyJTQ0NNVG9rZW5DYXRlZ29yeSI6IlN7Q01QcmVBdXRoVG9rZW4iLCJBdXRob3JpdHkiOiJTQ0NNIiwiTGljZW5zZSI6IlNDQ00iLCJUeXBlIjoiQnVsa1JlZ2lzdHJhdGlvbiIsIlRlbmFudElkIjoiQ0RDQzVFOTEtMEFERi00QTI0LTgyRDAtMTk2NjY3RjFDMDgxIiwiVW5pcXVlSWQiOiJkYjU5MWUzMy1wNmZkLTRjNWItODJmMy1iZjY3M2U1YmQwYTIiLCJpc3MiOiJ1cm46c2NjbTpvYXV0aDI6Y2RjYzVlOTEtMGFkZi00YTI0LTgyZDAtMTk2NjY3ZjFjMDgxIiwiYXVkIjoidXJuOnNjY206c2VydmljZSIsImV4cCI6MTU4MDQxNbUwNSwibmJmIjoxNTgwMTU2MzA1fQ.ZUJkxCX6lxHUZhMH_WhYXFm_tbXenEdpgnbIqI1h8hYIJw7xDk3wv625SCfNfsqxhAwRwJByfkXdVGgIpAcFshzArXUVPPvmiUGaxlbB83etUTQjrLIk-gvQQZiE5NSgJ63LCp5KtqFCZe8vlZxnOloErFIrebjFikxqAgwOO4i5ukJdl3KQ07YPRhwpuXmwxRf1vsiawXBvTMhy40SOeZ3mAyCRypQpQNa7NM3adCBwUtYKwHqiX3r1jQU0y57LvU_brBfLUL6JUpk3ri-LSpwPFarRXzZPJUu4-mQFIgrMmKCYbFk3AaEvvrJienfWSvFYLpIYA7lg-6EVYRcCAA`
 
@@ -94,13 +94,13 @@ The `BulkRegistrationTokenTool.exe` tool is in the `\bin\X64` folder of the Conf
 - `/new`
 - `/lifetime`
 
-#### /?
+#### `/?`
 
 Display this usage information.
 
 Example: `BulkRegistrationTokenTool.exe /?`
 
-#### /new
+#### `/new`
 
 Create a new bulk registration token.
 
@@ -114,7 +114,7 @@ The tool displays the following information:
 
 The token isn't stored on the client or the site. Make sure to copy the token from the command prompt, and store in a secure location.
 
-#### /lifetime
+#### `/lifetime`
 
 Use with `/new` parameter to specify the token validity period of the token. Specify an integer value in minutes. The default value is 4,320 (three days). The maximum value is 10,080 (seven days).
 

memdocs/configmgr/core/clients/deploy/deploy-clients-cmg-token.md

@@ -2,7 +2,7 @@
 title: Azure AD authentication workflow
 titleSuffix: Configuration Manager
 description: Details of the Configuration Manager client installation process on a Windows device with Azure Active Directory (Azure AD) authentication.
-ms.date: 07/15/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: reference
@@ -32,7 +32,7 @@ In this workflow sample, you installed the Configuration Manager client on a Win
 
 ### 1. Azure AD info request from ccmsetup
 
-Clients installed from internet need specific command-line properties to use Azure AD authentication. You can include these properties in the command line for [internet ccmsetup](../../../comanage/how-to-prepare-win10.md#install-the-configuration-manager-client), but they aren't required. When you don't use Azure AD properties, ccmsetup requests the **AADCLIENTAPPID** and **AADRESOURCEURI** properties from the cloud management gateway (CMG). It uses the device's Azure AD TenantID as a reference. If you haven't onboarded the client's TenantID in Configuration Manager, the CMG doesn't give the required properties to ccmsetup to continue client installation.
+Clients installed from internet need specific command-line properties to use Azure AD authentication. You can include these properties in the command line for [internet ccmsetup](../../../comanage/how-to-prepare-win10.md#install-the-configuration-manager-client), but they aren't required. When you don't use Azure AD properties, ccmsetup requests the `AADCLIENTAPPID` and `AADRESOURCEURI` properties from the cloud management gateway (CMG). It uses the device's Azure AD TenantID as a reference. If you haven't onboarded the client's TenantID in Configuration Manager, the CMG doesn't give the required properties to ccmsetup to continue client installation.
 
 The following entries are logged in **ccmsetup.log** of the client:
 
@@ -46,7 +46,7 @@ Enabled SSL revocation check.
 > [!IMPORTANT]
 > During ccmsetup, the device has to validate the CMG server authentication certificate. The root certificate authority (CA) certificate for the CMG server authentication certificate needs to be available on the client for the chain validation. If you use PKI, when the root CA isn't published on the internet, add the root CA certificate to the device's root CAs store.
 >
-> If the root CA certificate revocation list (CRL) isn't published on internet, add the **/nocrlcheck** parameter in the ccmsetup command line.
+> If the root CA certificate revocation list (CRL) isn't published on internet, add the `/nocrlcheck` parameter in the ccmsetup command line.
 
 ### 2. Azure AD token request
 
@@ -262,7 +262,7 @@ Message '{BD03DEED-D09A-4E63-ADAD-596376FFB0DA}' got reply message '{36EE3A78-8F
 
 - Root CA not present: Clients need the root CA certificate to validate the CMG server authentication certificate.
 
-- CRL check is enabled: Publish the CRL on the internet. As an alternative, use the **/NoCRLCheck** parameter for ccmsetup. You can also disable the following option: **Clients check the certificate revocation list (CRL) for site systems**. Find this setting on the **Communication Security** tab of the site properties.
+- CRL check is enabled: Publish the CRL on the internet. As an alternative, use the `/NoCRLCheck` parameter for ccmsetup. You can also disable the following option: **Clients check the certificate revocation list (CRL) for site systems**. Find this setting on the **Communication Security** tab of the site properties.
 
 - The WPJ certificate isn't found: Make sure the device is Azure AD-joined. Use [dsregcmd.exe](/azure/active-directory/devices/troubleshoot-device-dsregcmd). For example, `dsregcmd /status` and look at the **Device State** section.
 

memdocs/configmgr/core/clients/manage/azure-ccmsetup.md

@@ -2,7 +2,7 @@
 title: Configure clients for CMG
 titleSuffix: Configuration Manager
 description: Understand how to configure clients to use the cloud management gateway (CMG).
-ms.date: 08/02/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: how-to
@@ -56,7 +56,7 @@ There are two methods to install the Configuration Manager client on devices tha
 
 - The first method is to use a bulk registration token to install the client on a device. For more information on this method, see [Create a bulk registration token](../../deploy/deploy-clients-cmg-token.md#bulk-registration-token).
 
-- For the second method, when you run **ccmsetup.exe**, use the **/mp** parameter to specify the CMG's URL. For more information, see [About client installation parameters and properties](../../deploy/about-client-installation-properties.md#mp). This method requires one of the following conditions:
+- For the second method, when you run **ccmsetup.exe**, use the `/mp` parameter to specify the CMG's URL. For more information, see [About client installation parameters and properties](../../deploy/about-client-installation-properties.md#mp). This method requires one of the following conditions:
 
   - The Configuration Manager site is properly configured to use PKI certificates for client authentication. Additionally, the client systems each have a valid, unique, and trusted client authentication certificate previously issued to them.
 

memdocs/configmgr/core/clients/manage/cmg/configure-clients.md

@@ -2,7 +2,7 @@
 title: Manage clients
 titleSuffix: Configuration Manager
 description: Learn how to manage clients in Configuration Manager.
-ms.date: 12/01/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: conceptual
@@ -241,7 +241,7 @@ For more information, see [Configure the client content cache](configure-client-
 
 ## Uninstall the client
 
-You can uninstall the Configuration Manager client software from a computer by using **CCMSetup.exe** with the **/Uninstall** property. Run CCMSetup.exe on an individual computer from the command prompt, or deploy a package to uninstall the client for a collection of computers.
+You can uninstall the Configuration Manager client software from a computer by using **CCMSetup.exe** with the `/Uninstall` property. Run CCMSetup.exe on an individual computer from the command prompt, or deploy a package to uninstall the client for a collection of computers.
 
 > [!NOTE]
 > You can't uninstall the Configuration Manager client from a mobile device. If you must remove the Configuration Manager client from a mobile device, you must wipe the device, which deletes all data on the mobile device.

memdocs/configmgr/core/clients/manage/manage-clients.md

@@ -2,7 +2,7 @@
 title: Exclude client upgrades for Windows
 titleSuffix: Configuration Manager
 description: Learn how to exclude Windows clients from getting upgraded in Configuration Manager.
-ms.date: 07/23/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: how-to
@@ -53,7 +53,7 @@ If a device is a member of a collection that you excluded from upgrade, you can
 
 - **Client push installation**: Ccmsetup allows client push installation because it's your direct intent. This method lets you upgrade a client without removing it from the collection, or removing the entire collection from exclusion.
 
-- **Manual client installation**: Manually upgrade an excluded client by using the following Ccmsetup command-line parameter: **/IgnoreSkipUpgrade**
+- **Manual client installation**: Manually upgrade an excluded client by using the following Ccmsetup command-line parameter: `/IgnoreSkipUpgrade`
 
     If you attempt to manually upgrade a client that's a member of the excluded collection, and don't use this parameter, the client doesn't upgrade. For more information, see [How to install Configuration Manager clients manually](../../deploy/deploy-clients-to-windows-computers.md#BKMK_Manual).
 

memdocs/configmgr/core/clients/manage/upgrade/exclude-clients-windows.md

@@ -2,7 +2,7 @@
 title: Ports used for connections
 titleSuffix: Configuration Manager
 description: Learn about the required and customizable network ports that Configuration Manager uses for connections.
-ms.date: 12/21/2021
+ms.date: 02/16/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: reference
@@ -679,7 +679,7 @@ The following sections provide more information about ports that Configuration M
 
 Clients use Server Message Block (SMB) whenever they connect to UNC shares. For example:
 
-- Manual client installation that specifies the CCMSetup.exe **/source:** command-line property
+- Manual client installation that specifies the CCMSetup.exe `/source:` command-line property
 
 - Endpoint Protection clients that download definition files from a UNC path