Updating supportability items

Author: bobbytreed

articles/automation/automation-update-management.md

@@ -245,6 +245,9 @@ To create a new update deployment, select **Schedule update deployment**. The **
 
 Update Deployments can also be created programmatically. To learn how to create an Update Deployment with the REST API, see [Software Update Configurations - Create](/rest/api/automation/softwareupdateconfigurations/create). There is also a sample runbook that can be used to create a weekly Update Deployment. To learn more about this runbook, see [Create a weekly update deployment for one or more VMs in a resource group](https://gallery.technet.microsoft.com/scriptcenter/Create-a-weekly-update-2ad359a1).
 
+> [!NOTE]
+> The Registry keys listed under [Registry keys used to manage restart](/windows/deployment/update/waas-restart#registry-keys-used-to-manage-restart) can cause a reboot event if **Reboot Control** is set to **Never Reboot**.
+
 ### Maintenance Windows
 
 Maintenance windows control the amount of time allowed for updates to install. Consider the following details when specifying a maintenance window.

articles/automation/troubleshoot/start-stop-vm.md

@@ -38,6 +38,14 @@ The subscription is not registered to use namespace 'Microsoft.Insights'.
 The scope '/subscriptions/000000000000-0000-0000-0000-00000000/resourcegroups/<ResourceGroupName>/providers/Microsoft.OperationalInsights/workspaces/<WorkspaceName>/views/StartStopVMView' cannot perform write operation because following scope(s) are locked: '/subscriptions/000000000000-0000-0000-0000-00000000/resourceGroups/<ResourceGroupName>/providers/Microsoft.OperationalInsights/workspaces/<WorkspaceName>/views/StartStopVMView'. Please remove the lock and try again
 ```
 
+```error
+A parameter cannot be found that matches parameter name 'TagName'
+```
+
+```error
+Start-AzureRmVm : Run Login-AzureRmAccount to login
+```
+
 ### Cause
 
 Deployments may fail because of one of the following reasons:
@@ -46,6 +54,7 @@ Deployments may fail because of one of the following reasons:
 2. A policy is in place that disallows the deployment of the Start/Stop VMs solution.
 3. The `Microsoft.OperationsManagement`, `Microsoft.Insights`, or `Microsoft.Automation` resource types are not registered.
 4. Your Log Analytics workspace has a lock on it.
+5. You have an outdated version of AzureRM modules or the Start/Stop solution.
 
 ### Resolution
 
@@ -60,6 +69,7 @@ Review the following list for potential solutions to your problem or places to l
 
    See, [Resolve errors for resource provider registration](../../azure-resource-manager/resource-manager-register-provider-errors.md) to learn more about errors when registering providers.
 4. If you have a lock on your Log Analytics workspace, go to your workspace in the Azure portal and remove any locks on the resource.
+5. If the resolutions above do not solve your issue, follow the instructions under [Update the Solution](../automation-solution-vm-management.md#update-the-solution) to re-deploy the Start/Stop solution.
 
 ## <a name="all-vms-fail-to-startstop"></a>Scenario: All VMs fail to start/stop