We have an environment, ready to go-live on Jan 2, with just 2 AOS servers, with servers being load balanced. So, if a user goes into AOS1 and personalizes a grid, then exits and enters again, but now hitting AOS2, his/her personalizations are not there. We have tested this and it appears that sometimes it works, but many times it doesn't. And we've found that in some cases, I could personalize a grid, then do a couple more updates to the grid, but if I hit the other AOS server, it still shows the personalization from the 1st time.
I've had a technical representative from our consultant team look at this and he hasn't been successful yet in figuring it out. He also submitted a ticket to MS. He tried to synchronize assembly cache over the weekend, but this did nothing. All code is in sync and all kernels match.
Now, one solution is to save the grid view personalized then load, each time a user hits a new AOS server. But, this does not seem to be the correct behavior. This could be an easy work-around for us, having just 2 AOS servers. But, what if we added 10 more AOS servers?? This loading of each grid personalization would become very cumbersome.
Any help with this one would be greatly appreciated!