From c779c0bd373caae9b8508dda36089543c679e307 Mon Sep 17 00:00:00 2001 From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Date: Wed, 5 Oct 2022 18:18:05 -0400 Subject: [PATCH] More link fixes --- .../{understand => mdm}/eap-configuration.md | 0 .../understand/appv-deploy-and-config.md | 56 +++++++++---------- ...ollment-using-windows-provisioning-tool.md | 12 ++-- 3 files changed, 34 insertions(+), 34 deletions(-) rename windows/client-management/{understand => mdm}/eap-configuration.md (100%) diff --git a/windows/client-management/understand/eap-configuration.md b/windows/client-management/mdm/eap-configuration.md similarity index 100% rename from windows/client-management/understand/eap-configuration.md rename to windows/client-management/mdm/eap-configuration.md diff --git a/windows/client-management/understand/appv-deploy-and-config.md b/windows/client-management/understand/appv-deploy-and-config.md index a407704b93..a43ea26b6c 100644 --- a/windows/client-management/understand/appv-deploy-and-config.md +++ b/windows/client-management/understand/appv-deploy-and-config.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.technology: windows author: vinaypamnani-msft ms.date: 06/26/2017 -ms.reviewer: +ms.reviewer: manager: aaroncz --- @@ -21,7 +21,7 @@ manager: aaroncz ### EnterpriseAppVManagement CSP node structure -[EnterpriseAppVManagement CSP reference](./enterpriseappvmanagement-csp.md) +[EnterpriseAppVManagement CSP reference](../mdm/enterpriseappvmanagement-csp.md) The following example shows the EnterpriseAppVManagement configuration service provider in tree format. @@ -72,7 +72,7 @@ EnterpriseAppVManagement

Sync command:

-[App-V Sync protocol reference]( https://msdn.microsoft.com/enus/library/mt739986.aspx) +[App-V Sync protocol reference](https://msdn.microsoft.com/enus/library/mt739986.aspx)

AppVDynamicPolicy - A read/write node that contains the App-V dynamic configuration for an MDM device (applied globally to all users for that device) or a specific MDM user.

@@ -85,7 +85,7 @@ EnterpriseAppVManagement

Dynamic policy examples:

-[Dynamic configuration processing](/windows/application-management/app-v/appv-application-publishing-and-client-interaction#bkmk-dynamic-config">Dynamic configuration processing) +[Dynamic configuration processing](/windows/application-management/app-v/appv-application-publishing-and-client-interaction#dynamic-configuration-processing)

AppVPackageManagement - Primarily read-only App-V package inventory data for MDM servers to query current packages.

@@ -114,9 +114,9 @@ EnterpriseAppVManagement

A complete list of App-V policies can be found here:

-[ADMX-backed policy reference](./policy-configuration-service-provider.md) +[ADMX-backed policy reference](../mdm/policy-configuration-service-provider.md) -[EnterpriseAppVManagement CSP reference](./enterpriseappvmanagement-csp.md) +[EnterpriseAppVManagement CSP reference](../mdm/enterpriseappvmanagement-csp.md) ### SyncML examples @@ -147,24 +147,24 @@ EnterpriseAppVManagement

This example shows how to allow package scripts to run during package operations (publish, run, and unpublish). Allowing package scripts helps package deployments (add and publish of App-V apps).

```xml - - $CmdID$ - - - chr - text/plain - - - ./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowPackageScripts - - - - + + $CmdID$ + + + chr + text/plain + + + ./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowPackageScripts + + + + ```

Complete list of App-V policies can be found here:

-[Policy CSP](./policy-configuration-service-provider.md) +[Policy CSP](../mdm/policy-configuration-service-provider.md) #### SyncML with package published for a device (global to all users for that device) @@ -199,11 +199,11 @@ EnterpriseAppVManagement - + - + ```

*PackageUrl can be a UNC or HTTP/HTTPS endpoint.

@@ -236,7 +236,7 @@ EnterpriseAppVManagement [{ProgramFilesX86}]\Skype\Phone\Skype.exe [{Windows}]\Installer\{FC965A47-4839-40CA-B61818F486F042C6}\SkypeIcon.exe.0.ico - [{ProgramFilesX86}]\Skype\ + [{ProgramFilesX86}]\Skype\ Skype.Desktop.Application Launch Skype 1 @@ -339,8 +339,8 @@ EnterpriseAppVManagement - -``` + +``` #### SyncML for publishing mixed-mode connection group containing global and user-published packages @@ -403,7 +403,7 @@ EnterpriseAppVManagement - + @@ -419,7 +419,7 @@ EnterpriseAppVManagement - + ``` #### Unpublish example SyncML for all global packages @@ -481,5 +481,5 @@ EnterpriseAppVManagement ./User/Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement?list=StructData - + ``` \ No newline at end of file diff --git a/windows/client-management/understand/bulk-enrollment-using-windows-provisioning-tool.md b/windows/client-management/understand/bulk-enrollment-using-windows-provisioning-tool.md index c54261ccfa..5eb73f4203 100644 --- a/windows/client-management/understand/bulk-enrollment-using-windows-provisioning-tool.md +++ b/windows/client-management/understand/bulk-enrollment-using-windows-provisioning-tool.md @@ -1,10 +1,10 @@ --- title: Bulk enrollment description: Bulk enrollment is an efficient way to set up a large number of devices to be managed by an MDM server without the need to reimage the devices. In Windows 10 and Windows 11. -MS-HAID: +MS-HAID: - 'p\_phdevicemgmt.bulk\_enrollment' - 'p\_phDeviceMgmt.bulk\_enrollment\_using\_Windows\_provisioning\_tool' -ms.reviewer: +ms.reviewer: manager: aaroncz ms.author: vinpa ms.topic: article @@ -16,7 +16,7 @@ ms.date: 06/26/2017 # Bulk enrollment -Bulk enrollment is an efficient way to set up a large number of devices to be managed by an MDM server without the need to reimage the devices. In Windows 10 and 11 desktop devices, you can use the [Provisioning CSP](provisioning-csp.md) for bulk enrollment, except for the Azure Active Directory Join (Cloud Domain Join) enrollment scenario. +Bulk enrollment is an efficient way to set up a large number of devices to be managed by an MDM server without the need to reimage the devices. In Windows 10 and 11 desktop devices, you can use the [Provisioning CSP](../mdm/provisioning-csp.md) for bulk enrollment, except for the Azure Active Directory Join (Cloud Domain Join) enrollment scenario. ## Typical use cases @@ -69,9 +69,9 @@ Using the WCD, create a provisioning package using the enrollment information re - **EnrollmentServiceFullUrl** - Optional and in most cases, it should be left blank. - **PolicyServiceFullUrl** - Optional and in most cases, it should be left blank. - **Secret** - Password - For detailed descriptions of these settings, see [Provisioning CSP](provisioning-csp.md). + For detailed descriptions of these settings, see [Provisioning CSP](../mdm/provisioning-csp.md). Here's the screenshot of the WCD at this point. - + ![bulk enrollment screenshot.](images/bulk-enrollment.png) 9. Configure the other settings, such as the Wi-Fi connections so that the device can join a network before joining MDM (for example, **Runtime settings** > **ConnectivityProfiles** > **WLANSetting**). 10. When you're done adding all the settings, on the **File** menu, click **Save**. @@ -118,7 +118,7 @@ Using the WCD, create a provisioning package using the enrollment information re - **EnrollmentServiceFullUrl** - Optional and in most cases, it should be left blank. - **PolicyServiceFullUrl** - Optional and in most cases, it should be left blank. - **Secret** - the certificate thumbprint. - For detailed descriptions of these settings, see [Provisioning CSP](provisioning-csp.md). + For detailed descriptions of these settings, see [Provisioning CSP](../mdm/provisioning-csp.md). 8. Configure the other settings, such as the Wi-Fi connection so that the device can join a network before joining MDM (for example, **Runtime settings** > **ConnectivityProfiles** > **WLANSetting**). 9. When you're done adding all the settings, on the **File** menu, click **Save**. 10. Export and build the package (steps 10-13 in the procedure above).