Remove all Group Policy Objects completely and re-apply everything from scratch!
About DevOps, PowerShell and more
Tag: Windows Server 2016
And here is a small update on that:
Because others seem to have the same issue that I had, I cannot recommend to installation of KB4077525 on any ADFS Server! It looks like. that the problem occurs mostly with ADFS Server Farms that use WID as a backend. However, I cannot guarantee that it works better with a “real” SQL Server backend instead of WID.
If you want to give it a try, do yourself a big favour and use the AD FS Rapid Restore Tool to create a backup before. And maybe you should do a Backup of your OS before (Or a Snapshot if you have a Hypervisor, like I do).
Original article content:
Microsoft released the KB4077525 (OS Build 14393.2097) Fix, this fix contains some Active Directory Federation Services (ADFS) related bugfixes.
In my case, this one was the reason why I immediately applied it:
Addresses issue where AD FS incorrectly displays the Home Realm Discovery (HRD) page when an identity provider (IDP) is associated with a relying party (RP) in an OAuth Group. Unless multiple IDPs are associated with the RP in the OAuth Group, the user will not be shown the HRD page. Instead, the user will go directly to the associated IDP for authentication.
Right after applying the system asked for a reboot…
And then my headache started! The Active Directory Federation Services (ADFS) didn’t start. Lots of Error 102,220, and 352 in the Eventlog!
This content is older than 1 year. It might be outdated.
I installed the KB3150513 on some Windows 2016 Based systems. The Installation doesn’t ask for or enforced a reboot.
A couple of minutes later I pushed an updated DSC configuration and I saw the following Error Message:
The request to list features available on the specified server failed.
A DISM session could not be opened.
This content is older than 2 years. It might be outdated.
I shared my experience with Exchange 2016 on Windows Server 2016 in the last few weeks.
The most annoying problem, in my opinion, is the Get-Help Issue! I must admit, that I use Get-Help a lot, mostly because the Help is great and why remember every option if you can use Get-Help?
Nevertheless, there is a workaround!
Open a PowerShell Session (On the Exchange Server, or remote) and then type this:
1 |
add-pssnapin -name Microsoft.Exchange.Management.PowerShell.SnapIn
|
This content is older than 2 years. It might be outdated.
A while ago, I published an article about my experience with Exchange 2016 so far. Here is a minor update. Since my post, I found another Issue: The Exchange servers seemed to hand during a restart (reboot)!
We applied some patches on Monday and my two (2) servers hang during the restart. The RDP Session was terminated, but then nothing happened. I waited nearly an hour per node, but nothing happened. Even the local console (Via Hyper-V) was unresponsive. Only a hard Power Cycle fixed my issue.
The Patch was applied successful, so I decided to restart both nodes again today, but I had the same issue again.
This content is older than 2 years. It might be outdated.