Queries on one time schedule button on update manager

Question

1. when we navigate to VM ==> operations => update ==> one time schedule , when we click on patches are being installed on the machine , am I correct?
2. this one time schedule button , when we click on this and install patches, does it comes under manual applying patches?

3.whice one is suggested method selecting one machine and click on one time schedule OR selecting bulk machine and click on one time schedule? ( we are planning to do for production servers )

4. how long it would take usually for one machine when we click on one time schedule?

5.if we plan to use one time schedule function we no need to use maintenance configuration right? I mean both are independent right?

Answer 1

Hi,

I hope I am understanding the questions correctly:

1 - When you click One-Time update a new window will open to configure the settings for the one time update that it will start as soon as you configure those settings. So it not automatically starts the installation, it starts the process of configuring that and you still have one last step to confirm that you want to start it.

2- It is still automatic patch installation meaning you do not login to the machines to install them. Just the process to start the installation is not scheduled but triggered manually now.

3 - You can one-time update one machines or many machines. You can schedule updates for one machine or many machines. Whatever you choose it is up to your personal preference. Usually scheduled updates are used to have monthly process of apply the updates so you know in advance on which date the patches will be applied. One time update is usually used when you have some urgent update that you want to apply now or you have just several machines that you manage on your own.

4- How long it takes depends on the number of patches that are installed and which patches are installed. Also if you have restarts or not. You cannot predict that in advance. You can set maximum maintenance window let's say 120 minutes. Once the installation starts it will stop applying patches around 120 minutes after that to avoid breaking that maintenance window. The maintenance window can be set on one-time updates and scheduled updates as well.

5- You can use one-time updates and scheduled deployments but be careful not to start those two at the same time. Most likely the one that is second will fail but still does not makes sense to do one-time updates at the same time the scheduled updates are running.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 2

Hello Varma,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to affirm the five points listed in your questions on One-Time-Schedule and maintenance configuration with Manual Applying Patches, Suggest Method Clarification, and Duration of update.

Q1:

when we navigate to VM ==> operations => update ==> one time schedule , when we click on patches are being installed on the machine , am I correct?

Ans1:

When you navigate to VM ==> operations => update ==> one time schedule and click on it, you're setting up a schedule for patches to be installed on the machine.

Q2:

this one time schedule button , when we click on this and install patches, does it comes under manual applying patches?

Ans2:

Clicking on the one-time schedule button and installing patches can be considered as manually applying patches since you're initiating the process

Q3:

whice one is suggested method selecting one machine and click on one time schedule OR selecting bulk machine and click on one time schedule? ( we are planning to do for production servers )

Ans3:

Both methods have their uses. If you have a smaller number of machines or want to test the patches on a single machine before rolling them out more widely, you might select one machine and click on one-time schedule. If you have a larger number of machines and have tested the patches, you might select a bulk of machines and click on one-time schedule. It's important to consider the potential impact on your production servers and plan accordingly.

Q4:

how long it would take usually for one machine when we click on one time schedule?

Ans4:

The duration it takes for one machine when you click on one-time schedule can vary depending on the number and nature of the updates. It's hard to provide a specific time frame.

Q5:

if we plan to use one time schedule function we no need to use maintenance configuration right? I mean both are independent right?

Ans5:

According to the Azure Update Manager documentation, Update Manager uses a maintenance control schedule instead of creating its own schedules. So, if you plan to use the one-time schedule function, you will still need to consider the maintenance configuration.

References

For more understanding and additional reading, kindly use the available documentation by the right side of this page. Especially, scheduling recurring updates in Azure Update Manager: https://learn.microsoft.com/en-us/azure/update-manager/scheduled-patching.

Also,

https://petri.com/azure-update-management-part-2-schedule-updates-check-update-compliance-and-enroll-non-azure-vms/

https://learn.microsoft.com/en-us/azure/update-manager/updates-maintenance-schedules.

Accept Answer

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful ** so that others in the community facing similar issues can easily find the solution.

Best Regards,

Sina Salam