Search the Community
Showing results for tags 'windows server'.
Found 4 results
I finally had some time to get myself "into" Roon last night. Roon & Windows Server have somewhat worked in the past, but the overall experience to get it working was not very convenient. These steps were needed to get Roon or RoonServer working on Windows Server 2012 R2: - Add the Windows Role "Essentials Experience" (which actually converts a standard edition into an essentials edition) - Add the "Windows Server Essentials Media Pack" So i used the last night to get rid of all this inconvenient steps, and yes it does even work in Minimal-Server Mode now. I focused my testings on RoonServer and these are the needed steps to get a Roon Core working on Windows Server 2012 R2 (no matter if GUI or minimal-server Mode): - Install Windows Server 2012 R2 & all available updates - Install AudiophileOptimizer 2.10 - Install your DAC Driver - Install RoonServer - Stay in GUI mode or switch to Minimal-Server Mode (Core Mode is not supported!) - Run AudiophileOptimizer in advanced or ultimate mode - Say yes to "Install Kernel-Streaming and MediaPlayer support" - Say yes to "Add roon support" - Say no to "disable network related services" - Do not disable Windows Management Instrumentation (WMI) Enjoy, Phil OPENGL WARNING: If your graphic card driver for Server 2012/2012 R2 offers no OpenGL support (and you get OpenGL Errors when you start Roon) there is nothing AO could do against it. AO cannot change or extend the functionality of a graphic card driver. Consider using RoonServer instead of Roon or switch to Windows 10 if no OpenGL compatible graphic card driver is available for server 2012/2012 R2.
Hello Folks Not many days ago I was whining about AO 3.00 will probably not bring back WASAPI in Core as AO 2.20 did for Server 2016. I invested more than two months in the adaption of just the WASAPI part for Server 2019 but to no avail... But last evening things changed dramatically... I found the missing piece and can now give you a short step-by-step guide on how to achieve the entire audio stack (WASAPI/KS/DirectSound) in Windows Server 2019 Core. It was a heck of a long night..... goosebumps!!! 😎 As some of you beta testers might have noticed there is a little inscription on the beta portal regarding "Dan". I got a few questions about that, who Dan is, and why i dedicated the Beta portal to him. Dan is a good friend of mine since many years. He is a fellow forum member and an AO user since over 5 years. He was one of the very first ones to start exploring the audiophile nirvana together with me and the AudiophileOptimizer. Dan helped me a lot in all the alpha and beta testing phases, he helped me check the PDF guide for correct spelling and writing, he spent ideas for new features in AO, and he guided me through many other things as well. AO would never been there where it is as of today without the great help and continous support of Dan and many others who helped me during all these years, challenges and sometimes also very tough times. Sadly Dan is very ill since quite some time now. He's illness got much worste lately and it reached a point where's just nothing left to do for the doctors. Dan won't be here anymore by the time the final release of AO 3.00 will made available to the public. I actually didn't dedicate the beta portal to Dan, but I rather dedicated the entire AO 3.00 to him. He just deserves this. So the final release of AudiophileOptimizer 3.00 will be in Memory of Dan. A great and true friend who will be deeply missed. My biggest wish is that he makes it at least to february 7th so he can celebrate his 35th anniversay with his beloved wife. If all our prayers are strong enough, then he might have a chance to reach that goal. So, what do you need after all to get WASAPI working on Server 2019 Core? You need Windows Server 2019 in Core mode, AudiophileOptimizer Beta 31 (or newer) and the Windows Server FOD (features on demand) ISO. Then just follow these simple steps: Install Windows Server 2019 in Core mode Mount the FOD ISO and install the "Server Core App Compatibility" using this command: DISM /Online /Add-Capability /CapabilityName:"ServerCore.AppCompatibility~~~~0.0.1.0" /Source:drive_letter_of_mounted_ISO: /LimitAccess (If you need more detailed installation instructions for FOD see here: https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19) Install AO 3.00 (or newer) Do a full run with AO, say yes to "Install Kernel-Streaming and MediaPlayer support", say also yes to "Install Roon & HQPlayer Support" After the reboot fire up ServiceTool and launch the DriverHelper Install your DAC/DDC driver using the DriverHelper Start the Device Manager using AudiophileShell or by typing "devmgmt.msc" Select your DAC devices and uninstall them again, but do not select "delete the driver" Once uninstalled click the rescan hardware Icon, your DAC driver should now be successfully installed Do not continue until you verified that Kernel-Streaming is working -> play some music Once you are sure Kernel-Streaming is working launch AO again and install the WASAPI-support (AO -wasapi) I have tested WASAPI with Foobar2000, JPLAY Femto & RoonServer, it works just like a charm. The only thing that does not work is the "test tone" in the windows audio control panel. I have no idea why, but i can live with that as long as music playback works stable At least for now... Enjoy it, AudioPhil
It is possible to change your Windows Server Standard edition to Datacenter edition on the fly. This article will show how to do this. - You can only change the edition "upwards", meaning you can go "up" from standard to datacenter, but not "down" from datacenter to standard - To see where you are/what you have enter Dism /Online /Get-CurrentEdition - To see where you can go enter Dism /Online /Get-TargetEditions - To actually change the Standard into Datacenter edition enter Dism /online /Set-Edition:<edition name> /AcceptEula /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX - So with a Standard Edition installed the command to change to Datacenter edition is: Dism /online /Set-Edition:ServerDatacenterCor /AcceptEula /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (Here you need to enter a valid Datacenter Product Key for this to work) - If you want to change edition on an already optimized system, don't forget to do a reset via ServiceTool first - All this is documented here: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-windows-edition-servicing-command-line-options - The only difference between Standard and Datacenter is the licensing, otherwise both are identical bits and bytes wise. Datacenter in Server 2019 the only difference to standard is regarding to the virtualization rights. With one Datacenter license you are allowed to install one Hyper-V Host and run an unlimited number of virtual machines on it (Datacenter or Standard). In the older days there where more differences in terms of how many CPU's the OS supports and what the maximum RAM supported is, but with Server 2019 it all got the same (64 CPU's and 24TB of RAM): https://docs.microsoft.com/en-us/windows-server/get-started-19/editions-comparison-19
Be sure to install the following Updates and Components before you install HQPlayer: - KB2919442 Servicing Stack Update (March 2014) https://www.microsoft.com/en-us/download/details.aspx?id=42153 - KB2919355 April 2014 Update Rollup https://support.microsoft.com/en-us/kb/2919355 - After installing the two above mentioned updates, reboot and install all available updates - Visual C++ Redistributable Update 3 (September 2016) https://www.microsoft.com/en-us/download/details.aspx?id=53840 - Install latest HQPLayer Best, Phil