ADFS Federations Service rename with Azure Pack as Relying Party Trust

A week ago I was confronted to an issue with ADFS with Forms Based Authentication(FBA) and Windows Azure Pack.

Problem

The environment was setup several months ago for a Proof of Concept of Windows Azure Pack and only working with ADFS and Windows Authentication because there was no requirement to used FBA and there was also no Web Application Proxy involved. All was working fine but the customer decided to setup FBA and a web application proxy. Unfortunately, the web application proxy was not working and keeps prompting the FBA login page.

After several hours of troubleshooting the issue was drilled down to a problem with the FBA on the ADFS server. But why was Windows Authentication working and FBA not. To exclude possible Windows Azure Pack/relying pary issue’s I started testing with the https://auth-azure.domain.com/adfs/ls/IdpInitiatedSignon.aspx page.

Eventually it turned out that the Federations Service FQDN had changed. From https://auth.domain.com to https://auth-azure.domain.com. The rename was not done correctly and since I had a lot of trouble figuring it out with some colleague’s i decided to write a blog about it.

Solution

So when renaming the ADFS FQDN from https://auth.domain.com to https://auth-azure.domain.com the SPN was forgotten for the ADFS Service account. The SPN was left on http/auth.domain.org and needed to be changed to http/auth-azure.domain.org.

After this was fixed, I still received logon screens on the FBA page and could not login. Next problem, the Token-Signing and Token-Decrypting certificates were incorrect. Since there are lots of blogs discussing how to update the Token Certificates in ADFS I will not discuss this but I renewed the Token-Signing en Token-Decrypting certificates. Restarted the ADFS service

Read more


SCVMM 2012 R2 UR5 Bare metal deploy downloading wrong Operating System VHDX

Last week I ran into an issue with SCVMM and Bare metal deploying Hyper-V hosts. During testing I was deploying several HP blades with the same Physical Computer Profile. But some hosts had the Hyper-V Server 2012 R2 OS, which was the one I configured in the Physical Computer Profile and others had the Windows Server 2012 R2 OS.
After recreating the .vhdx file the problem seemed to be gone, but it returned. During the deployment of de host in the WinPE mode I pressed Shift+F10 to open a command prompt and opened the VMMAgentPE.exe.log file to view any error’s. There I discovered it was downloading the wrong VHDX file.

Localized VMM 2012 R2 UR6 Console crash when changing/creating Hardware Profiles

Not very often I see server software in a different language than English but last week I was working with a customer that wants the dutch language on every server and software. There are several good arguments not to… but as the say in the Netherlands “a customer is king” 😉 So the Dutch language it is!

I installed VMM 2012 R2 in a cluster with UR6. After working with it for a while I got the error message below. After a restart I got it again when I wanted to create a hardware profile. Also when deploying a VM and got to the hardware part the console crashes. So no matter what, when I access hardware settings in VMM, the console crashes.

Read more