Sage 100

As I wind my way down ""upgrade road"" one thing I keep struggling with is end users where the server was able to run their old version but when I go to download and install 2017 it's a no go. Typically these are 2008 servers which Sage refuses to install to. Am I missing any trick to use 2008 as the server or is the only resolution to upgrade the server to 2008 R2 or better?

Honestly, have them bite the bullet. It sucks but it happened to me when v2016 arrived. I was running 2008 Std. No dice. You could install on a workstation then copy it over to the server. But you can't install wksetup either so you probably have issues with remote support. Also, even if this is a workable route, I think you need information in the server registry for future update installation. After exhausting every thought I had for making it work, I took the server to my hardware guy for an upgrade to 2012 and went on vacation for a week. When I got back, 2012 was working and I was able to install v2016. What was particularly galling was when I bought the box the year before, I specifically told the HW guy to install 2008 R2. When the box was delivered, it had 2008 Std. When I called him on it, he said, Oops, sorry. But don't worry, you won't have any problem. I sent his resume to Sage tech support. Thought he would fit right in. You could tell them if they are on 100c and STD that you can install ADV for better performance and no additional charge.

I'm double checking to make sure that I'm not overlooking a trick. Doesn't seem like I am with respect to server 2008 and Sage 100 compatibility.

I have a client on SBS 2003 and v4.3. Lucky for them they aren't in any hurry to upgrade. I just remind them to have damn good backup......

When I've come across this in the past, I let them know that the server needs to be upgraded, but in order to move forward with the pilot and testing I've performed the installation and upgrade locally on my own machine then upload the MAS90 folder to their 2008 server. Though this will only work with Sage 100 'Standard.' I also let them know they will need to get the server upgraded sooner than later (preferably before going live) because any patches or updates will require the same process and we'll need to charge them for all the additional time.

This is a Microsoft issue with subsequent updates to how the msi installer works. There is a KB on it somewhere. We have been letting clients know a server upgrade is in the cards if they are on something other than 2008R2 or higher.

Thanks, that's the validation I was looking for. I find hardly anyone really wants to read the SPM so I give the readers digest and then send a PDF of the SPM. In most cases so long as they meet minimum requirements to run windows 7+ workstation things are fine. I really only have issues with upgraders who are still on old servers.

We actually check what server O/S they are using before we write up the proposal for the upgrade. If they are on Server 2008 or earlier, we now note in the proposal that the server OS has to be upgraded before we can start the upgrade.

We also require that the server OS is compliant with the SPM.

I've had this bite me as well. The biggest challenge for us has been, the Server OS is A-OK. But then you go to work on a Terminal Server that is 'aged'.