Mar 02, 2018 06:10 AM|Brando ZWZ|LINK
According to your description, I suggest you could follow below point:
By default, ASP.NET stores session information in the server memory. This configuration is known as in process.
In multi-server architectures, a single user’s request can be sent to a different server. A user may start a session at one server, but later requests are sent to a different in-process server.
One way is enable client affinity feature.
Details, you could refer to below article.
Another way is use ASP.NET State Server service, and Microsoft SQL Server to share the session state.
2.Synchronize Configuration and Content
A Web site’s security, performance, and many other aspects of its behavior are defined by the configuration of the Web server. Multi-server sites must have the configuration synchronized between all the servers to provide a consistent experience to users
whose requests are sent to different Web servers. ASP.NET makes it simple to synchronize configuration between multiple servers because all configuration information is stored in the virtual server’s path as XML files. These files have a .config file name
More details, you could refer to below article.