Forum Discussion
3 Replies
Use,
Default persistance as cookie fallback as source addr
- Rick_199205Nimbostratus
Microsoft does not recommend persistence in LTM on and after 2013 version of SharePoint /exchange Persistence is handled by sharepoint, exchange cas etc
- youssef1Cumulonimbus
Hi,
I understand that you don't use Iapp. I do not use it either because I added an apm and asm policy...
So for your question, Which persistence profile do you want to use? Advanced:
By using persistence, the BIG-IP system tracks and stores session data, such as the specific pool member that serviced a client request, ensuring client requests are directed to the same pool member throughout the life of a session or during subsequent sessions. For SharePoint 2016, the default is Do not use persistence. So you don't need to set any persistance:
You can find all information needed in the deployment guide:
https://www.f5.com/content/dam/f5/corp/global/pdf/deployment-guides/microsoft-sharepoint-2016-dg.pdf
Do not use persistence (recommended): This is the recommended option if you are using SharePoint 2016. If your implementation does not require persistent connections, select this option. SharePoint 2016 does not require connections from a single client to persist to the same SharePoint server, as the Distributed Cache service maintains authentication information across all SharePoint web application servers.
Additional Important information:
don't forget to create and use an oneconnect profile:
OneConnect (connection pooling or multiplexing) improves server scalability by reducing load associated with concurrent connections and connection rate to SharePoint servers. When enabled, the BIG-IP system maintains one connection to each SharePoint server which is used to send requests from multiple clients.
In all case check the deployment guide for sharepoint 2016
regards,