This is a long read, but I am frustrated by the approach of the IT staff so I am trying to figure out if I am wrong, or I need to fight the battle and push for compliance.
1. Install of Sage 100c Advanced 2022.03 in 32 bit mode.
2. Server 2019
3. 68 Sage users.
4. 4 load balanced RDP servers that all users log in to access Sage 100.
5. They are a 24/7 operation, meaning that there are users that are actively working in Sage 100 all the time.
6. Many users do NOT log out of Sage 100 at the end of the day.
7. Many users close the RDP session with the X, instead of logging out of the session.
7a. I believe this is important because, I don't think the load balancing is reconnecting a user to session that they left open if the server with the existing session is not the server load balancing determines they should connect to. I don't know enough about the load balancing to know if this can be controlled to force reconnection. My evidence of this happening comes from the Sage 100 folder that lives in documents being a problem when users connect sometimes. They use roaming profiles and there are times in which you have to rename the Sage 100 folder in Documents in order for the user to log in. I am of the belief that this is because there is a Sage 100 session open for the same user on another RDP server. I believe that this will result in that other session becoming an orphan.
8. When maintenance is done, they tell users to get out by X time, due to 6 & 7 above this means that when the host is sopped or server rebooted there may be 20-30 sessions showing in Master Console that may or may not be orphans and they may or may not be people who are actively working in Sage and ignoring the request to get out.
The there are 3 problems occurring that I believe are a direct result of 6, 7 and 8.
A. The users who have log logged out of Sage and not logged out of the RDP session - these tasks are becoming orphans through some action that effectively terminates or times out
B. The users who have log logged out of Sage and not logged out of the RDP session - these tasks are becoming orphans when they log into a different RDP server.
C. While A & B may be contributing to the problem, the maintenance methodology is a believe affecting the workstation and session files in MAS_SYSTEM, which then creates different errors that users logging in and using Sage experience. These problems go away for a period of time after we let the host recreate those files through renaming and restarting the host. However within 30-45 days we are right back in the same place.
No amount of discussion with the customer has yielded anything other than, we tell them to log out, log off or get out, we have no way to make them comply. But the frustration over the 3 problems keeps increasing. I would like any thoughts or feedback you may have to share. Thank you in advance.
