Problems with ADFs and IFD deployment under dynamics crm2013 server2012r2

In the previous article, I continued to solve the problem of server2012r2, because I found a lot of information on the Internet after I reported an error in the IFD deployed on R2, but after all, R2 is a new crm2013, there are basically no related feedback on the internet, basically the system versions earlier than 2012, and ADFs are also versions earlier than 2.1. So after the hotfix patch in 2012 cannot be installed on R2, I tried to re-deploy IFD in the 2012 system environment and encountered the same errors. So I thought about the problems in the two systems as one and tried to solve them in the same way, at the same time, let's take a look at what Microsoft has said about this, but later I reflected on adfs2.1's problem that could not be solved in adfs3.0.

So... view the system log carefully.We finally found the new world "there is already a listener on IP endpoint 0.0.0.0: 808"

Our international friends searched online have provided solutions.

"Region"

The obvious port conflict occurs. Run this command in Windows powershell.Set-adfsproperties-nettcpport 809"

After you press enter to complete the execution, the cursor jumps a line. There is no prompt for anything else, no prompt for success or failure. It doesn't matter if you have succeeded. After restarting the computer, you will be able to witness a miracle.

I put all domain control, certificate servers, databases, CRM applications, and ADFs services on one machine. It is said that becauseAll in one boxThe port conflict of some services.