Sage 100

Another heads up. Not sure if this has been disgust before either. If you are running 2016c Advanced / Premium and run via Terminal Server / Citrix there is a bug we reported to Sage yesterday that we're expecting a hotfix for. Let's say User A sets Launcher to the Standard desktop. User B as soon as they login to MAS and set theirs to Standard desktop, it causes ""Sage has stopped working"" (application crash / page fault type error). So any 2nd user who tries to set Standard desktop blows up. It only happens when there's TS / Citrix in the picture. The workaround for now is to use Classic desktop.

Hmmm. Second issue where the workaround is the Classic. Importing legacy data with VI also stumbles with 100c Standard

I'm not sure this is just advanced, we had a client on standard version with the same issue; yesterday, Sage gave us basically the same resolution 1.Change the User Settings to use Classic instead of Standard (logged into Sage as that user) 2.On Terminal Server Logged in as Each user a. Delete the Sage folder under ""my documents"" / ""document library"" b. Then log into Sage as that Sage User and you will get prompted for the ""which desktop"" question - - select Classic

The 2016(c) PU1 hotfix for this multiple users running with the Standard desktop via Terminal Server / Citrix issue has been posted on the portal as LM-5013T and will be included with PU2. We tested with multiple users on Advanced running the Standard desktop and it works ok. It should work on Premium and Standard too @DavidOverholt Article: https://goo.gl/tTEv9A Fix replaces the Launcher.2016.exe file.