Azure/Server 2016 not logging out admin account properly
We are having an issue with Azure/Server 2016 creating multiple versions of the admin account. This appears to be due to the OS not properly closing down the admin account and then creating another account when logging back in. We see this in the User directory where we find Admin, Admin.000, Admin.BACKUP-0 (not the real names). Sometimes Admin is a shortcut, sometimes Admin.000, sometimes one of the folders is empty. The problem is that when we install software in the admin account, files go into the active admin\documents directory and then when the admin account name changes, our software won't run. Our log out procedure from remote desktop is to use the sign out function in the upper icon above the Windows start button and then sign out of the Work Resources page. We have been told by the Azure reseller that this is the correct procedure. Anyone had this issue and found a solution?How would you build a custom solution based on the following requirements?
Environment: SharePoint 2013/2016 on-premise environment Requirements: Custom List form which needs to retrieve information based on filled inputs during edit > not after saving The information needs to be retrieved via Web Services from other internal applications > the authentication against the already present Web Services happens via Certificate Authentication and cannot be done client side Only users that have already access to the SharePoint site where the list with the custom form resides should have access to the functions to call the web services via custom form My approach would be to create a custom Site or Application Page with code behind with WebMehtods that can be executed client side via JSOM. Is this still the way to go or are there other more modern approach to implement such solutions? I'm aware of the client-side solutions that can be build but we're not able to call the present web services from client-side and we don't want to build new web services that themselves calls the present one because doing thins we'll need to implement a whole new solutions which handels authentication too. Thank you for your answers already in advance. I'm excited about your feedback ;-) Kind regards, Fabrizio
