From 37679304a5da763e2cf098fed2da21682b8e88c0 Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Mon, 17 Jun 2019 00:20:24 -0400 Subject: [PATCH] chore: Replace "syntax" with code fence language --- .../support-for-client-reporting-over-http.md | 2 +- ...he-connection-group-virtual-environment.md | 2 +- ...-connection-group-virtual-environment51.md | 2 +- ...ation-publishing-and-client-interaction.md | 14 +++---- ...ion-publishing-and-client-interaction51.md | 14 +++---- ...ng-microsoft-office-2013-by-using-app-v.md | 4 +- ...-microsoft-office-2013-by-using-app-v51.md | 4 +- ...-microsoft-office-2016-by-using-app-v51.md | 4 +- ...y-using-the-dart-recovery-image-dart-10.md | 2 +- ...rs-using-the-dart-recovery-image-dart-7.md | 2 +- ...by-using-the-dart-recovery-image-dart-8.md | 2 +- .../release-notes-for-mbam-20-mbam-2.md | 2 +- .../mbam-25-security-considerations.md | 2 +- .../mdm/alljoynmanagement-csp.md | 6 +-- .../mdm/applocker-ddf-file.md | 2 +- .../client-management/mdm/applocker-xsd.md | 2 +- .../mdm/appv-deploy-and-config.md | 18 ++++---- .../mdm/assignedaccess-csp.md | 26 ++++++------ .../mdm/assignedaccess-ddf.md | 2 +- .../client-management/mdm/bitlocker-csp.md | 42 +++++++++---------- .../additional-mitigations.md | 2 +- 21 files changed, 78 insertions(+), 78 deletions(-) diff --git a/mdop/appv-v4/support-for-client-reporting-over-http.md b/mdop/appv-v4/support-for-client-reporting-over-http.md index 85014b79b4..1afa6d3679 100644 --- a/mdop/appv-v4/support-for-client-reporting-over-http.md +++ b/mdop/appv-v4/support-for-client-reporting-over-http.md @@ -34,7 +34,7 @@ The client starts collecting data when it receives a “REPORTING=”TRUE””a The following schema gives specific details of the package and the application data that is sent to the server. -``` syntax +```xml diff --git a/mdop/appv-v5/about-the-connection-group-virtual-environment.md b/mdop/appv-v5/about-the-connection-group-virtual-environment.md index 34358bc9b5..d8d9974471 100644 --- a/mdop/appv-v5/about-the-connection-group-virtual-environment.md +++ b/mdop/appv-v5/about-the-connection-group-virtual-environment.md @@ -38,7 +38,7 @@ The connection group that is used is based on the order in which a package appea Consider the following example section: -``` syntax +```xml ``` diff --git a/mdop/appv-v5/about-the-connection-group-virtual-environment51.md b/mdop/appv-v5/about-the-connection-group-virtual-environment51.md index 4e889a147b..3489f151b7 100644 --- a/mdop/appv-v5/about-the-connection-group-virtual-environment51.md +++ b/mdop/appv-v5/about-the-connection-group-virtual-environment51.md @@ -38,7 +38,7 @@ The connection group that is used is based on the order in which a package appea Consider the following example section: -``` syntax +```xml ``` diff --git a/mdop/appv-v5/application-publishing-and-client-interaction.md b/mdop/appv-v5/application-publishing-and-client-interaction.md index 17dee15c45..b19f40b8e8 100644 --- a/mdop/appv-v5/application-publishing-and-client-interaction.md +++ b/mdop/appv-v5/application-publishing-and-client-interaction.md @@ -811,7 +811,7 @@ This document focuses on App-V Full Infrastructure solutions. For specific infor The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md) or utilize the PowerShell: -``` syntax +```powershell get-command *appv* ``` @@ -1174,7 +1174,7 @@ The short cut is one of the basic elements of integration with the OS and is the From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section similar to the following: -``` syntax +```xml [{Common Desktop}]\Adobe Reader 9.lnk @@ -1194,7 +1194,7 @@ As mentioned previously, the App-V shortcuts are placed by default in the user The App-V Client manages the local operating system File Type Associations during publishing, which enables users to use file type invocations or to open a file with a specifically registered extension (.docx) to start an App-V application. File type associations are present in the manifest and dynamic configuration files as represented in the example below: -``` syntax +```xml @@ -1323,7 +1323,7 @@ App-V supports specific software clients and application capabilities extension Example of software client registration of an App-V based mail client. -``` syntax +```xml @@ -1510,7 +1510,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio **Manifest** -``` syntax +```xml [{Common Programs}]\7-Zip\7-Zip File Manager.lnk @@ -1522,7 +1522,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio **Deployment Configuration** -``` syntax +```xml @@ -1537,7 +1537,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio **User Configuration** -``` syntax +```xml diff --git a/mdop/appv-v5/application-publishing-and-client-interaction51.md b/mdop/appv-v5/application-publishing-and-client-interaction51.md index 66b1ace5e5..7188685403 100644 --- a/mdop/appv-v5/application-publishing-and-client-interaction51.md +++ b/mdop/appv-v5/application-publishing-and-client-interaction51.md @@ -811,7 +811,7 @@ This document focuses on App-V Full Infrastructure solutions. For specific infor The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md) or utilize the PowerShell: -``` syntax +```powershell get-command *appv* ``` @@ -1174,7 +1174,7 @@ The short cut is one of the basic elements of integration with the OS and is the From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section similar to the following: -``` syntax +```xml [{Common Desktop}]\Adobe Reader 9.lnk @@ -1194,7 +1194,7 @@ As mentioned previously, the App-V shortcuts are placed by default in the user The App-V Client manages the local operating system File Type Associations during publishing, which enables users to use file type invocations or to open a file with a specifically registered extension (.docx) to start an App-V application. File type associations are present in the manifest and dynamic configuration files as represented in the example below: -``` syntax +```xml @@ -1323,7 +1323,7 @@ App-V supports specific software clients and application capabilities extension Example of software client registration of an App-V based mail client. -``` syntax +```xml @@ -1510,7 +1510,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio **Manifest** -``` syntax +```xml [{Common Programs}]\7-Zip\7-Zip File Manager.lnk @@ -1522,7 +1522,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio **Deployment Configuration** -``` syntax +```xml @@ -1537,7 +1537,7 @@ The example below shows the combination of the Manifest, Deployment Configuratio **User Configuration** -``` syntax +```xml diff --git a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md index cd697fed7c..0c1c022bae 100644 --- a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md +++ b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md @@ -227,7 +227,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file: - ``` syntax + ```xml @@ -688,7 +688,7 @@ To exclude specific Office applications (for example, Access and InfoPath) when 5. Add the Office 2013 App-V Package with the new Deployment Configuration File. - ``` syntax + ```xml InfoPath Filler 2013 diff --git a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md index a5afa4ef90..ec2a4316b5 100644 --- a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md +++ b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md @@ -229,7 +229,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file: - ``` syntax + ```xml @@ -696,7 +696,7 @@ To exclude specific Office applications (for example, Access and InfoPath) when 5. Add the Office 2013 App-V Package with the new Deployment Configuration File. - ``` syntax + ```xml InfoPath Filler 2013 diff --git a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md index e13e27d1f9..b90fa7c2e2 100644 --- a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md +++ b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md @@ -222,7 +222,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file: - ``` syntax + ```xml @@ -633,7 +633,7 @@ You may want to disable specific applications in your Office App-V package. For 5. Add the Office 2016 App-V Package with the new Deployment Configuration File. - ``` syntax + ```xml Lync 2016 diff --git a/mdop/dart-v10/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-10.md b/mdop/dart-v10/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-10.md index 1b7f39a897..2a8e35021d 100644 --- a/mdop/dart-v10/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-10.md +++ b/mdop/dart-v10/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-10.md @@ -138,7 +138,7 @@ A file is provided that is named inv32.xml and contains remote connection inform 2. The following is an example of a winpeshl.ini file that is customized to open the **Remote Connection** tool as soon as an attempt is made to boot into DaRT: - ``` syntax + ```ini [LaunchApps] "%windir%\system32\netstart.exe -network -remount" "cmd /C start %windir%\system32\RemoteRecovery.exe -nomessage" diff --git a/mdop/dart-v7/how-to-recover-remote-computers-using-the-dart-recovery-image-dart-7.md b/mdop/dart-v7/how-to-recover-remote-computers-using-the-dart-recovery-image-dart-7.md index 2fac900255..d8cdbc0ab0 100644 --- a/mdop/dart-v7/how-to-recover-remote-computers-using-the-dart-recovery-image-dart-7.md +++ b/mdop/dart-v7/how-to-recover-remote-computers-using-the-dart-recovery-image-dart-7.md @@ -131,7 +131,7 @@ A file is provided that is named inv32.xml and contains remote connection inform 2. The following is an example of a winpeshl.ini file that is customized to open the **Remote Connection** tool as soon as an attempt is made to boot into DaRT: - ``` syntax + ```ini [LaunchApps] "%windir%\system32\netstart.exe -network -remount" "cmd /C start %windir%\system32\RemoteRecovery.exe -nomessage" diff --git a/mdop/dart-v8/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-8.md b/mdop/dart-v8/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-8.md index ea9f968420..5cf1247cb4 100644 --- a/mdop/dart-v8/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-8.md +++ b/mdop/dart-v8/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-8.md @@ -138,7 +138,7 @@ A file is provided that is named inv32.xml and contains remote connection inform 2. The following is an example of a winpeshl.ini file that is customized to open the **Remote Connection** tool as soon as an attempt is made to boot into DaRT: - ``` syntax + ```ini [LaunchApps] "%windir%\system32\netstart.exe -network -remount" "cmd /C start %windir%\system32\RemoteRecovery.exe -nomessage" diff --git a/mdop/mbam-v2/release-notes-for-mbam-20-mbam-2.md b/mdop/mbam-v2/release-notes-for-mbam-20-mbam-2.md index c67aa2acee..7cb8d1004c 100644 --- a/mdop/mbam-v2/release-notes-for-mbam-20-mbam-2.md +++ b/mdop/mbam-v2/release-notes-for-mbam-20-mbam-2.md @@ -38,7 +38,7 @@ If you are using the MBAM Stand-alone topology, and you upgrade the server infra WORKAROUND: After the upgrade, run the following script on the Compliance and Audit Database: -``` syntax +```sql -- ============================================= -- Script Template -- ============================================= diff --git a/mdop/mbam-v25/mbam-25-security-considerations.md b/mdop/mbam-v25/mbam-25-security-considerations.md index f87672362a..05695a6beb 100644 --- a/mdop/mbam-v25/mbam-25-security-considerations.md +++ b/mdop/mbam-v25/mbam-25-security-considerations.md @@ -134,7 +134,7 @@ You can configure the MBAM Recovery and Hardware Service with the name of this s - Configure the group after the MBAM Recovery and Hardware Service has been installed by editing the web.config file in the <inetpub>\\Microsoft Bitlocker Management Solution\\Recovery and Hardware Service\\ folder. - ``` syntax + ```xml ``` diff --git a/windows/client-management/mdm/alljoynmanagement-csp.md b/windows/client-management/mdm/alljoynmanagement-csp.md index c2b7e64c26..1c55f8740e 100644 --- a/windows/client-management/mdm/alljoynmanagement-csp.md +++ b/windows/client-management/mdm/alljoynmanagement-csp.md @@ -80,7 +80,7 @@ Boolean value indicating whether AllJoyn router service (AJRouter.dll) is enable Set adapter configuration -``` syntax +```xml SyncML xmlns="SYNCML:SYNCML1.2"> @@ -104,7 +104,7 @@ You should replace \_ALLJOYN\_DEVICE\_ID\_ with an actual device ID. Note that t Get PIN data -``` syntax +```xml @@ -123,7 +123,7 @@ Get PIN data Get the firewall PrivateProfile -``` syntax +```xml diff --git a/windows/client-management/mdm/applocker-ddf-file.md b/windows/client-management/mdm/applocker-ddf-file.md index e714495ff9..0a2f4eefd2 100644 --- a/windows/client-management/mdm/applocker-ddf-file.md +++ b/windows/client-management/mdm/applocker-ddf-file.md @@ -19,7 +19,7 @@ This topic shows the OMA DM device description framework (DDF) for the **AppLock Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download). -``` syntax +```xml This example shows how to enable App-V on the device.

-``` syntax +```xml $CmdID$ @@ -117,7 +117,7 @@ manager: dansimp

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

-``` syntax +```xml $CmdID$ @@ -141,7 +141,7 @@ manager: dansimp

This SyncML example shows how to publish a package globally on an MDM enrolled device for all device users.

-``` syntax +```xml $CmdID$ @@ -183,7 +183,7 @@ manager: dansimp

This SyncML example shows how to publish a package globally, with a policy that adds two shortcuts for the package, on an MDM enrolled device.

-``` syntax +```xml $CmdID$ @@ -277,7 +277,7 @@ manager: dansimp

This SyncML example shows how to publish a package for a specific MDM user.

-``` syntax +```xml $CmdID$ @@ -320,7 +320,7 @@ manager: dansimp > [!NOTE] > The user connection group has the user-only package as optional in this example, which implies users without the optional package can continue to launch the global package within the same connection group. -``` syntax +```xml $CmdID$ @@ -397,7 +397,7 @@ manager: dansimp

This SyncML example shows how to unpublish all global packages on the device by sending an empty package and connection group list in the SyncML.

-``` syntax +```xml $CmdID$ @@ -433,7 +433,7 @@ manager: dansimp

These SyncML examples return all global, and user-published packages on the device.

-``` syntax +```xml $CmdID$ @@ -444,7 +444,7 @@ manager: dansimp ``` -``` syntax +```xml $CmdID$ diff --git a/windows/client-management/mdm/assignedaccess-csp.md b/windows/client-management/mdm/assignedaccess-csp.md index 644edc9197..69ae1d1fb5 100644 --- a/windows/client-management/mdm/assignedaccess-csp.md +++ b/windows/client-management/mdm/assignedaccess-csp.md @@ -166,7 +166,7 @@ This MDM alert header is defined as follows: KioskModeApp Add -``` syntax +```xml @@ -188,7 +188,7 @@ KioskModeApp Add KioskModeApp Delete -``` syntax +```xml @@ -206,7 +206,7 @@ KioskModeApp Delete KioskModeApp Get -``` syntax +```xml @@ -224,7 +224,7 @@ KioskModeApp Get KioskModeApp Replace -``` syntax +```xml @@ -246,7 +246,7 @@ KioskModeApp Replace ## AssignedAccessConfiguration XSD -``` syntax +```xml @@ -698,7 +698,7 @@ Example of the Delete command. ## StatusConfiguration XSD -``` syntax +```xml @@ -760,7 +760,7 @@ StatusConfiguration Add OnWithAlerts StatusConfiguration Delete -``` syntax +```xml @@ -778,7 +778,7 @@ StatusConfiguration Delete StatusConfiguration Get -``` syntax +```xml @@ -826,7 +826,7 @@ StatusConfiguration Replace On ## Status example Status Get -``` syntax +```xml @@ -844,7 +844,7 @@ Status Get ## ShellLauncherConfiguration XSD -``` syntax +```xml