Skip to main content

The importance of PowerShell is growing

By

Recently I read an article from Redmond Magazine about the importance for IT professionals to learn Windows PowerShell. (You can read the article here)  In the article, there is a good quote that I would like to post here.

Right now, you've got a choice if you want to remain relevant as an IT professional: Learn Windows PowerShell, or learn ‘Do you want fries with that?'"

Greg Shields  (RedmondMag.com)

This morning I am building a new Windows 8 test environment using the Windows 8 Datacenter Beta.  I usually just go right through the installation but this morning I stopped and read some changes.  I’m looking at the screen where you choose between Server Core and the Full installation (now called Server with a GUI).

Read the differences in the description between Server 2008 and Server 8 for the both the Server Core and Full installation.  take note of when command prompter and PowerShell is used as well as which is the “Recommended” installation.

Server Core 2008

This option installs the minimal installation of Windows Server without the standard Windows user interface, and with a subset of server roles that can be managed from a command prompt, reducing management requirements and attack surface.

 

Server Core Windows Server 8

This option (recommended) reduces management and servicing by installing only what is needed to run most server roles and applications.  It does not include a GUI, but you can fully manage the server locally or remotely with Windows PowerShell or other tools.  You can switch to a different instillation option later.  See “Windows Server installation Options.’

 

Windows 2008 (Full installation)

This option installs the complete installation of Windows Server.  The installation includes the entire user interface, and it supports all of the server roles.

 

Windows 8 (Server with a GUI)

This option is useful when a GUI is required – for example, to provide backward compatibility for an application that cannot run ion a Server Core installation.  All server roles and features are supported.  You can switch to a different option later. See “Windows Server installation Options.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more