From a9bbc179f0ec7fbe1b4bb630c2814324804d9113 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Fri, 7 Jun 2019 15:34:07 -0700 Subject: [PATCH] fixing note and important spacing --- ...ert-a-package-created-in-a-previous-version-of-appv.md | 4 ++-- ...s-running-on-a-stand-alone-computer-with-powershell.md | 2 +- ...appv-publish-a-packages-with-the-management-console.md | 2 +- .../app-v/appv-sequence-a-package-with-powershell.md | 2 +- .../administrative-tools-in-windows-10.md | 2 +- .../bulk-enrollment-using-windows-provisioning-tool.md | 2 +- windows/client-management/mdm/reboot-csp.md | 2 +- windows/client-management/mdm/windowslicensing-csp.md | 8 ++++---- 8 files changed, 12 insertions(+), 12 deletions(-) diff --git a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md index da84cc0efd..606d358e12 100644 --- a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md +++ b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md @@ -54,8 +54,8 @@ The App-V package converter will save the App-V 4.6 installation root folder and Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default. - > [!NOTE] - >Before you specify the output directory, you must create the output directory. +> [!NOTE] + >Before you specify the output directory, you must create the output directory. ### Advanced Conversion Tips diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 4912088722..f0f0b0ad03 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -59,7 +59,7 @@ Publish-AppvClientPackage "ContosoApplication" -Global ## Publish a package to a specific user -> [!NOTE]   +> [!NOTE] > You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter. An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID). diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index a849c0e86f..47e033fcbe 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -18,7 +18,7 @@ ms.topic: article Use the following procedure to publish an App-V package. Once you publish a package, computers running the App-V client can access and run the applications in that package. -> [!NOTE]   +> [!NOTE] > The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3. ## Publish an App-V package diff --git a/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md b/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md index 232685092a..1ccb908974 100644 --- a/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md +++ b/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md @@ -20,7 +20,7 @@ ms.author: lomayor Use the following procedure to create a new App-V package using Windows PowerShell. -> [!NOTE]   +> [!NOTE] > Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). diff --git a/windows/client-management/administrative-tools-in-windows-10.md b/windows/client-management/administrative-tools-in-windows-10.md index 131690f8f4..84c3b8c3d2 100644 --- a/windows/client-management/administrative-tools-in-windows-10.md +++ b/windows/client-management/administrative-tools-in-windows-10.md @@ -51,7 +51,7 @@ These tools were included in previous versions of Windows and the associated doc - [Windows Firewall with Advanced Security](https://go.microsoft.com/fwlink/p/?LinkId=708503) - [Windows Memory Diagnostic]( https://go.microsoft.com/fwlink/p/?LinkId=708507) -> [!TIP]   +> [!TIP] > If the content that is linked to a tool in the following list doesn't provide the information you need to use that tool, send us a comment by using the **Was this page helpful?** feature on this **Administrative Tools in Windows 10** page. Details about the information you want for a tool will help us plan future content.  ## Related topics diff --git a/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md b/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md index 10dc639f90..955a7207d1 100644 --- a/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md +++ b/windows/client-management/mdm/bulk-enrollment-using-windows-provisioning-tool.md @@ -32,7 +32,7 @@ On the desktop, you can create an Active Directory account, such as "enrollment@ On the desktop and mobile devices, you can use an enrollment certificate or enrollment username and password, such as "enroll@contoso.com" and "enrollmentpassword." These credentials are used in the provisioning package, which you can use to enroll multiple devices to the MDM service. Once the devices are joined, many users can use them. -> [!NOTE]   +> [!NOTE] > - Bulk-join is not supported in Azure Active Directory Join. > - Bulk enrollment does not work in Intune standalone environment. > - Bulk enrollment works in System Center Configuration Manager (SCCM) + Intune hybrid environment where the ppkg is generated from the SCCM console. diff --git a/windows/client-management/mdm/reboot-csp.md b/windows/client-management/mdm/reboot-csp.md index 227a21008a..71315bdf56 100644 --- a/windows/client-management/mdm/reboot-csp.md +++ b/windows/client-management/mdm/reboot-csp.md @@ -29,7 +29,7 @@ The following diagram shows the Reboot configuration service provider management **RebootNow**

This node executes a reboot of the device. RebootNow triggers a reboot within 5 minutes to allow the user to wrap up any active work.

-> [!Note]   +> [!NOTE] > If this node is set to execute during a sync session, the device will reboot at the end of the sync session.

The supported operations are Execute and Get.

diff --git a/windows/client-management/mdm/windowslicensing-csp.md b/windows/client-management/mdm/windowslicensing-csp.md index 0aa177f8cf..544ed62a02 100644 --- a/windows/client-management/mdm/windowslicensing-csp.md +++ b/windows/client-management/mdm/windowslicensing-csp.md @@ -31,7 +31,7 @@ The supported operation is Get. **UpgradeEditionWithProductKey** Enters a product key for an edition upgrade of Windows 10 desktop devices. -> [!NOTE]   +> [!NOTE] > This upgrade process requires a system restart. @@ -97,7 +97,7 @@ The supported operation is Get. **UpgradeEditionWithLicense** Provides a license for an edition upgrade of Windows 10 mobile devices. -> [!NOTE]   +> [!NOTE] > This upgrade process does not require a system restart. @@ -216,7 +216,7 @@ Values: ``` -> [!NOTE]   +> [!NOTE] > `XXXXX-XXXXX-XXXXX-XXXXX-XXXXX` in the **Data** tag should be replaced with your product key. @@ -297,7 +297,7 @@ Values: ``` -> [!NOTE]   +> [!NOTE] > `XXXXX-XXXXX-XXXXX-XXXXX-XXXXX` in the **Data** tag should be replaced with your product key.