Merge pull request #245432 from SnehaSudhirG/19July-UMCLimitations

Updated the TSG article

Author: prmerger-automator[bot]

articles/update-center/scheduled-patching.md

@@ -272,14 +272,6 @@ To view the current compliance state of your existing resources:
 ## Check your scheduled patching run
 You can check the deployment status and history of your maintenance configuration runs from the Update management center portal. Follow [Update deployment history by maintenance run ID](./manage-multiple-machines.md#update-deployment-history-by-maintenance-run-id).
 
-
-## Limitations and known issues
-
-The known issues and limitations of scheduled patching are:
-
-1. For concurrent/conflicting schedule, only one schedule will be triggered. The other schedule will be triggered once a schedule is finished.
-1. If a machine is newly created, the schedule might have 15 minutes of schedule trigger delay in case of Azure VMs.
-
 ## Next steps
 
 * To view update assessment and deployment logs generated by update management center (preview), see [query logs](query-logs.md).

articles/update-center/troubleshoot.md

@@ -10,7 +10,8 @@ author: SnehaSudhirG
 
 # Troubleshoot issues with update management center (preview)
 
-This article describes the errors that might occur when you deploy or use update management center (preview) and how to resolve them.  
+This article describes the errors that might occur when you deploy or use update management center (preview), how to resolve them and the known issues and limitations of scheduled patching.  
+
 
 ## General troubleshooting
 
@@ -103,7 +104,11 @@ To review the logs related to all actions performed by the extension, on Windows
 * `cmd_execution_<numeric>_stdout.txt`: There is a wrapper above the patch action, which is used to manage the extension and invoke specific patch operation. This log contains details about the wrapper. For Auto-Patching, the log has details on whether the specific patch operation was invoked.
 * `cmd_excution_<numeric>_stderr.txt`
 
-## Known issues
+## Known issues in schedule patching
+
+- For concurrent/conflicting schedule, only one schedule will be triggered. The other schedule will be triggered once a schedule is finished.
+- If a machine is newly created, the schedule might have 15 minutes of schedule trigger delay in case of Azure VMs.
+- Policy definition *[Preview]: Schedule recurring updates using Update Management Center* with version 1.0.0-preview successfully remediates resources however, it will always show them as non-compliant. The current value of the existence condition is a placeholder that will always evaluate to false.
 
 ### Scenario: Unable to apply patches for the shutdown machines 
 
@@ -141,6 +146,9 @@ More details can be found by reviewing the logs in the file path provided in the
 
 Setting a longer time range for maximum duration when triggering an [on-demand update deployment](deploy-updates.md) helps avoid the problem.
 
+
+
+
 ## Next steps
 
 * To learn more about Azure Update management center (preview), see the [Overview](overview.md).