Enable Exchange services after upgrade

So much for remembering to regularly post updates.. Ahh well.

Sometimes things go wrong with Exchange updates which Microsoft covers fairly well in it’s documentation. I recently ran into the described situation Exchange wasn’t working after the update as all the services were disabled. Now you could just enable them all, but as Microsoft notes some services are disabled by default and you should verify in the logs which services were disabled.

Here’s a quick PowerShell one liner to pull the list of services that were disabled from the logs and enable and start them. Hope someone finds it useful.

Get-Content -Path C:\ExchangeSetupLogs\ServiceControl.log | Where-Object { $_ -like "*Disabling service *"} | ForEach-Object { ($_ -split "'")[1]} | Sort-Object -Unique | ForEach-Object { Set-Service $_ -StartupType Automatic; Start-Service $_}

AD Enrollment failing after CA Migration when not removing existing server

Been awhile since I posted.. In that time I’ve moved home to Wellington, and started a new job that’s a mix of Infrastructure Engineer, DevOps Engineer, and general jack of all trades.  At my new job, the existing infrastructure was sorely in need of some TLC, and one of the things I had to tackle was replacing a 2008 R2 box that was serving as the sole DC, WSUS, and CA server among other things. For various reasons, I wasn’t able to migrate all the services off at once and do a big bang migration, so each service had to be done one at a time. After migrating the CA services over to a new 2016 box, everything was working great apart from AD Auto enrollment, which was failing with a fairly generic RPC connection error. TechNET and several CA migration guides talk about removing the source server from the domain as part of the process, but as the box still has other roles, this wasn’t possible. I strongly suspect this issue wouldn’t have cropped up if I was able to remove the PC from the domain, but what I did to solve the issue was this.

Open up ADSI edit, connect to the Configuration context, navigate to “CN=Enrollment Services,CN=Public Key Services,CN=Services”, select the pKIEnrollment object, and modify the DNShostname to be the new server. After that AD enrollment worked perfectly.. Hope this is useful to someone.

IBM M5100 Raid Controller stuck in Safe Mode.

So today at work I was attempting to re purpose an IBM x3650 M4  that was previously being used an an ESXi host from an internal USB drive. I’d thrown in a bunch of SAS disks from some other servers I was decomissioning, yoinked the USB key out, and was attempting to create some virtual drives. Normally this should be a trivial exercise, but the M5100 raid controller was perpetually reporting it was in Safe Mode, and wouldn’t let me successfully clear the the foreign configuration from either the GUI or the Storage interface to the controller in the BIOS. After a bit of faffing around, launching the CLI interface for the controller  and running “-adpfacdefset -a0” to reset the controller to factory defaults worked to successfully kill the safe mode loop, allow me to clear the foreign config and create new drives. There was a bit of a dearth of results googling for M5100 safe mode, so hopefully this will be of use to someone in the future.