Easily open a Remote PowerShell Session on Server 2012

The GUI is good,but PowerShell is better. Many IT Pros in my classes are confused with why we are moving more and more to a text based administration. All I can say is “everything old is new again.”

Remember back in the day when we had the expensive main frame that was larger than most peoples living rooms? End users accessed it via terminals. We moved on to the Client/Server model when hardware began to shrink and became cheaper. Now we are moving to virtualized desktops and are accessing them from terminals. Well, the same thing is happening on the administrative side.

We used to do everything in a text when it came to network administration. With Windows NT 3.5, we started doing it graphically. This made management very intuitive. There are some limitations though. If I needed to find all user SIDs that ended in 4 and were both part of the Newark OU and also in both the Finance and HR security groups. If I find them, I need to change their address and add them to another group and do this search and change every week, well the GUI cannot do that. So, we need to know PowerShell to handle things like this.

Server 2012 is designed to allow you to manage multiple servers from one. Let’s say that I need to open a remote PowerShell session on another server. This is one way to do it:

Open PowerShell
Type Enter-PSSession –ComputerName Indy-SVR1

Noticed the command prompt has changed to let me know that I am not executing commands on Indy-SVR1.

Now try this.

Open Server Manager.
Right click the server that you want to open the remote PowerShell session on.

Click Windows PowerShell.

Take a look at the command prompt. You are remotely administering the remote server via PowerShell. if you selected multiple server in Server Manager and then did this procedure, you would open a remote PowerShell session on each one in a separate Shell.

Comments

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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 .

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog