So I'm faced with having to log out and power off every day or suck up the cost of keeping the laptop on. /r/maliciouscompliance, here I come I suppose.
Tempted to get one of these: https://us.amazon.com/Vegamax-Button-Ethernet-Internet-Netwo...
But these laptops were in bags, the last thing I wanted was a mac to start a house fire by heating up in a bag, so fuck that.
We disabled sleep to improve battery life and address a personal safety issue. There are many failure scenarios between various builds of Windows 10 and shitty drivers. Devices often wake up in bags and spin up fans until dead.
Normal scenario is that the battery is dead in the morning. In one case, it melted the compartment material in a bag and was deemed a safety hazard.
Problem solved.
When did this become a chore? I do this as standard and imo all people should. SSD Boot times these days are mostly under a minute and you get a fresh desktop every time.
EDIT: In fact I am one of the sysadmins which so many seem to despise on here. I have hybrid sleep and fast startup disabled by group policy on all my windows domain networks. It reduces so many support tickets by just actually having machines properly rebooted every night. Without this, people contact IT for glitches and bugs in their system, and when you look at the system uptime it is years!
edit: i would legitimately quit a company that made me reboot every single night.
Be aware I am in a corporate environment, with all non technical users, and all services online.
I guess I'll have to add this to my questions to ask at job interviews. Admins like you these days sure try to make our lives as horrible as possible. Corporate anti-virus, DNS interception and policies like these turn my machine into something I constantly want to throw out the window.
All because you are too lazy to ask a person to reboot if the machine has high uptime.
Nothing to do with laziness. As other people have often mentioned on HN, in the real world of understaffed underbudget corporate IT you need to do what you can to enforce things which make everybodies life easier.
It might very well be that it is preferable to the organization as a whole to sacrifice a bit of productivity everywhere for less burden on IT. But IMHO it should not be a decision which the IT department can make in isolation.
If you are disabling things by policy, it should be after a discourse with your users and a serious attempt at training. Being a GPO dictator is an anti-pattern.
Policies such as yours are tremendously user hostile, and they are a reflection of the company's culture. I would probably not quit such a company, but I would certainly go rouge by either bringing my own equipment, or reinstalling the OS. If reprimanded, then I would quit.
I don't think this means what you think it means. I'm not a dev, but a mechanical engineer, and having to shutdown nightly, and reopen things the next morning, would cost the company at least an hour of my work time every week.
The frontline IT guys aren’t able to deal with shit like that, so a draconian policy comes top down.
In addition to the obvious browser I typically have an IDE, a few terminal windows, email, a few communication clients (due to internal and customer choices, not mine), and usually one or two database clients open at most times. Some of those restore their state nicely while others don't. Some of the terminal windows have e.g. a particular set of terminals at certain directories because I need to keep track of and work on multiple source repos at the same time.
Starting all of those from scratch every day would indeed be a chore. Perhaps more importantly, having my desktop be the way I left it also automatically reminds me what I was doing and helps continue from where I was.
A fresh desktop every morning would be a misfeature for me and would annoy and frustrate me immensely if forced on me.
I do of course reboot now and then for system updates etc., and I don't mind that.
There might be a decent rationale for forcing a reboot or disabling sleep on non-tech office devices if the staff are technically unskilled, but this is HN, so it's not much of a surprise if people aren't keen.
The year is $CURRENT_YEAR, needing to reboot a system should be regarded as a last resort and a relic of the past. No matter how much effort you dump into making apps remember their state when they're closed, it will always be strictly inferior to just dumping RAM to disk.
Why should I? Not long ago, my laptop had uptime of over half a year.
[Edit: Oh, "windows domain networks"? I guess perhaps that explains your propensity for rebooting?]
If the laptop crashes more than once a week, I simply won't use it. If I worked at your company, I'd just BYOD, and keep your garbage laptop in a drawer, only booting for compliancy crap (and certainly not leaving it on long enough to download updates).
I've actually done this at a previous job or two. It was fine. Both (large behemoth) companies ended up cratering, at least partially due to chasing away competent employees with boneheaded corporate policies.
Office? Gitlab? Jira? Confluence? Any code at all? Adobe Experience Cloud? Any Google Service? Adobe Creative Cloud? Our Time and Expenses Tooling?
All locked behind SSO with EPM enforced. Additionally nearly all internal resources are only accessible via VPN. And guess what - only usable on EPM devices.
When I started I received a device, SDD encrypted me being root. After being acquired by big corp we now are in compliance world. Parts of that would have come regardless of big corp due to client requirements.
But a lot of this is quite taxing.