a footnote in this thread in case it helps anyone.

Sage runs on (basically any windows OS) and it really does not care if you have windows home edition, pro, windows server. etc.

Windows Server 2008 went EOL a few years ago and it is normal that microsoft have EOL / retirement plans for every version of windows the day they announce new windows product.

You generally need help from someone who can assist with Sage install, migration - modest scope IT project basically - for this kind of thing.  
It will more be about (what is your budget, what is the access requrement, how many staff, etc) that drives what direction it goes

Sage deploy can be anything on the spectrum of

(a) single user with sage on their laptop, 'it just works'

(b) main accountant has sage on their office desktop PC, and 2 x junior accountants on same LAN have sage, and they all share company data living on the master-pc-'server' sage computer

(c) RDS-term server with Sage installed, and 20 staff remote into this and use sage concurrently as they remote-telework from across the globe and drink martinis while remote working from the beach

clearly the install requirements for a>b>c scenario are different. But in all cases your sage install is not really so terribly different. Just all the icing around the edges about how you run sage, from where, how many people etc. that makes the deploy config for a given environment really all that much different.

a footnote in this thread in case it helps anyone.

Sage runs on (basically any windows OS) and it really does not care if you have windows home edition, pro, windows server. etc.

Windows Server 2008 went EOL a few years ago and it is normal that microsoft have EOL / retirement plans for every version of windows the day they announce new windows product.

You generally need help from someone who can assist with Sage install, migration - modest scope IT project basically - for this kind of thing.  
It will more be about (what is your budget, what is the access requrement, how many staff, etc) that drives what direction it goes

Sage deploy can be anything on the spectrum of

(a) single user with sage on their laptop, 'it just works'

(b) main accountant has sage on their office desktop PC, and 2 x junior accountants on same LAN have sage, and they all share company data living on the master-pc-'server' sage computer

(c) RDS-term server with Sage installed, and 20 staff remote into this and use sage concurrently as they remote-telework from across the globe and drink martinis while remote working from the beach

clearly the install requirements for a>b>c scenario are different. But in all cases your sage install is not really so terribly different. Just all the icing around the edges about how you run sage, from where, how many people etc. that makes the deploy config for a given environment really all that much different.