Hey @robbbby, if you want to move your Roon core to a different PC, just go ahead and install it on the 2nd machine. When you attempt to launch it as a core you will be given an error message that says you’ve already authorized your first machine, and you’ll see an option to unauthorize it. Unauthorize the first machine (you’ll be automatically logged out), and authorize the new one. You can then launch switch to a remote on your first machine.
As far as your remote question, we don’t support that configuration just yet. You can initiate playback (from computer A’s library) from computer B to its own “private” zone, but other devices can’t play to computer B’s private zone, unless your stereo is a shared network endpoint.
However, we’ll eventually be releasing a standalone RoonSpeakers package that runs as a service. It would be accessible regardless of whether the remote is running/connected, and would behave just like an MS200–discoverable and controllable from anywhere on the LAN. This package is meant to solve your exact use case.
Private zones will remain private–they’re meant to address a different set of needs, and we don’t want to create confusion by creating two mechanisms to accomplish this.
Hope this helps! We’ll be publishing more information about RoonSpeakers in the near future.