Sysadmin

7713 readers

3 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world

founded 1 year ago

MODERATORS

DarraignTheSane@lemmy.world

00Lemming@lemmy.world

L3s@lemmy.world

Windows Server Updates in succession (lemmy.world)

submitted 1 year ago by LobsterScuttle@lemmy.world to c/sysadmin@lemmy.world

3 comments fedilink hide all child comments

Greetings SysAdmins. I am looking for a way to automate monthly windows updates for some of my servers. Currently I do them manually during maintenance period. The somewhat unique part I have is that they have to be done in order.

server1: Update, Reboot, back on; then Server2: Update, Reboot, back on; then on and on for 10 servers.

I'm open to ideas, we have (shudder) WSUS but if you've experienced the ability to do updates in this scenario in other apps I will explore. Something ideally that can determine that the server has rebooted and move on to the next, or say server1 wait 25 minutes then server2 wait 25 minutes...

Thanks

you are viewing a single comment's thread
view the rest of the comments

[–] SheeEttin@lemmy.world 4 points 1 year ago (1 children)

MECM and rolling reboots? Time how long it takes normally, then use at least 1.5x that time, or as long as you can.

What's the reason for the ordered reboots? Sounds like you need to review your architecture for better availability.

[–] BEEKAYRANDEE@kbin.social 4 points 1 year ago

Exactly this. MECM even has this sort of feature built-in with Orchestration Groups. You can set group 1 to perform updates and reboot at a certain time, then group 2 will only begin its update/reboot cycle when group 1 has completed or crossed a certain threshold.