Skip to main content

Enabling PowerShell Remoting and Remote Administration - Windows 2008 R2 Server Core

Enabling Powershell Remoting and Remote Administration - Windows 2008 R2 Server Core

Following on from my post Enable WinRM via Group Policy, there as some follow on tasks to ensure server core is manageable via powershell and server manager.

Add Firewall Rule
To start with, to allow GUI remote management of the event viewer, another firewall rule needs to be added :

Computer Configuration / Policies / Windows Settings / Security Settings / Windows Firewall with Advanced Security

Create an Inbound Rule allowing the predefined group 'Remote Event Log Management'


Install powershell and packs
Next, as server core is the only version of Windows Server 2008 R2 that does not install Powershell V2 by default, we need to install powershell and which ever cmdlet management pack we need. In this case I am only going to install the server manager and AD cmdlets.

Winrs -r:$dc.name Ocsetup MicrosoftWindowsPowerShell
Winrs -r:$dc.name Ocsetup ServerManager-PSH-Cmdlets
Winrs -r:$dc.name Ocsetup ActiveDirectory-PowerShell

Restart services
To complete the task, we need to stop and start the WinRM service to register the services now available. As we will be stopping the Winrm Service, we can use it to stop the service, but not to start it again. To get around this, I have used WMI to connect to the remote server.

$service = gwmi -Class Win32_Service -ComputerName $DC.name | where {$_.name -eq "winrm"}
stop service"
$service.StopService()
#let the service stop before trying to start in again
Start-sleep 2
"start service"
$service.StartService()

Finally, I have read in from a csv list of servers to process. Actually I ran a remote job with the script from this post and output the servers that failed and exported to csv:

$job.childjobs | where {$_.State -eq "Failed"} | Select location | Export-Csv dclist.csv -NoTypeInformation

The complete script

Foreach ($DC in $(Import-csv dclist.csv)){
   Winrs -r:$dc.location Ocsetup MicrosoftWindowsPowerShell
   Winrs -r:$dc.location Ocsetup ServerManager-PSH-Cmdlets
   Winrs -r:$dc.location Ocsetup ActiveDirectory-PowerShell
   $service = gwmi -Class Win32_Service -ComputerName $DC.location | where {$_.name -eq "winrm"}
   "stop service"
   $service.StopService()
   #let the service stop before trying to start in again
   Start-sleep 2
   "start service"
   $return = $service.StartService()
   #check the service has started, if not try again
   if ($return.returnvalue -ne 0){$service.StartService()}
}

After setting the GPO to enable winrm, adding the firewall rules to manage event logs remotely, ensuring the PowerShell componenets are installed and the service have been restarted, your server core installs should be easily managed remotely.

Comments

Popular posts from this blog

Assigning Permissions - AGDLP

AGDLP It seems I have been mildly distracted away from the title of this blog site.   It does say AD Admin, but I seem to have been taken away by file system stuff.   I have to say, it has all been worthwhile, but it’s probably time I got back to the real heart of what I do. There are probably a million permission assigning advice pages, but I thought I would put another one out there after referring to AGDLP in my last post. So, what is this all about – AGDLP.   Well, it is something I learned in my MCSE 2003 studies and has become ingrained into my ideals since.   As a contractor, I get to move job often.   This enables me to forge opinions on how to configure things in a domain, and more importantly how NOT to configure things. AGDLP is definitely on the to do list…for anyone in any size domain or forest, as it follows some very basic principals.   I will explain these whilst I go through what AGDPL stands for. A A is for...

Finding out what 'SearchFlags' are set on you AD attributes

Whilst doing some research into indexed attributes, I posted this  a while back on how to find your index attributes.  Since then, I have looked a little deeper into what indexing really means and found this excellent explanation on the numbers that can be found in the searchflags attribute of a schema object. Using Florian’s reference, I built the following script (which is both powershell v1 and v2 compatible) to get the schema attributes from the forest schema and return (among other things) the breakdown of your attributes search flags. $forest = [System.DirectoryServices.ActiveDirectory.forest]::getcurrentforest() $schema = [ADSI]('LDAP://CN=Schema,CN=Configuration,dc=' + ($($forest).name -replace "[.]",",dc=")) $attributes = $schema.psbase.children | where {$_.objectClass -eq "attributeSchema"} $collection = @() foreach ($attr in $attributes){ $store = "" | select "Name","lDAPDisplayName","singlev...

Updated : V0.992 Filesystem Powershell module

Update : version 0.992  now available including DFS-r Hot on the heals of my AD sites module , I have been looking at some file system functions.  This module is driven primarily by my own needs, but after a prompt on the powergui website from someone after a way of managing DFS with powershell (thanks packetboy), this is what I have come up with.  All help files are included with examples, but I will publish the help and examples over time. Requirements This module has been built on a Windows 2008 R2 platform and therefore the DFS functions will be based around the 2008 R2 version of DFSUTIL.  This is not to say that it is not compatible with anything earlier, it has just not been tested. Installation and use Download the zip file and extract to your modules folder. This can be found by running "explorer $pshome\modules" from a PowerShell console. To use, run "import-module Filesystem" Command list and Help To retrieve the list of comma...