Hand it back to management and tell them that if they want a technical solution implementing to force a shutdown you have a number of options you can explore, but any notification sent out regarding it has to come from them. Out of interest who's asked you to send this email? If you're just a techy then don't get involved, we've had this discussion a few times before and the consensus is generally that this is a company policy decision, if it's going to carry any weight then someone at managerial level or higher has to send it. Why not instead create a Group Policy that shuts their machines down at a given time and then send out an email reminding them to save their work and shut down their computers or else it will be shut down for them and they will lose work?Īs wonderful as that would be, just wait until all the higher ups start complaining about having to press the power button every morning, it will get messy and you'll eventually just pull it because the list of exceptions gets silly. Doing this over and over and over could cause some hardware failures that may have been avoided if it were just left on and power management set properly. When you start that machine up in the morning its hard on the hardware. We showed him quickly that there was a very real possibility of causing more problems with daily operation by shutting down machines than it would save in money to keep them off while not in use. When I worked at Department of Energy we had a situation where one manager thought we'd save a ton of cash shutting down the machines every day. Either way, if you have multiple machines to manage and there is a situation where you need remote management you better make sure you have a solid WOL solution which has been tested and retested so you can wake said machines up. Most operating systems have robust power management options. Turning displays off, sleep or hibernation mode (I wouldn't use either), Intel power management which integrates into Spiceworks. My question is why would you need your users to shut down their machines at all? Are you mounting an effort to save energy? If so, imho there are far better ways to automate this rather than putting it in the hands of the user. Thank god I had myself covered in black and white on that one. Now people were very, very angry about this. It was fairly embarrassing when every machine in the school turned off mid way through the night. They had not requested that I be present nor do anything and that they had it all in hand. They will assume that you are psychic, and should of known, that there was a late meeting going on and to of cancelled the script.įor example, one time when I was working in a college, it was the open evening. You do need to cover yourself, not only from the users but also the company. To give them a chance to save etc.Īlso make sure you have some sort of policy for it and people above you agree to it, include in this policy that any changes to the shutdown schedule are to come from such a such level and with so x amount of notice. With the shutdown script, it's always good to have a message alerting them that the machine will shutdown in x minites. A shutdown script or policy is the way to go, and it goes without saying that you need to inform your users ahead of time.
0 Comments
Leave a Reply. |