Note that I’m using the correct certificate thumbprint (starting with 22121…): You need to provide your credentials in order to execute the cmdlet.
After running this cmdlet, the WAP server came back online and the configuration could be successfully retrieved from AD FS.
The reason is that the v Center Server system and the Platform Services Controller use the new certificate, but the corresponding service registrations with the VMware Lookup Service are not updated.
When solutions connect to v Center Server or Platform Services Controller, they look at the service registration, which includes the service URL and the ssl Trust string.
When comparing the certificate thumbprint provided by the WAP Server event with the one used by the AD FS certificate, I noticed they were completely different: If you look at all certificate thumbprints, you won’t find any starting with “50571..” mentioned in the WAP server event.
After some research, I decided to do exactly what AD FS Event ID 276 says to do: Run the Install-Web Application Proxy cmdlet on the WAP server to re-establish trust between AD FS and WAP: The command above re-installs the correct certificate on the WAP Server.
Some solutions, such as VMware v Center Site Recovery Manager, VMware v Sphere Replication, or VMware v Center Support Assistant might be installed on a different machine than the v Center Server system or Platform Services Controller.
If you replace the Machine SSL certificate on the v Center Server or the Platform Services Controller, a connection error results if the solution attempts to connect to the v Center Server or Platform Services Controller.
Run the following command to verify the trusts are set to True: “Get-Broker Site” Check the line “Trust Requests Sent To The Xml Service Port=TRUE” At this stage, Virtual Delivery Agent (VDA) must allow pass through authentication and start.
The errors occur because the XML Service does not (by default) trust the requests that are sent without explicit authentication.
If both checks fail, AWS Cloud Formation returns a template validation error.
You can validate templates locally by using the aws cloudformation validate-template --template-body file:///home/local/test/A client error (Validation Error) occurred: Template format error: JSON not well-formed.
For some reason I was unable to view the websites that I previously published on this server, and access to the back end IIS server was not working.