Forum Discussion
NimbostratusSharepoint 2013 iApp
Hi Dmetcalfe, those FQDNs are used to populate both the WAM/AAM host names and the APM auth domains. If you are using neither WAM/AAM nor APM, the deployment should work for any requests that point to that VIP.
The iApp validator for the FQDN fields doesn't support wildcards, so if you are using WAM/AAM, you would need to disable strictness and add the wildcard entry to the AAM host names manually (the APM auth domain config doesn't support wildcards, AFAIK).
thanks
Mike
Hi Dmetcalfe, those FQDNs are used to populate both the WAM/AAM host names and the APM auth domains. If you are using neither WAM/AAM nor APM, the deployment should work for any requests that point to that VIP.
The iApp validator for the FQDN fields doesn't support wildcards, so if you are using WAM/AAM, you would need to disable strictness and add the wildcard entry to the AAM host names manually (the APM auth domain config doesn't support wildcards, AFAIK).
thanks
Mike
Dmetcalfe_13626Thank you for the reply. That's an interesting thought. So your saying the dns being wildcard for that IP would be enough to support all the sites, that the vs itself doesn't need to know all the FQDNs?- Correct-without WAM/AAM/APM, the only thing the FQDN field is used for is the host header in the monitor send string.
- Dmetcalfe_13626Awesome! You were right. Boss is happy. He made a random sharepoint site on that subdomain and the F5 load balanced it like a champ. Thanks!
rduque481dmetcalfe, is there anyway you can tell me exactly were you made that change? our users are use to going to intranet, not intranet.company.com which is what this iapp is restricting us to do.
- boneyard
MVP
it might be wiser to just ask this in a new question. as mikeshimkus is mentioning a FQDN validator im afraid you need to enter a FQDN which just intranet isn't.
