cleaning up note/important/tip/warning formatting for markdig engine conformance

This commit is contained in:
Liza Poggemeyer
2019-06-07 15:48:27 -07:00
parent a9bbc179f0
commit d495de72a5
100 changed files with 218 additions and 218 deletions

View File

@ -18,7 +18,7 @@ ms.topic: article
You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade.
>[!NOTE]
>[!NOTE]
>If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell.
The package converter can only directly convert packages created by an App-V sequencer version 4.5 or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion.

View File

@ -41,7 +41,7 @@ Before you can deploy the upgrade, make sure you import the new version of the a
4. Click **Add**, browse to the existing (older) version of the app that you're upgrading, and then click **OK**.
5. Under **New Deployment Type** select the new version of the app. (When you imported the new version, it comes in as a new deployment type. If you're upgrading a Universal application, you'll see only one type here.)
![Create a supersedence rule for the new version of the app](media/app-upgrade-supersede-deploy-type.png)
> [!IMPORTANT]
> [!IMPORTANT]
> Do **NOT** select **Uninstall**. This tells Configuration Manager to uninstall the old version, but it does **NOT** then install the new version.
6. Click **OK**.