Sample Code and Documentation to Assist Deployment and Management of On-Premises and AWS Servers
Microsoft Documentation:
Az Automation Schedule
Az Automation Software Update Configuration
General Troubleshooting:
1) Ensure Azure Az PowerShell module is completely up to date.
2) Troubleshoot Update Agent Readiness: Not Configured
Troubleshooting MMA Agent:
Windows Troubleshooting
Linux Troubleshooting
Troubleshoot Hybrid Runbook Worker
Windows Troubleshooter Tool
Linux Troubleshooter Tool
General Information:
1) As of January 2019, patch groups are limited to 500 servers. If there are more than 500 servers, customers will need to divide into multiple groups.
2) If WSUS is involved with the deployment, Windows looks to WSUS as the control plane with excluded and included patches.
3) Standalone WSUS works well, even if there is a substantial amount of Windows machines.
4) Pay attention to the total number of nodes if using an OMS Gateway. If servers cannot be assessed in the portal underneath Update Management and telneting to the machines over appropriate ports (default is 8081) does not work, plan to build out another OMS Gateway and use a load balancer. The easiest way to course correct is to assign a new static IP address to the first OMS Gateway, assign a new static IP address to the second OMS Gateway, and use the static IP of the first OMS Gateway as your VIP on the load balancer. You will not need to adjust the deployment on all servers' MMA configurations this way.