Sage 100

Not Urgent Support, but seemed the best place to ask. Customer is on 2016 Premium and is considering moving to Server 2016. I also have an Advanced customer moving to it for their 2017 upgrade. Has anyone have a customer on Server 2016 and does it seem to be stable, etc? Any advise for users wanting to move to it?

Have a premium using server 2016 to host Citrix and they get all sorts of odd black screens on startup. I don't think Premium is being hosted on 2016 just the Citrix . There seems to be an issue with 2016 in general if you Google within Sage City.

With our windows 2016 server clients, we haven't seen many problems (could be luck?). The only one we have run into is the task scheduler doesn't function which is in engineering. However I would note the security changes with windows 10 so I would expect more of the same as time goes on.

@JeremyFox - The Windows Task Scheduler doesn't work? My Advanced client moving to 2016 has a bunch of Task Scheduler Tasks and this could be a major issue then for them. Can you please explain your 'security changes in W10, expect more of the same' statement? Thanks in advance.

Sure, the location in question is using sage premium 2017, and we are unable to run any scheduled tasks (this can be tested via opening the task scheduler and running the log it 100% bombs out) error 47. engineering currently has it and they are finding more clients with the same bug. I do know they seem to have made a modification to the task scheduler since 2014 however I'm not sure what all was included. for the windows 10 permissions this is when users are unable to run the program as admin due to security concerns. windows tends to change permissions on registry or C: with updates this normally presents in problems printing to paperless office. the solution we have found is to simply go through C: and registry adding users to the sage specific locations (tabbing through all the locations\software or anywhere else sage might be). this fixes the issues while keeping security relatively tight. given that server 2016 is similar to windows 10 i suspect we will start running into similar permissions based issues with server 2016, until sage updates its practices in programming. If someone has a better script or process to fix that I'd love to hear it.

@JeremyFox - Just to confirm, you're referencing Server 2016, not Sql Server 2016, is that correct?

Correct windows server 2016, graphically looks like windows 10, now they also do have SQL server 2016, but that's not the issue here. I'd just test the task scheduler before going live would be my main suggestion if its a critical part. At the moment I'm attempting to write a VBS script to print the daily transaction registers for all 65 companies my client with the problem has (it's working but so far its unable to print to paperless).

@WayneSchulz, just FYI, that black screen issue is supposed to be patched by Microsoft this month and Citrix (if necessary) next month.

@SteveIwanowski Do you have a link to anything I could send to the customer on the above upcoming patch?

Actually, it just dropped today. https://support.citrix.com/article/CTX225819

Thank you!!