Launch terminal and ssh into the server, something like this:
ssh admin@serverIP address
supply the password when prompted, you may also be asked to accept the RSA fingerprint if this is the first time you have ssh'ed into the server, key in 'yes'. Of course I am assuming you have left ssh access enabled. Once logged in issue this command:
sudo shutdown -h now
supply the password when prompted. Now go the XServe and attach a keyboard. Press the power on button and depress these 4 keys: command
alt+PR, keep your fingers on these keys for at least a minute. You should briefly see the activity lights on the front of the XServe come off and then on again. There is no sound on the XServe so you won't get the start up chime.
Launch terminal and ssh into the server, something like this:
ssh admin@serverIP address
supply the password when prompted, you may also be asked to accept the RSA fingerprint if this is the first time you have ssh'ed into the server, key in 'yes'. Of course I am assuming you have left ssh access enabled. Once logged in issue this command:
sudo shutdown -h now
supply the password when prompted. Now go the XServe and attach a keyboard. Press the power on button and depress these 4 keys: command
alt+PR, keep your fingers on these keys for at least a minute. You should briefly see the activity lights on the front of the XServe come off and then on again. There is no sound on the XServe so you won't get the start up chime.
Apple Remote Dekstop > select the server > Manage Meny > Log out current user. I've assumed you've tried this already and that your issue was one of incorrect screen resolution. The only way I know of resetting the screen resolution is the method I've already outlined. Perhaps someone else knows different?
In remote desktop, it says the current application is X11, but when I run top from terminal, I cannot see X11 running.
I wonder if a process is stuck and preventing me from logging out?
If I check the system info in X11 it show my resolution is 1024 x 768 which is correct, so I'm thinking this blue screen is just a glitch that a logout would fix...