ADFS deep dive planning and design: http://blogs.technet.com/b/askpfeplat/archive/2014/11/24/adfs-deep-dive-planning-and-design-considerations.aspx
ADFS deep dive certificate planning: http://blogs.technet.com/b/askpfeplat/archive/2015/01/26/adfs-deep-dive-certificate-planning.aspx
Technet videos: http://technet.microsoft.com/en-us/video/ff701694
Certificates requirements: http://technet.microsoft.com/en-us/library/dn151311.aspx Also previous: http://technet.microsoft.com/en-us/library/dd807040(v=ws.10).aspx . In general a standard SSL certificate will be sufficient and you can use the same certificate for token signing and SSL communications (if acceptable by your security policy).
Certificate Requirements for Federation Server Proxies: http://technet.microsoft.com/en-us/library/dd807054%28WS.10%29.aspx
Federation server proxies are usually exposed to computers on the Internet that are not included in your enterprise public key infrastructure (PKI). Therefore, use a server authentication certificate that is issued by a public (third-party) certification authority (CA), for example, VeriSign or Comodo. When you have a federation server proxy farm, all federation server proxy computers must use the same server authentication certificate. It is important to verify that the subject name in the server authentication certificate matches the Federation Service name value that is specified in the AD FS 2.1 Management snap-in. To locate this value, open the snap-in, right-click Service, click Edit Federation Service Properties, and then find the value in Federation Service name text box. Note: Client authentication certificates are not required for AD FS 2.0 federation server proxies.
How to Replace the SSL, Service Communications, Token-Signing, and Token-Decrypting Certificates: http://social.technet.microsoft.com/wiki/contents/articles/2554.aspx
Prepare your network for federation servers: http://technet.microsoft.com/en-us/library/dn151322.aspx
and create A records for your AD Federation service name not CNAME !
BIG-IP hw load balancers and ADFS: http://www.f5.com/pdf/deployment-guides/microsoft-adfs-dg.pdf
Installation checklist : http://technet.microsoft.com/en-us/library/dd807086.aspx
In addition, this is an excellent article on configuring ADFS v. 2.0: http://www.sysadminsblog.com/microsoft/installing-and-configuring-adfs-2-0/
example of implementation with a cloud service: http://support.druva.com/entries/21437659-How-to-install-and-Configure-Active-Directory-Federation-Services-for-Druva-inSync-Cloud-SAML-integr
ADFS design and deployment: http://technet.microsoft.com/en-us/library/dd391937(v=ws.10).aspx
Understanding the ADFS proxy: http://blogs.technet.com/b/askds/archive/2012/01/05/understanding-the-ad-fs-2-0-proxy.aspx
Planning Federation Server Proxy Placement: http://technet.microsoft.com/en-us/library/dd807130%28WS.10%29.aspx
Troubleshooting federation server proxy problems: http://technet.microsoft.com/en-us/library/adfs2-troubleshooting-federation-server-proxy-problems%28WS.10%29.aspx
How to test if ADFS is functioning: http://www.dagint.com/2011/10/how-to-test-if-adfs-is-functioning/
Guidance for Selecting and Utilizing a Federation Service Name: http://social.technet.microsoft.com/wiki/contents/articles/4177.aspx
Cmdlets in Windows PowerShell: http://technet.microsoft.com/en-us/library/ee892329.aspx
Replacing ADFS certificates: http://jorgequestforknowledge.wordpress.com/2013/05/15/replacing-adfs-certificates/
Enable auditing of issued claims: http://jorgequestforknowledge.wordpress.com/2013/07/08/enabling-auditing-of-issued-claims-in-adfs-v2-x-and-adfs-v3-x/
Other web resources about ADFS:
Steps by steps and use cases: http://technet.microsoft.com/en-us/library/adfs2-step-by-step-guides(v=ws.10).aspx