[HOW-TO] Roon and RoonServer on Windows Server 2012 R2

[HardrockInMiniMac]

On 27.2.2018 at 10:54 PM, tboooe said:

I run HQP and Roonserver with Server 2012 R2 Essentials without any problems.  In Roon settings, you enable HQP and output to it.  Simple.

 

The NAA is an application that runs on a separate device like a Raspberry Pi or Windows PC.

I can do so too, but Roon or HQP alone sound better in my system than both together - Even in Shell Mode minimal Server 

[HardrockInMiniMac]

13 hours ago, tboooe said:

Thank you for the reply.  When I converted from minimal server mode to core mode and ran AO again, I did not see an option to install Roon support.  I am using 2.2 b6 and have the latest version of Roonserver.

Will see what Phil says but I have tried and I end up with light blue frame around the DOS shell after being stuck in reboot. before I had Roon Server running as shell replacement, switched to Core mode and came back in minimal server mode with some Roon related error messages along the way i.e. "can't find this or that .dll"...

 

So I believe it is still not working in Core mode. But we will see...

 

Chris

[HardrockInMiniMac]

Have to test further....

[HardrockInMiniMac]

Seems to be working now:

 

1. Switch to Core Mode - reboot

2. Set Roon as Shell - reboot

3. Run AO - reboot

4. Enter remote desktop. Still black screen = Roon is shell

 

In my case I have to then enter remote desktop once and Roon is working

 

Chris

[HardrockInMiniMac]

Odd it is. I am not playing mp3 so I do not know. But I know I have had light grey frame on the CMD box which means Core mode and Roon was playing FLAC files through Core mode. However, I found the network connection not stable, sometimes could not connect to remote desktop while playing files and so on. 

 

So I have now reverted back to minimal server mode with Roon as Shell as that runs flawless. 

 

Chris

[HardrockInMiniMac]

13 minutes ago, AudioPhil said:

 

RoonServer does work in core mode on 2012 R2, but ONLY with ASIO devices. Not with WASAPI or Kernel-Streaming (because Roon does not support KS and Core mode in 2012 has no WASAPI).

 

best,

AudioPhil

Hi Phil, thanks for clarification. I am fairly new to your level of audiophile optimized and have only last week installed Server and AO onto my MacMini, so forgive me the following questions:

 

1. Shell: Roon Server & HQP - will this also work in Core mode?

2. SOTM- sMS-200 ultra - I would have to pick HQP endpoint, correct?

3. I have had it working with only Roon Server in Core mode, but I have seen hiccups:

 

- It took a while for Roon Control to see Roon Server

- Roon control was not willing to transport audio files until I manually connected to the shared audio folder on the mac mini through Finder and managed to fire off remote desktop as well

- Remote desktop also wasn't willing to connect for some time, then I had Bootcamp error messages

- I have seen a few times that the Roon connection from Roon Control to Roon Server gets established the moment remote desktop works

 

In AO (latest beta), I had network services, Remote desktop and your other recommendations enabled but drivers and services disabled. I also have Lyngdorf ASIO drivers installed but as Lyngdorf sits behind SOTM it should not play a role that these drivers probably got disabled as well, should it?

 

Maybe you can give a few more hints as to how this must be setup correctly for Core mode.

 

Thanks

Chris

 

[HardrockInMiniMac]

It is all up and running nicely.

 

Core Mode:

Windows 2012 R2 with Roon Server and HQ Player as shell replacement on Mac Mini 2014

 

Tick in the box.

 

Chris

 

 

[HardrockInMiniMac]

Frederick, it is different with 2016 than with 2012.

 

I wrote myself a complete installation manual if I have to do it but I don't have access right now.

 

So what you have is exactly what I had: Roon can see the core and gets stuck in "initializing".

 

You must edit the network policies in 2016, otherwise it won't work. There are several things to do in order to make 2016 see your private network as private as it is set as "public" per default. This is the key. Without this it won't work and it is not sufficient to allow for remote connection and/or toggling DHCP and fixed IP - it got to be a fixed IP anyway. 

 

With 2016 Core it is of course a bit more tricky and work to change policies (powershell), but I have also noted the required commands somewhere. It is basically all available from the internet if you know what you are looking for.

 

Chris

 

 

[HardrockInMiniMac]

4 hours ago, frederick184 said:

Ok, this is driving me nuts.

 

Started over with fresh install.  No more dual boot machine.  Dedicated PC.

 

WS 2016 standard core installed, then Roon Server 1.5, then AO 2.20 in Ultimate mode, chose Roon support and Roon as shell.

 

Changed to a static IP address and changed network policy to private.  All Roon processes are up and running.

 

Tried to connect to Roon from both iPad and phone.  Still says “initializing”.

 

Colin

 

Ok, here are my actions that worked in this order and right after first boot of Win2016:

 

• in tool local network policies change to "privat" AND "user can change"
• Set fixed IP, Gateway and DNS
• Set Computer network name
• Reboot
• Check if router / switch can see Windows 2016
• Check remote access to Windows 2016 with Microsoft remote desktop from any machine
• If you use BootCamp, do it know and install latest drivers
• Reboot
• Check for Windows 2016 updates and install
• Check for unknown devices and de-activate them
• Reboot
• Remote management will be enabled now
• I have then set my remote share and tested access through the network (upload/download)
• Install RoonServer64bit
• Check remote access to Windows 2016 again
• Try to connect Roon Remote to Roon Server (will not work)
• Install AO 2.2 with Roon Server support
• Reboot
• Licence AO 2.2 by starting ST tool
• Disable write caching on SSD
• Disable power saving on LAN Adapter
• Reboot
• Run Roon AO ultimate with safe settings
• Test SMB connection to share again
• Probe Roon Remote: it finds Roon Core on Server
• Enable auto logon in AO service tool
• Reboot
• Roon Remote will find Roon Core on Server automatically

 

I have protocoled each and every step of also other tools (HQP, Windows Commander ...) so that  I can replicate my installation anytime and do not need 2-3 days again. Some might not be relevant and I do not care. It works. With the hassle, trust me, I feel for you! 2012 had been a walk in the park in comparison.

 

I have then started to use more aggressiv settings in AO. Connection never lost. I then tested all AO possible settings and combinations and never lost connection.

 

Just for the record, the following AO settings I have left ON:

 

• Roon Support
• HPET
• WASAPI
• USB Opt
• Intel WMI

 

With that I have Roon remote, MS remote desktop and SMB working.

 

Chris

[HardrockInMiniMac]

Hi, It is easier with GUI, isn't it? It is a very good idea to have an image but it will work all the way.

 

I found this for you:

"With AO 2.20B5 when answering YES to Roon Support the Media Support is added - no need for the media pack from MS."

 

I cannot remember this error message that you got on my machine, I only had troubles with the network setup as mentioned before. Did you also replace the shell with Roon?

 

I am 100% sure Phil will be able to help you quickly and if it takes some time for him to answer in here then send him a message through his webpage. It should be easy to solve.

 

Good luck,

 

Chris