I have tried this on both WHS v1 and WHS v2 but you will soon find out that with no way to keep MC running (as a service) the server instance cannot stay on or stay stable - unless you leave the server open to security problems by staying logged onto the server with a user acct indefinitely. As designed - if you log off the WHS normally - your instance of MC will shut down too and no one can connect.
Yes, this makes total sense. Those other applications use the add-ins to run apps as services
Now - there are bunch of different ways to try and have MC run as a service - but none ever seemed really viable to me - and I didn't like the idea of hacking the server too much - so I gave up on the "run MC from the server" routine and have now just stored my actual music files on the WHS and having the actual "library server" be my main workstation running Windows 7. This setup works perfectly as all my other clients simply connect to my PC as "library server" and play away. My machine is up from 5am to whenever at night anyway - so needing MC actually "running" on the server is a bit of a moot point. Also - there are numerous issues with updating files, tags and other stuff that makes an "isolated" MC on the server seem not that great after a while.
I use a similar set-up. I have the WHS storing all the media files and a main library on a win 7 workstations. I just added a HTPC to the mix and from there used the functionality of loading the main library from the WS. Worked fine which got me thinking it could work the same on the WHS, but still has limitations.
The small glitch in my mileage is that the workstation is my home office/studio next to my work PC and is the PC I use to manage the main library, and as a result goes into sleep mode when not in use. I could switch that around so the HTPC becomes the home to the main library.
Have you tried moving the library 'file' to the WHS and having the clients all load the same library file? I guess there really isn't much benefit if the above works.
[/quote]
I would rather have complete control of all aspects of the main library by being able to edit it in real time on a real workstation and have those changes be immediately available to my clients - rather than having to "remote" into the server all the time and do library maintenance "on the server" using the server based copy of MC.
Yes, we share the same objectives. If the server and library components could live on the server and operate as a service while the interface components to manage them were on the clients that would be the best of both worlds to me. I could have complete control regardless which PC i was using...