run mezzmo server as

[ftanner]

Before Mezzmo v5.0, Mezzmo server always ran as a Windows service on your computer. This works great - but quite a few users had problems when they tried to access and stream media files from their NAS drives on their home network. The problem is related to access permissions issues where Mezzmo server running as a Windows service under (by default) the Windows Local System account could not access your files and folders on your NAS. This can be fixed with some configuration changes of your Windows service and/or NAS permissions (see FAQ - http://forum.conceiva.com/showthread...r-home-network).

For Mezzmo v5.0+, we've introduced a new method of running your Mezzmo server - i.e. as a console application that runs under the Windows account that you are currently logged into. This fixes any of these access permission issues that NAS owners often complain about.

In general, we now recommend using the console application method as the simple, trouble-free method.

The problem with this is that you must be logged into the workstation in order to run a "console app" That defeats the whole purpose of having a dedicated device for it that you don't want to always be logged into. In addition, this introduces various security concerns.

I would highly recommend working on getting the service method working correctly. Third party services should NEVER run in the Local System context unless absolutely necessary (such as system management) as this introduces various security vulnerabilities. The service should be running under a named user context and all application functionality should run under this context. In another thread, there is an issue utilizing the web interface when running under a named user context. This is ESPECIALLY important when you consider that people are allowing access to Mezzmo from the Internet via the web interface. You *ALWAYS* want to run services under the LEAST privileged security context that you can get away with for application and device security reasons.