Sage 100

After performing a test 2015 upgrade for a client on a new server, we are finding that users cannot launch Sage 2015 until we check ""spawn tasks on application server"" for each of the user accounts. I know that using this ensures a ""more stable"" connection, but does anyone have any ideas why it is all of a sudden required of this new server/version?

@AlnoorCassim ?????

Windows Advanced Firewall is turned on at the server.

Beautiful - another nugget of pure gold! Thank you! I will pass on to client right away.