New answers tagged

-4

You want to have two NICs to prevent clogging up the NLB. I have seen this happen especially during the search crawl. So one NIC should be used for the WFE to talk to SQL and should be on a separate VLAN that does not go through the NLB. The other NIC goes through the NLB and is how users access the WFE.


5

You could set up HSTS (RFC 6797) for the domain in question along with the redirection from HTTP to HTTPS. (HSTS is not supported if turned on for a HTTP site, and in fact including the HSTS header on a HTTP connection is a violation of the RFC; HTTPS must be used, and the RFC requires that any HSTS headers received over non-secure transports be ignored.) ...


0

Another way this can be done is with a commercial product called WebDrive (full disclosure: I work for the developer of this product). WebDrive maps a persistent drive letter to SharePoint Servers (and many other cloud services and server types as well). A huge benefit for system admins is the ability to preconfigure settings and push them out to all of ...


2

The issue is that the domain that was required for the SignInAccelerationDomain wasn't the domain used as the UPN for office 365 but the full domain name of the Windows domain. So i had to enable in my example the acceleration for "corp.B.com" and not for "B.com".


1

Did you use the Set-SPOTenant commandlet? Set-SPOTenant -SignInAcceletationDomain “mydomain.com” Set-SPO Tenant -EnableGuestSignInAcceleration $true There must also be only one identity provider in your AD. SharePoint Online must have a specific site to target when accelerating. The organization can have multiple domains as long as there is a single AD ...



Top 50 recent answers are included