Skip to main content

Shutdown switches for Server Core.

Below is a copy of the help file for the Shutdown Command.

Usage: shutdown [/i | /l | /s | /r | /g | /a | /p | /h | /e] [/f]

[/m \\computer][/t xxx][/d [p|u:]xx:yy [/c "comment"]]

No args Display help. This is the same as typing /?.

/? Display help. This is the same as not typing any options.

/i Display the graphical user interface (GUI).

This must be the first option.

/l Log off. This cannot be used with /m or /d options.

/s Shutdown the computer.

/r Shutdown and restart the computer.

/g Shutdown and restart the computer. After the system is

rebooted, restart any registered applications.

/a Abort a system shutdown.

This can only be used during the time-out period.

/p Turn off the local computer with no time-out or warning.

Can be used with /d and /f options.

/h Hibernate the local computer.

Can be used with the /f option.

/e Document the reason for an unexpected shutdown of a computer.

/m \\computer Specify the target computer.

/t xxx Set the time-out period before shutdown to xxx seconds.

The valid range is 0-600, with a default of 30.

Using /t xxx implies the /f option.

/c "comment" Comment on the reason for the restart or shutdown.

Maximum of 512 characters allowed.

/f Force running applications to close without forewarning users.

/f is automatically set when used in conjunction with /t xxx.

/d [p|u:]xx:yy Provide the reason for the restart or shutdown.

p indicates that the restart or shutdown is planned.

u indicates that the reason is user defined.

if neither p nor u is specified the restart or shutdown is unpl

anned.

xx is the major reason number (positive integer less than 256).

yy is the minor reason number (positive integer less than 65536).

Reasons on this computer:

(E = Expected U = Unexpected P = planned, C = customer defined)

Type Major Minor Title

U 0 0 Other (Unplanned)

E 0 0 Other (Unplanned)

E P 0 0 Other (Planned)

U 0 5 Other Failure: System Unresponsive

E 1 1 Hardware: Maintenance (Unplanned)

E P 1 1 Hardware: Maintenance (Planned)

E 1 2 Hardware: Installation (Unplanned)

E P 1 2 Hardware: Installation (Planned)

P 2 3 Operating System: Upgrade (Planned)

E 2 4 Operating System: Reconfiguration (Unplanned)

E P 2 4 Operating System: Reconfiguration (Planned)

P 2 16 Operating System: Service pack (Planned)

2 17 Operating System: Hot fix (Unplanned)

P 2 17 Operating System: Hot fix (Planned)

2 18 Operating System: Security fix (Unplanned)

P 2 18 Operating System: Security fix (Planned)

E 4 1 Application: Maintenance (Unplanned)

E P 4 1 Application: Maintenance (Planned)

E P 4 2 Application: Installation (Planned)

E 4 5 Application: Unresponsive

E 4 6 Application: Unstable

U 5 15 System Failure: Stop error

E 5 19 Security issue

U 5 19 Security issue

E P 5 19 Security issue

E 5 20 Loss of network connectivity (Unplanned)

U 6 11 Power Failure: Cord Unplugged

U 6 12 Power Failure: Environment

P 7 0 Legacy API shutdown

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/shutdown.mspx?mfr=true

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...