How to run Serviio under WIndows 10

I want to start this thread for anyone and everyone who is running Serviio and has or will upgrade to WIndows 10.

I have upgraded to Windows 10 (2 systems so far; one on hold) and things are not exactly smooth running under Windows 10.

So hopefully this thread can be used to post issues and solutions as time goes by.

Paul

First, you cannot run Serviio service as the default user. You have to change the user to your logon name. This was documented for my by user [atc98092] in this thread:

viewtopic.php?f=5&t=18487&start=20#p102014

Kudo's to [atc98092] for that major fix.

Paul

Once I set the Serviio service to my logon, things got better.

But, I have since discovered that Serviio will not scan a DLNA (mine is a WDMyCloud 2TB) if the source directory is MAPPED! Don't know why. But it only works if you select the actual network resource in Serviio Console for the multimedia type you are setting.

Paul

[DenyAll]

Thanks for starting this thread- a good initiative and worth continuing.

Having said that - neither of these issues is however specific to Windows 10.

The first issue is known and relates to networked drives. Users upgrading to Win10 without network drives will not experience it. It is common to all operating systems and relates to access rights. It's documented in the FAQ here: http://www.serviio.org/component/conten ... e?id=21#q5

The second issue is also known and relates to how and when a drive is mapped. It's also documented in that same FAQ. Once again this issue only affects users with network drives.

Although I haven't upgraded to Win10 as yet I have been monitoring things. It appears that the upgrade for most has gone very smoothly wrt Serviio - the main issue has been for users with network drives as you have, and a few users have had to re-install Serviio over the top (not an onerous process).

For users with networked drives, I suspect the reason your seeing this (known) issue for the first time is that the security token for the "System" user is being changed during the upgrade...but I would need to test that theory first.

[atc98092]

I agree that Windows 10, in itself, does not seem to be an issue. I rebuilt my daughter's media server with a clean install of Win 10 and then installed Serviio 1.5.2. The media is all on local drives, and it is working fine.

There was an issue after I first brought it back to her house and changed its IP address (uses the same as my server, so couldn't use that at my house). I forgot to restart the Serviio process so it used the correct IP address for broadcasting on the network. Serviio saw the devices, but no device saw Serviio. After a reboot all was well. And that too was not a Windows 10 (or even Windows specific) issue. It was me being forgetful!

I can see that those folks who have been successful at running serviio under win 10 seem quite happy but I actually have a problem. I wonder if any one can solve it.

I upgraded win 7 to win 10, all seemed ok
I then installed serviio, all seemed ok (I should say that my firewall is McAfee)
Started the server and console all ok
console can see some IP's all all with generic DLNA profile
my WD TV live is not shown on the list
my WD TV live does not find serviio as a media server

Any help would be appreciated. By the way links in previous posts on this thread do not go the bitbuket subject stated.

Thanks

[DenyAll]

By the way links in previous posts on this thread do not go the bitbuket subject stated.

Thanks - it should have pointed to the FAQ, not bit bucket. Have fixed that.

wrt to your issue, check that their are entries in the McAfee firewall that allow access to the Serviio application and/or Serviio's ports (TCP port 8895 and UDP 1900). Also, do you have any other DLNA devices (TV's etc rather than other PC's) and if so, are these being detected?

One thing I noticed when I did my upgrade to Win10 was that the "Bound IP address" in "Network Settings" on the "Status" tab of the console had changed.

I have VMWare Player installed and for some reason it had switched from my LAN card to one of the VMWare created adaptors meaning that Serviio was working but "connected" to the wrong LAN...!

Hope that helps

[atc98092]

One thing I noticed when I did my upgrade to Win10 was that the "Bound IP address" in "Network Settings" on the "Status" tab of the console had changed.

I have VMWare Player installed and for some reason it had switched from my LAN card to one of the VMWare created adaptors meaning that Serviio was working but "connected" to the wrong LAN...!

Hope that helps

When you have a multi-homed computer (more than one network adapter) things like this can happen. You can't use the Auto Select function, but must choose the correct NIC/IP address. Serviio (at least for now) cannot broadcast on multiple IP addresses, so you have to make sure you have the right one selected.

...... you have to make sure you have the right one selected.

I did, until the upgrade process changed it..! Or rather the upgrade process made Win10 enumerate the NIC cards again and assigned them in a different order, so Serviio was fooled into pointing to the wrong one.

At least that's my theory.

[atc98092]

...... you have to make sure you have the right one selected.

I did, until the upgrade process changed it..! Or rather the upgrade process made Win10 enumerate the NIC cards again and assigned them in a different order, so Serviio was fooled into pointing to the wrong one.

At least that's my theory.

And a reasonable theory it is!

Previously, in my journey to a happy windows 10 PC I said.....

"One thing I noticed when I did my upgrade to Win10 was that the "Bound IP address" in "Network Settings" on the "Status" tab of the console had changed."

Changing that setting manually and restarting the Serviio service worked fine for me, but it seems that the setting change does not survive a reboot. Could this be since changing the account under which Serviio runs the console now has no rights to update the config file..?

What and where is the config file, and how can I check and update it to ensure that I don't have to manually update the bound IP address after each machine reboot..?

[DenyAll]

Just checking - You did press Save after binding the address? Also, is your server on a static or reserved address, which is a must if you bind the address.

No, the account you use won't cause this. The console talks to the server through REST. The server writes the config, not the console.

The config is stored in your library in a Derby database, which is for all extensive purposes inaccessible.

You could try using the serviio.boundAddr system property to force the binding on startup (see http://www.serviio.org/component/conten ... properties)

You did press Save after binding the address?

I thought I did, it's always possible I didn't.

is your server on a static or reserved address, which is a must if you bind the address.

It's a statically assigned DHCP address. The router has an option to always assign the same IP to the same MAC, and that is set. So I'm good there.

You could try using the serviio.boundAddr system property to force the binding on startup

Thanks for the pointer, I'll look into that one.....