Windows Server 2012 R2 Core Setup Part 2

Let's continue the Windows Server Core setup from where we left it in the previous article of the series!

We will start by enabling the Remote Desktop firewall rules so you can connect to the server remotely:

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"


Next, it's time to allow access to administrative file shares like c$ using:

Enable-NetFirewallRule -DisplayGroup "File and Printer Sharing"

Some monitoring systems use ping to test if a system is up, in that case we have to allow it through the firewall:

Get-NetFirewallRule -Name FPS-ICMP4-* |
    Enable-NetFirewallRule

Those rules are part of the File and Printer Sharing group and will be enabled if you enable the group.

Now that we have allowed the Remote Desktop connections through the firewall, it's time to check if Remote Desktop is enabled and if not, enable it.

First, we will use the following command to check if Remote Desktop is enabled:
(Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server').fDenyTSConnections

If the result is 1 connections are not allowed.

If you get 1 and want to enable Remote Desktop, execute the following commands:

Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' `
 -Name "fDenyTSConnections" -Value 0

To make Remote Desktop more secure, we will enable the Network Level Authentication:

Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' `
 -Name "UserAuthentication" -Value 1

James O'Neill has a great post where he wraps the above commands in functions here.
 This is the end of the second article in the series, in the next - and last - article we will see how to update the server with the latest updates from Microsoft Update.

Popular posts from this blog

Domain Controller Machine Password Reset

Image
On my lab environment, I've configured two Active Directory sites since most enterprises have offices in more that one places. My lab however is not running 24/7 and the domain controllers in the second site are rarely turned on in order to save resources. This leads to issues with the Active Directory replication such as the "The target principal name is incorrect" error when I execute:  repadmin /syncall /AdeP. To remedy the issue, we have to reset the machine password of the domain controller that has been offline. First off, we are going to stop and disable the Kerberos Key Distribution Center (kdc) service on the problematic domain controller, in our case DC4. There may be some tickets in the cache so we should also clear them using klist purge Now it's time to change the machine password of the domain controller using the command netdom resetpwd /s:dc3 /ud:lab\administrator /pd:* Replace the "lab\administrator" with an account on your...
Keep reading

Managing Active Directory User Certificates using PowerShell

I first came across user certificates when I was working with email certificates a few years ago and I have to admit that I had trouble updating the certificates on the objects! Most organizations have a Microsoft Active Directory Certification Authority that issues the certificates used internally. When a certificate is issued to a user, the Microsoft Certificate Service saves the public key in Active Directory. The userCertificate attribute is a multi-valued attribute that contains the DER-encoded X509v3 certificates issued to the user. Although we rarely need to pay attention to this attribute, there are cases where we have to update it. To make things easier, I've written PowerShell functions to Get, Remove, Import and Export the certificates on that field. To get the list of certificates for an object, use the Get-ActiveDirectoryObjectCertificate function: PS C:\> Get-ActiveDirectoryObjectCertificate -UserPrincipalName cpolydorou@lab.local DistinguishedName  ...
Keep reading

Configuring a Certificate on Exchange Receive Connector

Today's article is about configuring Exchange receive connectors with specific certificates. Out of the box, Exchange uses self signed certificates to provide TLS secured mail flow. This will definitely be an issue if you expose the SMTP protocol to client computers since they won't trust the certificate. In this article we are going to configure a certificate that was issued by a third part authority to the Client Frontend receive connector. We'll start with getting the thumbprint of the certificate using the Get-ExchangeCertificate cmdlet: [PS] C:\> Get-ExchangeCertificate Thumbprint                               Subject ----------                               ------- 241B864DC82C664FECBA18B8D54987AAFB65B4C2 CN=*.lab.com, ... D4D210886B34E690191A1F008C78FDD0E7325DD4 CN=Exchange2013A 960171662EB26116...
Keep reading