Tag Archives: Windows Server 2016

Windows Server 2016: CDPUserSvc has stopped working

You may observe the following error on Windows Server 2016 immediately after OS startup:

CDPUUserSvc_65df7 has stopped working

This “has stopped working” part tells us that some unhandled exception occurred, so we can switch over to Event Viewer to find some more details about it:

svchost.exe_CDPUserSvc_65df7 – Exception code: 0xc0000005

Exception details are the following:

Faulting application name: svchost.exe_CDPUserSvc_65df7, version: 10.0.14393.0, time stamp: 0x57899b1c
Faulting module name: cdp.dll, version: 10.0.14393.1715, time stamp: 0x59b0d38c
Exception code: 0xc0000005
Fault offset: 0x0000000000193cf5
Faulting process id: 0x1b14

After quick research I found out that this error was introduced with some Microsoft updates and to resolve it on Windows Server 2016 14393.1884 you just need to apply another update πŸ™‚ More specifically you need to install KB4053579, which can be downloaded from Windows Update Catalog. Applying this update resolves this error.

Configuring Windows Server 2016 Core Domain Controller

In Windows Server 2016 you no longer have an opportunity to switch back and forth between core and GUI installation, hence you cannot do install and configure AD DS in a lazy way (using full GUI) and then convert it to core. That was something I discovered hard way long time ago – so I already have separate VHDX templates for Server 2016 core and full GUI VMs.

But it has been quite a while since I was playing with Server Core so when I starting provisioning my new Server 2016 core domain controller VMs today I realized that I need to remember quite a few commands to fully install AD DS on Server Core. I was about to create a blog post listing essential commands, but actually found very well written blog post on TechNet covering exactly that:Β Chad’s Quick Notes – Installing a Domain Controller with Server 2016 Core. So just sharing it here, instead of writing the same myself πŸ™‚

Installing Exchange 2016

I’ve finally found some time to install Exchange 2016 in my test environment. This thing has been on my to do list for a long time, and recently Nicolas Prigent wrote a blog post at StarWind blog on exactly this subject – Installing Exchange Server 2016 on Windows Server 2016, leaving me no excuses for not completing task from my to do list anymore πŸ™‚

So essentially instructions provided in the abovementioned blog post were sufficient for me for getting Exchange Server 2016 up and running in my test environments. Installation process itself is a bit lengthy and before that you have to take care of prerequisites as well as prepare your AD DS schema. With these preliminary parts I had couple of issues which I will mention below.

First of all you have to have the following update for Windows Server 2016 – KB3206632 which is available for download in Microsoft Update Catalog. When I installed this update on my Hyper-V VM with Windows Server 2016 I had an issue on reboot stage – system sort of went into applying updates and restart but then stuck with empty blue background. After waiting for about 8 hours (I just left box running during the night) I just powered off VM and switched it on again – update was applied successfully after this.

Next part is AD DS schema modifications you need to make before installing Exchange by issuing the following commands one after another (strictly in order specified):

cd d:
#Step 1 Preparing AD DS Schema
.\setup /PrepareSchema /IAcceptExchanfeServerLicenseTerms
#Step 2 Preparing AD DS
.\setup /PrepareAD /OrganizationName:"Conundrum" /IAcceptExchanfeServerLicenseTerms
#Step 3 Prepare Domain
#In case you have multiple domains replace PrepareDomain with PrepareAllDomains
.\setup /PrepareDomain /IAcceptExchanfeServerLicenseTerms

I run into issues with steps 1 and 2. Step 1 failed with on Extending Active Directory schema with the following error:

There was an error while running ‘ldifde.exe’ to import the schema file ‘C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf’ The error code is: 8224.

To solve this I just attached installation ISO to one of my DCs and run it there – operation completed without errors.

Next issue happened on step 2:

An Active Directory 0x51 occurred when trying to check the suitability of server. Error: ‘ActiveDirectory response: The LDAP server is unavailable.’

In this case re-running the same command from DC didn’t helped and what actually helped is moving schema master role from one DC to another. If you are a bit rusty on how to do this – see this blog post.

So thanks to Nicolas’ post I now have Exchange 2016 in my test environment, and I already reconfigured my K2 farm (yes I run 4.7 + Feb 2017 CU) to enable Exchange Server integration:

How to install and manage Nano Server

My 2nd article about new Windows Server 2016 installation option “Nano Server” is now available @StarWind Blog.Β In my previous article, I covered general concepts around Nano Server, in this one I talk about more practical aspects: installation and management. At the end of the day, you would agree that the best way to learn new technology it is try to use it – this way you will be exposed to its strengths and weaknesses directly, and can get real understanding of whether it works for you or not. Though at this point even Microsoft admits that despite all its greatness, at the moment, Nano Server has quite limited utility as it supports only a small subset of roles and features out of those which you can find in full GUI version of Windows Server.

Read more @StarWind Blog…

Windows Server 2016 Nano Server – Just enough OS model

I’ve recently spent some time exploring Windows Nano Server installation option and wrote detailed blog post for StarWind blog entitled Β “Windows Server 2016 Nano Server – Just enough OS model” you can read it here. Article covers Nano Server basic concepts and compares this installation type with conventional Full Server and Server Core installation options – if you find this topic interesting please read on @ StarWinds Blog.