Merge pull request #46764 from georgewallace/omsdeprecation

adding oms migration article

Author: GitHubber17

articles/automation/TOC.yml

@@ -41,6 +41,8 @@
         href: automation-update-management.md
       - name: Manage updates for multiple VMs
         href: manage-update-multi.md
+      - name: Migrate OMS update deployments to Azure
+        href: migrate-oms-update-deployments.md
       - name: Integrate SCCM with Update Management
         href: oms-solution-updatemgmt-sccmintegration.md
     - name: Change Tracking

articles/automation/automation-update-management.md

@@ -203,7 +203,7 @@ Select the **Update Deployments** tab to view the list of existing update deploy
 
 ## Create or edit an update deployment
 
-To create a new update deployment, select **Schedule update deployment**. The **New Update Deployment** pane opens. Enter values for the properties described in the following table:
+To create a new update deployment, select **Schedule update deployment**. The **New Update Deployment** pane opens. Enter values for the properties described in the following table and then click **Create**:
 
 | Property | Description |
 | --- | --- |

articles/automation/media/migrate-oms-update-deployments/azure-automation.png

@@ -0,0 +1,71 @@
+---
+title: Migrate your OMS Update Deployments to Azure
+description: This article describes how to migrate your existing OMS Update deployments to Azure
+services: automation
+ms.service: automation
+ms.component: update-management
+author: georgewallace
+ms.author: gwallace
+ms.date: 07/16/2018
+ms.topic: conceptual
+manager: carmonm
+---
+# Migrate your OMS Update Deployments to Azure
+
+The Operations Management Suite (OMS) portal is being [deprecated](../log-analytics/log-analytics-oms-portal-transition.md). All functionality that was available in the OMS portal for Update Management is available in the Azure portal. This article provides the information you need in order to migrate to the Azure portal.
+
+## Key information
+
+* Existing deployments will continue to work. Once you have recreated the deployment in Azure, you can delete your old deployment from OMS.
+* All existing features you had in OMS are available in Azure, to learn more about Update Management, see [Update Management overview](automation-update-management.md).
+
+## Access the Azure portal
+
+From your OMS workspace, click **Open in Azure**. This navigates to the Log Analytics workspace that OMS used.
+
+![Open in Azure - OMS portal](media/migrate-oms-update-deployments/link-to-azure-portal.png)
+
+In the Azure portal, click **Automation Account**
+
+![Log Analytics](media/migrate-oms-update-deployments/log-analytics.png)
+
+In your Automation Account, click **Update Management** to open up Update Management.
+
+![Update Management](media/migrate-oms-update-deployments/azure-automation.png)
+
+In the future you can go directly to the Azure portal, under **All services**, select **Automation Accounts** under **Management Tools**, select the appropriate Automation Account, and click **Update Management**.
+
+## Recreate existing deployments
+
+All update deployments created in the OMS portal have a [saved search](../log-analytics/log-analytics-computer-groups.md) also known as a computer group, with the same name as the update deployment that exists. The saved search contains the list of machines that were scheduled in the update deployment.
+
+![Update Management](media/migrate-oms-update-deployments/oms-deployment.png)
+
+To use this existing saved search, follow these steps:
+
+To create a new update deployment, go to the Azure portal, select the Automation Account that is used, and click **Update Management**. Click **Schedule update deployment**.
+
+![Schedule update deployment](media/migrate-oms-update-deployments/schedule-update-deployment.png)
+
+The **New Update Deployment** pane opens. Enter values for the properties described in the following table and then click **Create**:
+
+For Machines to update, select the saved search used by the existing OMS deployment.
+
+| Property | Description |
+| --- | --- |
+|Name |Unique name to identify the update deployment. |
+|Operating System| Select **Linux** or **Windows**.|
+|Machines to update |For Machines to update, select the saved search used by the existing OMS deployment. |
+|Update classifications|Select all the update classifications that you need. CentOS does not support this out of the box.|
+|Updates to exclude|Enter the updates to exclude. For Windows, enter the KB article without the **KB** prefix. For Linux, enter the package name or use a wildcard character.  |
+|Schedule settings|Select the time to start, and then select either **Once** or **Recurring** for the recurrence.|| Maintenance window |Number of minutes set for updates. The value can't be less than 30 minutes or more than 6 hours. |
+
+Click **Scheduled update deployments** to view the status of the newly created update deployment.
+
+![new update deployment](media/migrate-oms-update-deployments/new-update-deployment.png)
+
+As mentioned previously, once your new deployments are configured through the Azure portal, the existing deployments can be removed from the OMS portal.
+
+## Next steps
+
+To learn more about Update Management in Azure, see [Update Management](automation-update-management.md)