How do you handle rebooting file servers?

[stick1977]

We have a new client, I find that their server 2003 is only on SP1 and only has IE6. I go to upgrade to IE8 but can't because it's only SP1. I install IE7 because that's all I can do and it now the machine needs to be rebooted. (I should've just installed FF, but anywho).

Q: This is a file server and a DC but my question is about the file server side. If I reboot tonight once everyone has gone home, what will their open files look like in the morning? What if each user has one Word doc open with unsaved changes, what will they see on their screens in the morning? Will they lose any work?

In this day in age I'd just like to think that I can reboot a server without coordinating it with each and every user in the building but I'm not so sure. I know that I can go into computer management and view open files and shares but I don't see how that's going to help me if I can't close the files from there without deciding whether or not to save changes, etc.

My guess is that this is a pain for all administrators but maybe I'm missing something, how do you all handle these types of reboots? The users at this company never log off or shut down at the end of their days.

thanks in advance

 

[4ycr]

Not tried it with open files before but if I need to do it, I tell the office manager or owner that I need to restart and for everyone should save their work and log out.

They might not need to do that but it is something I have always done and as I told everyone to save their work they have no come back if data is lost during the reboot.

 

[Knightsman]

I also wouldnt install FF or Chrome on a file server. Keep it as native as possible to prevent issues.

But like 4ycr said, just tell them before you do it.

Normally though, I wait until the end of the day, remote in, update, and reboot. Or just set your system to install updates on the weekend, or at a time when you know no one is going to be working.

 

[BadBoy House]

If there are some updates that need to be installed and the server rebooted ASAP, I call our main contact at the client and let them know I'll be scheduling an automatic server reboot in the middle of the night once the backup has completed.

I have a shutdown/restart batch file in place that I can automate to run whenever I need it to.

 

[Paul Rodgers]

I like to do reboots on Friday nights if possible. That gives you a whole weekend to fix things if something gets borked.

 

[YeOldeStonecat]

Try to schedule. Rebooting clients servers is one of the things I do early in the morning before I hit the road. I typically am up around 0500...remote in..do updates, reboots, check on things..so it's all done before peeps start rolling in around 0730 or so....

I also used to install Firefox as an alternate browser..and then when Chrome switched out..started using that. Chrome is much safer than IE, you don't have to deal with the dreaded IE Enh Security settings...no need to install flash/shockwave with Chrome....so it's actually cleaner for the server, safer since Chrome runs sandboxed, and more secure than using IE. Not saying I do regular surfing from a server...but we do need to often go to vendors websites to download software/drivers/etc.

But when it comes to reboots of the server...we line it up with our clients. For our monthly clients..many are on regular habits of Monday morning reboots. Staff knows to close files when they leave Friday...or they're at their own risk. They've been told!

For other clients..we'll notify them or schedule a "maintenance window" for a server...someone in the office is in charge of spreading the word to close stuff/stay off.

 

[stick1977]

Sounds like the consensus is that there should be a scheduled reboot time that the users are aware of so you don't need to notify them each and every time you need to reboot. I'll set it for Sunday nights and let them all know. Thanks.

 

[Turcoloco]

Sounds like the consensus is that there should be a scheduled reboot time that the users are aware of so you don't need to notify them each and every time you need to reboot. I'll set it for Sunday nights and let them all know. Thanks.

I agree with others and what 4ycr said is what I'd do as well. In my current place, GP forces each workstation on the domain to automatically shutdown at 11pm but in your case, if no one ever logs off, reboots or shutdowns (amazing for Windows! ) then you definitely will have to notify the entire group prior to any scheduled date and before taking any action.

Some users do not also know the difference between log off and locking their WS so I would ask them to save their files and power off their computer at the end of the scheduled day.

 

[YeOldeStonecat]

Sounds like the consensus is that there should be a scheduled reboot time that the users are aware of so you don't need to notify them each and every time you need to reboot. .

The goal is to make it easier for you!

This way you can quickly check for open file sessions...see if some users have lots of stuff actively open.

I always check that first when it comes to servers with sensitive hosted applications....like accounting software. If several people leave some accounting software open on their workstations...and you go reboot the server...next time they launch it and open that client it may be corrupted.

After hours, when it comes to just open word docs or spreadsheets that end users leave open or minimized when they go home...I don't worry about those, they'll snap back in place when the server is back up.