Merge pull request #7264 from MicrosoftDocs/main

Publish 04/05/2022, 10:30 AM

Author: v-dihans

.openpublishing.redirection.json

@@ -924,15 +924,20 @@
             "redirect_document_id": false
         },
         {
-            "source_path": "windows-365/end-user-access-cloud-pc.md",
-            "redirect_url":"/windows-365/enterprise/end-user-access-cloud-pc",
+            "source_path": "windows-365/enterprise/end-user-access-cloud-pc.md",
+            "redirect_url":"windows-365/end-user-access-cloud-pc",
             "redirect_document_id": false
         },
         {
-            "source_path": "windows-365/end-user-hardware-requirements.md",
-            "redirect_url":"/windows-365/enterprise/end-user-hardware-requirements",
+            "source_path": "windows-365/enterprise/end-user-hardware-requirements.md",
+            "redirect_url":"windows-365/end-user-hardware-requirements",
             "redirect_document_id": false
-        },
+        },                
+        {
+            "source_path": "windows-365/business/get-users-started.md",
+            "redirect_url":"/windows-365/get-users-started",
+            "redirect_document_id": false
+        },                        
         {
             "source_path": "windows-365/get-cloud-pc-audit-logs-using-powershell.md",
             "redirect_url":"/windows-365/enterprise/get-cloud-pc-audit-logs-using-powershell",
@@ -1094,4 +1099,4 @@
             "redirect_document_id": true
         }
     ]
-}
+}

memdocs/autopilot/windows-autopilot-hybrid.md

@@ -126,10 +126,13 @@ The Intune Connector requires the [same endpoints as Intune](../intune/fundament
 4. Open the downloaded Connector setup file, *ODJConnectorBootstrapper.exe*, to install the Connector.
 5. At the end of the setup, select **Configure**.
 6. Select **Sign In**.
-7. Enter the user Global Administrator or Intune Administrator role credentials. 
+7. Enter the Global administrator or Intune administrator role credentials. 
  The user account must have an assigned Intune license.
 8. Go to **Devices** > **Windows** > **Windows enrollment** > **Intune Connector for Active Directory**, and then confirm that the connection status is **Active**.
 
+> [!NOTE]
+> The Global administrator role is a temporary requirement at the time of installation.
+
 > [!NOTE]
 > After you sign in to the Connector, it might take a couple of minutes to appear in the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). It appears only if it can successfully communicate with the Intune service.
 
@@ -204,6 +207,7 @@ Here is a list of VPN clients that are known to be tested and validated:
 - Checkpoint (Win32 client)
 - Citrix NetScaler (Win32 client)
 - SonicWall (Win32 client)
+- FortiClient VPN (Win32 client)
 
 **Not supported clients:**
 - UWP-based VPN plug-ins
@@ -246,9 +250,10 @@ It takes about 15 minutes for the device profile status to change from *Not assi
     - **Name**: Enter a descriptive name for the new profile.
     - **Description**: Enter a description for the profile.
     - **Platform**: Select **Windows 10 and later**.
-    - **Profile type**: Select **Domain Join**.
-3. Select **Settings**, and then provide a **Computer name prefix**, **Domain name**.
-4. (Optional) Provide an **Organizational unit** (OU) in [DN format](/windows/desktop/ad/object-names-and-identities#distinguished-name). Your options include:
+    - **Profile type**: Select **Templates**, choose the template name **Domain Join** and select **Create**.
+3. Enter the **Name** and **Description** and select **Next**. 
+5. Provide a **Computer name prefix** and **Domain name**.
+6. (Optional) Provide an **Organizational unit** (OU) in [DN format](/windows/desktop/ad/object-names-and-identities#distinguished-name). Your options include:
     - Provide an OU in which you've delegated control to your Windows 2016 device that is running the Intune Connector.
     - Provide an OU in which you've delegated control to the root computers in your on-prem Active Directory.
     - If you leave this blank, the computer object will be created in the Active Directory default container (CN=Computers if you never [changed it](https://support.microsoft.com/help/324949/redirecting-the-users-and-computers-containers-in-active-directory-dom)).

memdocs/configmgr/develop/core/clients/remote-control/how-to-configure-remote-tools-settings.md

@@ -1,6 +1,7 @@
 ---
 title: "Configure Remote Tools Settings"
 titleSuffix: "Configuration Manager"
+description: "Learn how to use the Remote Tools Client Agent settings by modifying the necessary site control file settings."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/core/servers/configure/how-to-configure-active-directory-group-discovery.md

@@ -1,6 +1,7 @@
 ---
 title: "Configure Active Directory Group Discovery"
 titleSuffix: "Configuration Manager"
+description: "Learn how to configure the Active Directory Group Discovery settings by modifying the necessary site control file settings."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/osd/how-to-create-a-configuration-manager-custom-action-control.md

@@ -1,6 +1,7 @@
 ---
 title: "Create a Custom Action Control"
 titleSuffix: "Configuration Manager"
+description: "Learn how to create a custom action control in Configuration Manager."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/core/clients/client-classes/compliance-settings--dcm--client-interfaces.md

@@ -1,6 +1,7 @@
 ---
 title: "Compliance Settings Client Interfaces"
 titleSuffix: "Configuration Manager"
+description: "Learn about the configuration management COM automation classes and related types used by client applications to manage configuration items on the client computer."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/core/clients/client-classes/iappmanagementhandler--enforceapp-method.md

@@ -1,6 +1,7 @@
 ---
 title: "IAppManagementHandler::EnforceApp"
 titleSuffix: "Configuration Manager"
+description: "A method that starts the installation of a specific application."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/core/clients/sdk/ccm_userlogonevents-client-wmi-class.md

@@ -1,6 +1,7 @@
 ---
 title: "CCM_UserLogonEvents Class"
 titleSuffix: "Configuration Manager"
+description: "A client class that represents a user logon event."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/core/clients/sdk/getmachinepolicy-method-in-class-ccm_clientutilities.md

@@ -1,6 +1,7 @@
 ---
 title: "GetMachinePolicy Method"
 titleSuffix: "Configuration Manager"
+description: "A Windows Management Instrumentation class method that gets and evaluates the machine policy for a client device."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/core/servers/configure/getfeaturestate-method-in-class-sms_site.md

@@ -1,6 +1,7 @@
 ---
 title: "GetFeatureState Method"
 titleSuffix: "Configuration Manager"
+description: "A Windows Management Instrumentation class method that gets the enabled and disabled state of a feature."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk