Heard of it, but have never looked into it.

@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:

Your more than welcome to dive into https://issurvivor.com/ and search his archives

His only mention of MSP is from Nov, 2000 when he discovered the term. And he talks about ASPs as well. I had started my first of both, over a hear before he heard the terms 🙂

https://issurvivor.com/2000/11/20/trend-overload-first-appeared-in-infoworld/

It really was a new term at the time. But he acts like the concept was new. It was very tried and true in the 1990s. It's an ancient article, just funny that in late 2000 he was thinking that MSPs were some hot, new thing, lol.

@matteo-nunziati said in Anacron Jobs on a CentOS 7 Server:

@JaredBusch well never considered the workload on servers. I don't know how they manage it! maybe not so many use unattended upgraqdes in debian.

I definitely feel like Ubuntu users don't keep their systems as up to date 😉

In larger teams, you normally have 24x7 staff. So the reboot schedule goes to the current shift to monitor. It's only shops that lack round the clock scheduling that have this as a real issue, and if you don't have 24x7, shouldn't you be outsourcing to a shop that does if you really need that at all? I think that this normally (maybe not always) becomes a problem when you are dealing with layers and layers of other problems like not having enough IT staff to properly staff a department without causing unnecessary cost and risk and choosing not to outsource to an MSP/ITSP that could do this cost effectively.

Exactly. Job manager is "generic": it allows you to build complex planned stuff (like shutdown those VM during the night, and create another job to start them in the morning).

It's very very generic.

Backup is a kind of specific planned job.