Install PowerShell R2 on Server Core

It’s here! PowerShell for Server Core. This is just a quick lesson in how to install it. So, how do you get it?

Once you get Windows Server 2008 Core R2 installed, Type OCLIST. We need to make sure that the following is installed:
• NetFx2-ServerCore (There may be additional characters after this)
• MicrosoftWindowsPowerShell

If you are missing any of these two, install them with the instructions below. Don’t forget, these are case sensitive.

For NetFx2-ServerCore
OCSetup NetFX2-ServerCore

For MicrosoftWindowsPowerShell
OCSetup MicrosoftWindowsPowerShell

OK, now that the software is installed, navigate to c:\Windows\System32\WIndowsPowerShell\V1.0. Once there, type PowerShell you will notice that the prompt changes to PS. Go ahead and type Get-Command and press Enter If this worked, PowerShell is installed. It is not going to be the pretty blue window, but inside the command prompt. Go ahead and type Write-Host –fore blue “Hello World” and press Enter. You will see the text change color. The color formatting will allow you to make your scripts in Server Core look pretty. Typing Exit will take you back to the command prompt.

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.

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Jason Yoder, MCT

Search This Blog