How to set PowerShell to Always Open in Version 2

One of the things that I love most about being an MCT is that I get to meet a lot of people who look at things differently. For example, in my PowerShell class this afternoon, I had one individual ask if it was possible set PowerShell to open in V2 by default. They were in a mixed environment between V2, 3, and 4. My first instinct was to add this line to their PowerShell profile.

PowerShell -Version 2

Then I thought about it. I would much rather have version 5 as my default and just create a different icon for version 2. So this is what I did.

Right click your desktop and select New –> Shortcut.

In the Type the location of the Item: box, enter PowerShell.exe –Version 2 and click Next

In the Type a name for this shortcut box, I gave the name PowerShell V2 and clicked Finish.

I then opened the icon that it created.

When you type Get-Host the Version property should show that you are using V2. If you want to switch to V5 in this windows, just type PowerShell –Version 5 and press Enter.

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