What OS is it running? Sorry about the false alarm, I think this is not actually a hardware issue, but an OS issue. I'm still trying to lock it down.
I have modified my original post to reflect new information. I suspect I might have a glitch somewhere in the registry since I have a handful of new error codes showing up that started on the weekend. Forget the needle and the damage done, it's going to be all about a needle and a haystack hunt today If you have any suggestions as to what to look at as a possible OS based cause of a 1 hour shutdown, I'd be happy to check on it. Quite frankly, I'm a tiny bit suspicious of the license key.
It was a number written on the back of the CD envelope and I have no more paperwork on it. It came from the boss's now estranged brother, whom I took over for several years ago, but have no contact with and no paper trail. I think it's possible that a bad license key might cause a 1 hr shutdown.
Got some homework and reading to do So much hay Flush all the event logs then do a reboot Yes this is a trail feature of windows server I believe that it shuts down after a definite amount of time if you are using a trial licence, Hope this helps, Tom. A trial on Server ? This far along in the product cycle? I do hope OP did not fail to see the "this is not a registered version" watermark on the desktop and thought it was initially a motherboard issue??
If it continues running and seems like the key was the issue, it would be helpful if you mark the thread as answered. Solo Compute is an IT service provider. If you replaced the motherboard, the software would require activation again probably, whats the activation status.? I did have a similar issue with a server in the past if there was a power cut or similar thing that caused a shutdown.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Interesting conundrum here. Edited Jun 25, at UTC. If you type p: followed by the reason code for an unplanned shutdown, the command will not carry out the shutdown.
Conversely, if you omit p: and type in the reason code for a planned shutdown, the command will not carry out the shutdown. To force applications to close and restart the local computer after a one-minute delay with the reason "Application: Maintenance Planned " and the comment "Reconfiguring myapp. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
Contents Exit focus mode. Note If p or u are not specified, the restart or shutdown is unplanned. In this article. Forces running applications to close without warning users. Lists the reason for the system restart or shutdown. The following are the parameter values: p Indicates that the restart or shutdown is planned. XX Specifies the major reason number positive integer less than See more on Secpol.
Here is addition information about the optional commands to remotely restart your Windows Server. Naturally it only works during the time-out period. Of all the optional switches, this the one to test before you start restarting servers for real. The syntax is deceptively simple:. Is 30 seconds too long or too short a time? You can adjust with -t: 60 to display the dialog box for one minute.
The maximum time is seconds! Shutdown -r -f as you may have guessed, restarts the machine, and closes any programs without warning. Would you like to put your stamp on the shutdown? Let people know who is in charge, who is restarting their server?
Personally, I would avoid this switch, the syntax is tricky the numbers obscure, and it does nothing exciting. That said the idea is sound, it enters a reason for the shutdown in the event log. For me, this switch is an option, an option that I do not take. Note 2: Here is another example of Shutdown in action. VM Monitor is a clever desktop tool that not only tests that your server is online, but also displays the CPU and memory utilization for each node.
0コメント