Sage 100

Anyway found a workaround to install SAGE 100 Advanced v2016 in a windows xp workstation and a windows server 2003???? net framework 4.5.2 is giving me problems....thanks

What type of problems? In some cases, the framework has to be applied via the server install routine itself and won't self-install. I'm not at all sure what the exact issue is here.

These OS's are no longer supported so the REAL solution is to upgrade. This happened to me. You can install Sage on a WIN 7 WS, then copy the folder to the 2003 Server. This should suffice until you have to install any product updates at which point you will have to copy the folder back to the WIN 7 WS, install the PU, then copy back to the 2003. Not possible to install the workstation client to the XP. There may be some workarounds, but you will be money ahead in the long run to just upgrade your machines and the OS. As I said, OS is no longer supported and the machines have got to be dog slow in processing.

I've done it with Sage 100 2015 before, I had to install all of the Microsoft pre-requisites, separately, before running the Sage install at the server.

Jeff...copy the complete windows folder from the ws???

Install Sage 100 on a acceptable workstation OS (e.g. WIN 7). Copy the MAS 90 folder from the WIN 7 workstation to the 2003 server. The problem you have is that you still can't install the workstation client on the 2003 server or the XP. You can probably use the existing 2015 workstation client on the XP to run v2016, just copy the launch ICON and change the pathing of the copied icon. But as I said, it is time to have the talk with the client about upgrading their IT infrastructure.