Rhino on Windows Server

Two different experiences running Rhino on Windows Server 2019:

Why the difference?

I really would like to switch my main machine to Windows Server, even if getting a Windows Server license is costly. But that money is well worth the time I safe, and anyhow, it is possible to run a trial installation for up to three years. Regular Windows 11 Pro is just too bloated, buggy, and distracting. It’s just too much pain to operate.

OK, I just fired up another EC2 instance with the AMI: NICE DCV for Windows (g3, g4 and g5 graphics-intensive instances)

This one is based on Windows Server 2019 Base, same as a related AMI for gaming.

Well, Rhino does not run there, although I thought it did run in the past. But probably my memory is failing me. I certainly did use EC2 servers with NICE DCV, a desktop streaming solution, a few times to run 3D software, for example Agisoft Metashape (photogrammetry). People also use these instances, with Windows Server, for gaming.

I assume, the reason that Rhino doesn’t like to run on Windows Server comes down to licensing, i.e. preventing people from simply using a single user Rhino license to serve stuff on the web. This is not my intention. I just want to use it for modeling on a fast and robust machine. :frowning:

Got Rhino to start on Windows Server 2019 Base on EC2 by editing some registry values:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions:

    • ProductType: WinNT
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion:

    • ProductName: Windows 10 Pro

    • EditionID: Professional

    • InstallationType: Client

No idea if that breaks anything long term, but I just use remote machines temporarily if I need something more powerful than my local machine. I quickly install Rhino and sync the directory I’m working on using SyncThing. Currently I’m in Hong Kong. When in Europe, I use Shadow PC.