If the product says it can run on Windows 10 or 11 and falls under the 20 connection limit then go for it but with one caveat: Make sure the hardware has ECC memory to avoid a memory flipped bit error that can wreak havoc and at least a RAID 1 array between two SATA SSDs.

@PhlipElder said in Can you run a Windows desktop OS as a server to run AVImark Veterinary Software?:

@Obsolesce said in Can you run a Windows desktop OS as a server to run AVImark Veterinary Software?:

@JaredBusch said in Can you run a Windows desktop OS as a server to run AVImark Veterinary Software?:

Historically, QuickBooks has only used file sharing for this. The remote users are opening the QuickBooks data file over the network. This matches the restrictions last I knew.

exactly this.

Please reread the Device Restrictions section without all of the underlines especially the part where "internal" is mentioned and "the following purposes:" after that. It's very clear that one can use a Windows Desktop OS for shared internal services. That hasn't changed at all.

By very definition: Peer-to-Peer.

I've been doing this a very long time in the SMB/SME markets. Former SBS MVP and all that.

Tell me a time when any IT tech in those markets hasn't encountered a peer-to-peer setup of desktop operating systems sharing who knows what in a rat's nest of patchwork.

If peer-to-peer wasn't a thing, or illegit as being claimed here, then why did Microsoft have the clause I pointed to included? That is by very definition peer-to-peer.

Again, definitions of words are important here. We can't apply IT Tech definitions to legal definitions. The whole 32-bit memory limitation thing is a good example of that. All y'all know that Windows 32-bit being held down to 4GB of addressable RAM was an arbitrary choice by Microsoft to force-sell their Advanced/Enterprise products that could address more RAM right?