Hi all,
I know similar questions have been asked before but I don't think its been answered clearly yet or at least not to my knowledge.
Given that 3rd party certificate suppliers won't allow you to place internal domain namespace FQDN's on certs any more..... .local .global or even .contoso if you really follow the books. If they did then tying down a company to such a externally referenced namespace would be virtually impossible.
This leads me to the actual question: if your not supposed to change the value given to InternalNLBBypassUrl because of the cas-cas proxy requirement then how can it be secured using its server fqdn value when you can't have such an entry on your 3rd party cert.
Stumbling blocks - you can only have one cert assigned to IIS services.
I'm looking for solutions that work in for a default install of all IIS virtual directories as opposed to splitting out the VD's into internal and external.
Anyone?
