I'm fairly clueless about dism, but oops. I missed a few files. To get the rest of the media decoding, you need to copy these files: hevcdecoder.dll mfh265enc.dll msauddecmft.dll msmpeg2adec.dll MSVP9DEC.dll and register them. Only msmpeg2adec.dll and msauddecmft.dll should be needed for AAC. For some reason I was (temporarily) getting decoding without msauddecmft.dll. Those files are from Windows 10 1607 and work fine.
For me the audio didn't work even using the lav codec (I mean outside vivaldi, which doesn't used them anyway) so I gues something more than just the codec was missing Whatever. I didn't bother to make a list given most of the missing files were already installed by dism so I don't have an exact list of what was copied by tp5. I used te files from tp5 and not w10 because w10 has way more files and following the "quick and dirty" approach more unnedded trash would be dragged. Also MS already broke the WMC with msmpeg2vdec.dll on newer 143xx builds, so I felt more comfortable using the older version
I had tried the \\server method before and it made no difference, but the computer browser service has solved it entirely so a big thank you. I am kind of shocked that this has been deliberately turned off since about TP3 or 4, particularly that even the sharing section of the Server Manager doesn't even give you a tiny hint it was disabled. It never was before those in any previous version of Server... Another bizarre Microsoft choice. Go figure!
Heck I couldn't even get server to enable network discovery. Nothing on my network was reachable. Tried all scenerios to fix issue...finally shut her down. Went back to Enterprise. Will wait until autumn to grab server again.
I saw bluetooth is enabled in this Server 2016 Desktop gui release. Although there is one big difference between this and windows 10. In windows 10 all bluetooth devices are paired and drivers are installed. In this server 2016 some devices only pair and drivers are not found.Like for instance Lenovo bluetooth wireless mouse is not working it says missing someone broadcom driver. So I thought I export the drivers from Windows 10 (same platform x64) but server 2016 doesn't accept the driver. Anyone have a clue about this?
Yes looks like some BT drivers are still missing. Short answer, use the toshiba stack. It's better anyway than the poor MS one.