PowerShell: What if I do this???

In PowerShell we have the ability to see what a command will do before it executes. Image when you were first starting out in IT. Someone told you to type Format C: without telling you the results. Obviously formatting the C: drive is not something you want to do on accident. You can ask PowerShell what would happen if you did _______. We use the -WhatIf parameter.

Let's first get a list of all services running on you client:

Get-Process

You noticed that a process is called BlueToothHeadsetProxy is listed. What would happen if you typed:

Stop-Process -ID 5200

(5200 is the process ID )

You would disconnect your headset. We can use the -Whatif parameter to discover what would happen if we would execute this command without executing it. To do this type:

Stop-Process -ID 5200 -whatif

stop-process -id 5200 -whatif

What if: Performing operation "Stop-Process" on Target "BluetoothHeadsetProxy (5200)".

We can also confirm each step before it is taken:

Stop-Process -ID 5200 -confirm

Confirm

Are you sure you want to perform this action?

Performing operation "Stop-Process" on Target "BluetoothHeadsetProxy (5200)".

[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help

(Default is "Y")

The Suspend option has its value when you are typing a long command, but then remember that something else needs to be done first. By adding the -Confirm parameter, you can suspend the execute. This gives you a chance to complete the missed step and then to use the up arrows to retrieve the long command and execute it without having to retype it.

Comments

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...

Jason Yoder, MCT

Search This Blog