OK, here's a tutorial.
HOW TO INSTALL ZUMOCAST ON WHS
ZumoCast can be installed on Windows Home Server (version 1—everything I say here pertains to my experience with version 1, not WHS 2011) and works well for streaming content and file access offsite. Installation itself is unproblematic; it is just like installing ZumoCast on a PC. Unfortunately, ZumoCast is designed to work only as an application on a PC with a user account logged in. Therefore, ZumoCast as normally installed will work on WHS only when there is a session logged in from a Remote Desktop Connection. Once you log off, ZumoCast will report that “the server is offline.” You can close the RDC window without logging off, and ZumoCast will continue to provide server access, but if the server restarts for any reason, ZumoCast stops working until you RDC in to start a new session.
A way to solve these difficulties is to install ZumoCast to run as a Service on WHS. This resolves both problems just mentioned, because a Service can be set to run automatically on server startup and can be given a user login account to run under. It turns out to be relatively easy to set up any application to run as a Service on WHS. Basic instructions are here:
http://support.microsoft.com/kb/137890. The two programs needed to follow these instructions (srvany.exe and instsrv.exe) can be obtained here:
http://www.microsoft.com/download/en/de ... x?id=17657. What follows is a recast of the basic instructions with specific advice based on my experience setting up ZumoCast to run as a Service under WHS.
1. Download and install the Windows Server 2003 Resource Kit Tools from the link provided above.
2. Open a DOS command prompt (CMD.EXE) and execute the following command:
“C:\Program Files\Windows Resource Kits\Tools\Instsrv.exe” ZumoCast “C:\Program Files\Windows Resource Kits\Tools\Srvany.exe”
(This command is all one line.) If your path to these programs is different, change it. If your path includes directory names with spaces as above, you must include the quotation marks. Otherwise, they are not necessary. Close the command window.
3. Open the registry editor (Regedt32.exe). Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ZumoCast
If you can’t find this key, you’ve made a mistake in the previous step.
4. Now we want to add a parameter to this registry key to tell the system what executable to run for the Service. From the Edit menu, select New|Key. Make the key name Parameters.
5. Select the new Parameters key, and from the Edit menu, select New|String Value. For the name, put Application. Then pull down the Edit menu again and select Modify (with the new “Application” value selected). For the value data, type:
“C:\Program Files\Zecter\ZumoCast\zumolauncher.exe”
Again, if your path is different, change it. The quotation marks may not be necessary here. I used them and it worked.
6. Close the registry editor.
7. Services created this way are set to start automatically on server startup. But we must still add a login for ZumoCast. Open Services. Scroll down to ZumoCast. If it isn’t there, you’ve done something wrong. Double-click it and select the Log On tab in the Properties dialogue. Click the This Account radio button and enter an account name and password. I used Administrator, but I should think any (that has the relevant content access privileges) would do. Click OK.
8. If ZumoCast is still running from before its new incarnation as a Service (there’ll be a ZumoCast icon in the Systray if this is true), better close it. Then in Services, start it.
That’s it. You should now be able to logoff your RDC session and still access server content through ZumoCast, and you should be able to restart the server and have ZumoCast start automatically.