I replaced my internal CA and needed to replace all certificates, including the machine certs on my server core machines. I had to replace the domain controller certs, and some machine certs.
Posts Categorized: Server 2012
I’m testing a little bit with one of my Terminal Servers and noticed I could not connect through RDP with a normal (non-admin) user. Admin users fine but normal users were terminated immediately. I reviewed all settings for a while but couldn’t find the issue. Eventlog gave me a nice warning:
The Desktop Window Manager has exited with code (0xd00002fe)
I’m not really into timesyncing but I ran into an issue on my network that my time was off 10 minutes on my DC’s and servers. With the w32tm /query /source command I could see that my machines all were using the DC with the PDC emulator role enabled. The DC was using the VM IC Time Synchronization Provider as time source.
So at this moment we’re setting up a managed file transfer solution which needs some open ports. We would like to test these ports before our consultancy partner arrives to help us implement. We need to test if we can make a connection on a specific number of ports without actually having the software installed that listens on them.
Situation: Windows 7 SP1 x64. Remote Desktop Client 6.1.7601.17514. Connecting to a Microsoft Windows Server 2012 Remote Desktop Gateway.
The following error occurs:
Tutorial: Setting up SSTP on Windows Server 2012 (part 1) – prereqs
In this tutorial I’ll write about how to setup SSTP on Windows Server 2012 in a limited lab environment. It’s not a tough job, although you need some basic RRAS, DNS and Certificate knowledge. Before we start the prereqs: In my lab I use a domain controller which also is my enterprise root CA. My RRAS server is also my Online Responder. I’m going to assume you already installed these roles.
So I tought posting a blog for everyone that’s frustrated like me and looking for a solution for something that might be considered logical. WHY ON EARTH IS FOREFRONT NOT UPDATING!!!!
I created a PowerShell script that runs scheduled under serviceaccount credentials. When executing the task I got an access denied. Investigating the problem I noticed that the Do not store password. The task will only have access to local computer resources checkbox was enabled. With this box enabled you cannot perform remote tasks (including writing to network shares).
I encountered this one on a newly installed Windows 2012 server (Hyper-V) and it took me a while to figure it out. When you google it you will find different posts about registering dll’s, checking networking configs etc. etc. In my case something was messed up in the registry. So on top of all the posts you will find online make sure to check HKLM\Software\Policies if something is messed up with your Windows Update policies.