asked on Reboot SBS2011 box from a non-domain account on the same LAN
Small network with two servers. SBS 2011 & Server 2008.
Just today, nobody can log in remotely or get mail on any device.
The domain admin cannot login either. Gets invalid username or password message.
I can log on remotely to the Server 2008 box as the local admin, but of course that doesn't give me domain privileges.
I want to remotely reboot the SBS box. I've tried using shutdown.exe, but of course authentication fails.
Any suggestion as to how I might achieve this? I'll have physical access tomorrow but would love to solve this today.
Just today, nobody can log in remotely or get mail on any device.
The domain admin cannot login either. Gets invalid username or password message.
I can log on remotely to the Server 2008 box as the local admin, but of course that doesn't give me domain privileges.
I want to remotely reboot the SBS box. I've tried using shutdown.exe, but of course authentication fails.
Any suggestion as to how I might achieve this? I'll have physical access tomorrow but would love to solve this today.
IT AdministrationWindows NetworkingWindows Server 2008
Last Comment
snooflehammer
ASKER
You couldn't provide the syntax by any chance?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
If the server has an iDRAC or ILO module which has been configured, you should be able to logon to that and then force a reboot of the server that way. But if that hasn't occurred to you yet, the server probably doesn't have such a module anyway, or it hasn't been configured for use.
So you would still have to go on site. But you could then configure the iDRAC or ILO or whatever your server model includes so you can use it in the future.
So you would still have to go on site. But you could then configure the iDRAC or ILO or whatever your server model includes so you can use it in the future.
psexec syntax:
psexec \\(hostname or IP address of remote server) -i -s "c:\windows\shutdown /r"
this sound make the remote server run "shutdown /r" as a system process in whatever session is running on the server.
you should run the command from an elevated command line , as far as I know you don't need domain admin rights as long as you've run the command from an admin command prompt.
let us know if it works for you or not
psexec \\(hostname or IP address of remote server) -i -s "c:\windows\shutdown /r"
this sound make the remote server run "shutdown /r" as a system process in whatever session is running on the server.
you should run the command from an elevated command line , as far as I know you don't need domain admin rights as long as you've run the command from an admin command prompt.
let us know if it works for you or not
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
really? if you're running it as admin , using the switch tech to use the current session on the server + passing the command as a system process?
I don't know for absolutely sure because this is not a situation I would ever be in, but I'm pretty confident that it can be done. it's not like the OP is swimming in choices here so it's worth giving it a go.
I don't know for absolutely sure because this is not a situation I would ever be in, but I'm pretty confident that it can be done. it's not like the OP is swimming in choices here so it's worth giving it a go.
You would have to be logged into that machine with an account that is a member of the domain admins group -- and if you are able to do that you are able to log into the server with that same account.
psexec doesn't do any more than what can be done with other commands like shutdown (which didn't work for him) where you can add a \\MACHINENAME parameter.
psexec doesn't do any more than what can be done with other commands like shutdown (which didn't work for him) where you can add a \\MACHINENAME parameter.
And if the machine isn't accepting logins it is most likely stuck in an unstable state and nothing is going to respond except hitting the button...
yes if the machine is not accepting logins and it is not already logged in to a session then I agree, the only option really will be to button it.
how is this normally accessed, do you connect via RDP or do you use 3rd party software (team viewer, logmein etc)
how is this normally accessed, do you connect via RDP or do you use 3rd party software (team viewer, logmein etc)
ASKER
It's going to get buttoned this morning. Severely regretting not configuring ILO :(
ASKER
This could not be resolved without a manual reboot, so although they didn't answer the requirement to remotely force a reboot in this situation, I've accepted the two answers that best addressed the situation.
it should let you push the shutdown command to the remote machine with any admin account details.