Tony Posted July 30, 2015 Share Posted July 30, 2015 Hi, DVBViewer/RS does not store recordings on a network drive after upgrade from Win8.1 on Win10 (Status > Recording Folder > Network_Drive Missing) I don't know whether this is a property of the current built of Win10, or another problem. Upgrade to Win10 took place automatically, completely without any apparent problem, all accessible network disks (3) as read-write. Supporttool.exe runs after updating to the latest version DVBV, therefore, searched for and added support.zip, which are the last entries (29.7) from Win10 ... Quote Link to comment
Tony Posted July 31, 2015 Author Share Posted July 31, 2015 (edited) I clarify the situation somewhat… DVBViewer accepts both ways to record on a network drive under Win8 and under Win10: As the mapped drive Z:\aaa As a network drive \\NetDrive\Public\Shared Videos\Filmy\aaa Recording Service accepts registration only entire network path (which is a logical). Under Win 8.1 is included functional network path Under the Win10 the network path is BROKEN: Status > Recording Folder \\NetDrive\Public\Shared Videos\Filmy\aaa MISSING Edited July 31, 2015 by Tony Quote Link to comment
Griga Posted July 31, 2015 Share Posted July 31, 2015 Searching the web for Windows 10 network share yields severals results pointing out that Windows 10 restricts the shared access to local (not Microsoft!) accounts with username and password, which also excludes guest accounts. So there is evidence that the Recording Service does not get access because it is running in a system account without username and password. DVBViewer being able to access the network drive confirms this assumption. There are sites that propose measures to remove / circumvent this restriction. Maybe you can find something that works. Currently we have no solution for this issue. Quote Link to comment
Tony Posted July 31, 2015 Author Share Posted July 31, 2015 Thanks, Griga. I believe that a solution can be found... Quote Link to comment
Griga Posted August 22, 2015 Share Posted August 22, 2015 There is a solution now posted by a German user. The Recording Service is able to access network drives if it is running in the context of a local user account with username and password. It can be achieved by opening the service properties (after launching services.msc from the start menu under Windows 7, dunno if it is still the same under Windows 10) and changing the account accordingly, which requires entering username and password. There are no known drawbacks up to now. The Recording Service is still runing as a background service and doesn't require the user to be logged on. It's just a different security context. Quote Link to comment
Tony Posted August 25, 2015 Author Share Posted August 25, 2015 I tried this procedure (setting the service in services.msc) today. DVBViewer Recording Service won't start even under a standard account or administrator account (Windows 10)… Quote Link to comment
thpf Posted August 27, 2015 Share Posted August 27, 2015 (edited) DVBViewer Recording Service starts under a administrator account on my Windows 10 so this is not a general issue But I installed my Win10 from scratch. I don't believe in updates. Edited August 27, 2015 by thpf Quote Link to comment
Tony Posted August 28, 2015 Author Share Posted August 28, 2015 DVBViewer Recording Service starts under the Local System account which ignores any password... Quote Link to comment
thpf Posted August 29, 2015 Share Posted August 29, 2015 DVBViewer Recording Service starts per default under the Local System account which ignores any password. But under Windows 10 this leads to the issue that Rec Serv can no longer access the netwok shares on the host system it is running on. Windows 10 does no longer allows the access to a network share without a password. Therefore I changed under services.msc the account from local system to a local administrator account that is allowed to access the network shares. Quote Link to comment
Tony Posted August 29, 2015 Author Share Posted August 29, 2015 Something I have overlooked or do wrong... The change of the Local System account to the Local Admin in services.msc problem passed ... Thank you very much thpf. Quote Link to comment
rabbit0x536 Posted June 17, 2017 Share Posted June 17, 2017 On 22/08/2015 at 9:12 PM, Griga said: There is a solution now posted by a German user. The Recording Service is able to access network drives if it is running in the context of a local user account with username and password. It can be achieved by opening the service properties (after launching services.msc from the start menu under Windows 7, dunno if it is still the same under Windows 10) and changing the account accordingly, which requires entering username and password. There are no known drawbacks up to now. The Recording Service is still runing as a background service and doesn't require the user to be logged on. It's just a different security context. Hi, This solution was working for me so far. Till i decided to get the paid version of the Media Service. Now it doesn't want to start if i change the Log On user with my personal account (as I did before) I have no way to make it save recordings to my NAS. I even tried to open a share that is accesible for guests, no luck. Quote Link to comment
Tjod Posted June 17, 2017 Share Posted June 17, 2017 Start the DMS configuration as admin. Go to Tasks and disable "Extended privileges ..." Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.