I'm using Sage 50 Premium Accounting 3-User, and trying to upgrade from v. 2017 to 2018.
Sage has announced that v. 2017 is going into Obsolescence on Feb 28, 2018.
Sage requires an upgrade to version 2018 in order to continue using the software, so this must be done in some form within the next week.
This would be fine, except I just discovered that v. 2018 will not install on our server. It is an older HP ML-310 running MS Server 2008 Foundation.
Sage 50 v. 2018 requires at minimum Server 2008 R2 operating system.
I will eventually upgrade this server, but it is a major undertaking for our small one-person (me) IT department.
I am trying to discover if there are any hidden tricks which will allow me to fool the Sage software into installing successfully on the Server 2008 Foundation system.
If I cannot figure a way to install the Sage update on my existing server machine, I will be forced to either hurriedly buy and configure a new server (2016 Essentials?) or just install the Sage update on a client machine for the short term. Neither of these options are good...
What I would prefer to do is find a way to get Sage 50 working short-term, then just buy a new machine with a modern OS and take my time setting it up and porting the needed apps to the new system.
For more background: We are a small ~50 employee company with this one old server and about 10 workstations ranging from XP to Win10.
Other than the Sage 50 Accounting, I also have three other mission critical applications on the server. These apps are installed on the HP Server, and accessed both locally and remotely by other employees. They are all set up as "Remote Applications" using Terminal Services, so they can be accessed by both local and offsite workers just by running a local ".rdp" file.
I'm not technically astute enough to just quickly buy and set up a new Server 2016 Essentials box and get all of this working within a week, so I need a stop-gap solution. I'm not sure that the "Remote Application" capability even exits in Server 2016 Essentials.
I could survive short-term without offsite access to all except one of the programs, but this one does absolutely need remote access.
Any and all help is much appreciated.