Skip to main content

Running PowerShell V2 on Windows Server 2012

Microsoft has always gone way out of their way to maintain backward compatibility for as long as possible.  In 2011, while delivering a class in New York, one of my students worked at a regional airport in the area.  He said that the landing system was still running Windows NT.  Even though the current version on the market was Windows Server 2008 R2, the software on the Windows NT system was working just fine.  Why fix what is not broken?

For those who have made a significant investment in PowerShell V2, your scripts should run just fine in PowerShell V3.  In the slim chance of a problem, you can run your script using the V2 engine.  For systems that were upgraded to PowerShell V3, such as your Windows 7 workstation, the V2 engine is already present.  For fresh installs, it is not.

On Windows Server 2012, Open Server Manager.

On the Dashboard, click Add roles and features.

Click Next 4 times.

Expand Windows PowerShell and then check Windows PowerShell 2.0 Engine.

image

Click Add Features and then click Next.

Click Install and then Close

Once the installation finishes, open PowerShell.

Type $PSVersionTable and press Enter.

image

Notice the PSVersion is 3.0

Now, type PowerShell.exe –version 2.0 and press Enter.

Type $PSVersionTable and press Enter.

image

Notice you are in V2 mode. To exit V2 mode, type Exit and press Enter.

You can also start V2 mode from the Start menu by typing PowerShell.exe –Version 2.0 and pressing Enter.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.