Solved

Shutting down Windows 2008 Server R2

Posted on 2013-12-18
7
387 Views
Last Modified: 2013-12-22
I am moving my server from one room to another. It is a Windows 2008 Server R2 file server. I'm not to familiar with servers so what would be the procedure in doing a proper shutdown? I know you can usually shut down the system from the logon screen. When I move the server into another room and power it on, am I required to have admin privileges to get the server back online? Or is it as long as the server is powered on, users are able to access the network share? My question is ....what is the proper protocol to shutdown, move the server into a new area, power back on, and make sure the clients are able to use the server successfully?


Thanks!
0
Comment
Question by:polymorphic26
7 Comments
 
LVL 13

Accepted Solution

by:
Felix Leven earned 250 total points
ID: 39726900
it's a good idea to move the Server not in the middle of a work day

normal shutdown

move to other room, power on server -> file services will work in the background without your interaction or Login.

Network Connection of the new room should be patched into the same vlan (same configuration) as before
0
 
LVL 2

Expert Comment

by:Berlin142
ID: 39726995
After moving the Server into the other romm, you start the Server. Logon is not required, it is a Server and the Services will start automatically. So users can Access. But you Need to have your admin credentials still have in the pocket. Be sure, that the Network configuration is corect (if you are in another subnet, you need to reconfigure).
0
 

Author Comment

by:polymorphic26
ID: 39727003
How would I properly shut down the server without administrator privileges? The logon screen on the server does not have that option.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 34

Assisted Solution

by:Seth Simmons
Seth Simmons earned 250 total points
ID: 39727010
do a clean shutdown of the system (need admin rights for this) then physically move it, reconnect everything (power, network, etc.) and turn on

give it maybe 10 min and from a client machine test if shares are accessible
if you can access files on there then you should be good
0
 
LVL 2

Expert Comment

by:Berlin142
ID: 39727014
OK, this is a rigght question. :-) Of course, you Need to logon before for shutting down. Only to cut off the power is a bad idea. But after restart, logon might not be required.
You can logon to the Server over the Network too, use mstmc for this.
0
 
LVL 13

Expert Comment

by:Felix Leven
ID: 39727063
pressing the power button quick will normaly shut down the Server. if no one/few users are working on the Server, it will do a clean shut down.

Even if some users have documents open in Office for example, they get a message that it is not possible to save at the document (they can try it later again so), if you are quick they will not notice.

If you run into any real Problems, you have a problem without administrative personal and passwords!
0
 
LVL 88

Expert Comment

by:rindi
ID: 39727071
If you don't have admin credentials, then leave the server where it is and either wait until an admin comes to do the job, or at least get the admin to give you those credentials, and he should also be ready to help you should you have issues.

Even though a move is simple enough, there is always the possibility something goes wrong, and to fix anything you need the credentials. If you don't have them it will almost certainly happen that something goes wrong, see Murphy's Law, if you have them everything will run smoothly after the move...
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you migrate a Terminal Server licenses server inside the 2008 server family, you can takte advantage of the build-in migration tool. If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you …
Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question