It was meant as an example of other server grade software that requires a shutdown reason, even if you could turn it off (which i honestly didn’t know)
2 Likes
Haven’t seen this removed yet in the latest version - which is where I encountered it as I began moving from a 24 scale server and a Xigmanas server to 2 new scale servers.
Unfortunately with the learning I’m doing I’m regularly shutting down and or restarting. It is of no value to me whatsoever to record these and as it’s a couple of clicks, choose dropdown for custom and then garbage it’s intensely frustrating and for a home environment a wrong default on such a feature.
In a DC sure, if that’s what the company wants, but this type of activity should be recorded in the Change management system anyway and that definitely SHOULD be read by anyone attempting to identify an issue that arises so I can see many companies not needing it in the server log either because such things should be recorded centrally not on each individual server so that all teams can see what’s happened.
Anyway if there’s still a debate on whether to address this with a change. Please add 1 to requests to make it configurable (or remove it, don’t really care which)
You can also post suggestions and vote there.