If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Group Policy Management and Mapped Drives
I have the problem of Windows 10 losing mapped drives and the solution
appears to be making a change/addition to Group Policy as shown he https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2 The "best solution" is "Change the drive to "Update" in group policy and the issue will disappear!" I do not have the "Local GP Editor" location "User Configuration Preferences Windows Settings Drive Maps" and there are no entries in the GP Management GUI. The instructions I find to add Drive Maps to the GP require that I use GP Management and to us it login to a domain which I cannot figure out how to do. I hope someone can show me how to do this on my home PC that, as far as I know, is not on a Domain. The drive is an NAS currently configured as N: and I have already issued a NET USER /P:YES command. |
Ads |
#2
|
|||
|
|||
Group Policy Management and Mapped Drives
Zaidy036 wrote:
I have the problem of Windows 10 losing mapped drives and the solution appears to be making a change/addition to Group Policy as shown he https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2 The "best solution" is "Change the drive to "Update" in group policy and the issue will disappear!" I do not have the "Local GP Editor" location "User Configuration Preferences Windows Settings Drive Maps" and there are no entries in the GP Management GUI. The instructions I find to add Drive Maps to the GP require that I use GP Management and to us it login to a domain which I cannot figure out how to do. I hope someone can show me how to do this on my home PC that, as far as I know, is not on a Domain. The drive is an NAS currently configured as N: and I have already issued a NET USER /P:YES command. That's probably this sort of baloney. https://docs.microsoft.com/en-us/pre...4%28v=ws.11%29 I don't think that's for non-Enterprise users. It's intentionally nasty. The page explaining it is a mile long. Paul |
#3
|
|||
|
|||
Group Policy Management and Mapped Drives
On 6/26/2020 10:35 PM, Paul wrote:
Zaidy036 wrote: I have the problem of Windows 10 losing mapped drives and the solution appears to be making a change/addition to Group Policy as shown he https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2 The "best solution" is "Change the drive to "Update" in group policy and the issue will disappear!" I do not have the "Local GP Editor" location "User Configuration Preferences Windows Settings Drive Maps" and there are no entries in the GP Management GUI. The instructions I find to add Drive Maps to the GP require that I use GP Management and to us it login to a domain which I cannot figure out how to do. I hope someone can show me how to do this on my home PC that, as far as I know, is not on a Domain. The drive is an NAS currently configured as N: and I have already issued a NET USER /P:YES command. That's probably this sort of baloney. https://docs.microsoft.com/en-us/pre...4%28v=ws.11%29 I don't think that's for non-Enterprise users. It's intentionally nasty. The page explaining it is a mile long. Â*Â* Paul Thanks I will have to read that tomorrow since it is too late and would probably put me to sleep. |
#4
|
|||
|
|||
Group Policy Management and Mapped Drives
On 6/26/2020 10:35 PM, Paul wrote:
Zaidy036 wrote: I have the problem of Windows 10 losing mapped drives and the solution appears to be making a change/addition to Group Policy as shown he https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2 The "best solution" is "Change the drive to "Update" in group policy and the issue will disappear!" I do not have the "Local GP Editor" location "User Configuration Preferences Windows Settings Drive Maps" and there are no entries in the GP Management GUI. The instructions I find to add Drive Maps to the GP require that I use GP Management and to us it login to a domain which I cannot figure out how to do. I hope someone can show me how to do this on my home PC that, as far as I know, is not on a Domain. The drive is an NAS currently configured as N: and I have already issued a NET USER /P:YES command. That's probably this sort of baloney. https://docs.microsoft.com/en-us/pre...4%28v=ws.11%29 I don't think that's for non-Enterprise users. It's intentionally nasty. The page explaining it is a mile long. Â*Â* Paul It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Question: If I join a domain, implement the Policy and then leave the domain will the policy still work? |
#5
|
|||
|
|||
Group Policy Management and Mapped Drives
Zaidy036 wrote:
On 6/26/2020 10:35 PM, Paul wrote: Zaidy036 wrote: I have the problem of Windows 10 losing mapped drives and the solution appears to be making a change/addition to Group Policy as shown he https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2 The "best solution" is "Change the drive to "Update" in group policy and the issue will disappear!" I do not have the "Local GP Editor" location "User Configuration Preferences Windows Settings Drive Maps" and there are no entries in the GP Management GUI. The instructions I find to add Drive Maps to the GP require that I use GP Management and to us it login to a domain which I cannot figure out how to do. I hope someone can show me how to do this on my home PC that, as far as I know, is not on a Domain. The drive is an NAS currently configured as N: and I have already issued a NET USER /P:YES command. That's probably this sort of baloney. https://docs.microsoft.com/en-us/pre...4%28v=ws.11%29 I don't think that's for non-Enterprise users. It's intentionally nasty. The page explaining it is a mile long. Paul It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Question: If I join a domain, implement the Policy and then leave the domain will the policy still work? You would need an IT guy to answer this :-) A domain is a way to centralize security identifiers. On home copies of Windows, every install uses different SID values. You log into just that copy of Windows, while you're working. When domain joined, the domain server keeps account information, and you're logging to the domain server. This makes a "smoother" operating environment (especially in business settings, where the user may move from one desk to another, and their work files follow them seamlessly as roaming materials). As I understand it, there are techniques for domain-joining a machine or separating it from a domain. If you were, say, giving away a computer to an employee, you separate it from the domain, so that the employee can use it as a standalone machine with standalone accounts and so on. While I'm not an IT guy, my suspicion is "leaving the domain leaves a lot on the table", and you're likely to regret the separation when it comes to things that got fixed. What I find strange about your problem, is what Microsoft were thinking when they did this (made mapped drives do the wrong thing at startup, on non Enterprise setups). Microsoft has applied pressure to SOHO small businesses to encourage upgrading to a more expensive Enterprise SKU for the OS. But why screw up a basic function like this one ? It doesn't make a lot of sense. It's like if the computer did arithmetic, you set it up so you weren't ever allowed to subtract 3 from a number. Just an arbitrary decision that makes no sense. There's already a limit on how many connections you can make to SMB, so the Home and Pro SKUs are already nicely hobbled in terms of "stealing server business". Nobody needing a server is going to be using $100 copies of the OS to do it, as the capabilities suck. I wouldn't expect Microsoft to fix this. Paul |
#6
|
|||
|
|||
Group Policy Management and Mapped Drives
Zaidy036 wrote:
[...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. |
#7
|
|||
|
|||
Group Policy Management and Mapped Drives
Frank Slootweg wrote:
Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". -- Zaidy036 |
#8
|
|||
|
|||
Group Policy Management and Mapped Drives
Zaidy036 wrote:
Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. BTW, I do not see any network related settings in the (8.1) 'Screen Saver's. So I wonder whether this problem isn't one caused by the particular screensaver you're using (whichever one that is). BTW2, why do you use a screensaver? Screensavers were for CRT displays which had no power control. These days, you just configure the display to go off (not 'blank') after X minutes of non-use. OTOH, if you want it to display pretty pictures when not in use, .... |
#9
|
|||
|
|||
Group Policy Management and Mapped Drives
On 6/29/2020 10:06 AM, Frank Slootweg wrote:
Zaidy036 wrote: Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. Not remote, no Workgroup, only LAN and one desktop PC. I am trying various credential settings to see if that will help. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. I cannot find a "screen lock"separate from a screensaver on Win 10 Pro BTW, I do not see any network related settings in the (8.1) 'Screen Saver's. So I wonder whether this problem isn't one caused by the particular screensaver you're using (whichever one that is). BTW2, why do you use a screensaver? Screensavers were for CRT displays which had no power control. These days, you just configure the display to go off (not 'blank') after X minutes of non-use. OTOH, if you want it to display pretty pictures when not in use, .... I do dim my two monitors during the unattended batch but if they are turned off then the "on screen" log file the batch generates is not visible after turning the displays back on. I realize I could display the txt log file but that would be a big effort to display errors in colors to get my attention in the morning. I am running tests without a screensaver running but not having good results so far. Another problem is that after a reboot the NAS networked as "N:" will no longer connect and I must remove and then reattach it. |
#10
|
|||
|
|||
Group Policy Management and Mapped Drives
On Mon, 29 Jun 2020 17:12:22 -0400, Zaidy036 wrote:
On 6/29/2020 10:06 AM, Frank Slootweg wrote: Zaidy036 wrote: Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. Not remote, no Workgroup, only LAN and one desktop PC. I am trying various credential settings to see if that will help. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. I cannot find a "screen lock"separate from a screensaver on Win 10 Pro I use Windows key + L |
#11
|
|||
|
|||
Group Policy Management and Mapped Drives
On 6/29/2020 8:11 PM, Char Jackson wrote:
On Mon, 29 Jun 2020 17:12:22 -0400, Zaidy036 wrote: On 6/29/2020 10:06 AM, Frank Slootweg wrote: Zaidy036 wrote: Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. Not remote, no Workgroup, only LAN and one desktop PC. I am trying various credential settings to see if that will help. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. I cannot find a "screen lock"separate from a screensaver on Win 10 Pro I use Windows key + L still thehttps://support.microsoft.com/en-us/help/12445/windows-keyboard-shortcuts |
#12
|
|||
|
|||
Group Policy Management and Mapped Drives
On 6/26/2020 10:35 PM, Paul wrote:
Zaidy036 wrote: I have the problem of Windows 10 losing mapped drives and the solution appears to be making a change/addition to Group Policy as shown he https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2 The "best solution" is "Change the drive to "Update" in group policy and the issue will disappear!" I do not have the "Local GP Editor" location "User Configuration Preferences Windows Settings Drive Maps" and there are no entries in the GP Management GUI. The instructions I find to add Drive Maps to the GP require that I use GP Management and to us it login to a domain which I cannot figure out how to do. I hope someone can show me how to do this on my home PC that, as far as I know, is not on a Domain. The drive is an NAS currently configured as N: and I have already issued a NET USER /P:YES command. That's probably this sort of baloney. https://docs.microsoft.com/en-us/pre...4%28v=ws.11%29 I don't think that's for non-Enterprise users. It's intentionally nasty. The page explaining it is a mile long. Â*Â* Paul The more, one looks the more one finds. Another interesting possibility is "System Unattended Sleep Timeout" which is a hidden setting that can override "Never Sleep" in "Power Management". See https://winaero.com/blog/add-system-unattended-sleep-timeout-to-power-options-in-windows-10/ And https://winaero.com/blog/how-to-open-advanced-settings-of-a-power-plan-directly-in-windows-10/ |
#13
|
|||
|
|||
Group Policy Management and Mapped Drives
On 30.06.20 2:11, Char Jackson wrote:
On Mon, 29 Jun 2020 17:12:22 -0400, Zaidy036 wrote: On 6/29/2020 10:06 AM, Frank Slootweg wrote: Zaidy036 wrote: Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. Not remote, no Workgroup, only LAN and one desktop PC. I am trying various credential settings to see if that will help. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. I cannot find a "screen lock"separate from a screensaver on Win 10 Pro I use Windows key + L That even works at XP PRO |
#14
|
|||
|
|||
Group Policy Management and Mapped Drives
Zaidy036 wrote:
On 6/29/2020 10:06 AM, Frank Slootweg wrote: Zaidy036 wrote: Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. Not remote, no Workgroup, only LAN and one desktop PC. I am trying various credential settings to see if that will help. With 'remote' (user and password), I mean remote from the computer to the NAS. As to no Workgroup, 'even' with one computer, you have a Workgroup, namely the computer and the NAS. At least in my NAS, I configure the Workgroup which the NAS belongs to. We 'happen' to have two computers (laptops), but even if I would have only one, I still would have/need a Workgroup. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. I cannot find a "screen lock"separate from a screensaver on Win 10 Pro Yes, you've got me there. I don't know where that is set and now I even doubt if I have a screen lock after a certain time, or only after Sleep (or Hibernate). So forget this bit. The main point is that I do not use a screensaver. BTW, I do not see any network related settings in the (8.1) 'Screen Saver's. So I wonder whether this problem isn't one caused by the particular screensaver you're using (whichever one that is). BTW2, why do you use a screensaver? Screensavers were for CRT displays which had no power control. These days, you just configure the display to go off (not 'blank') after X minutes of non-use. OTOH, if you want it to display pretty pictures when not in use, .... I do dim my two monitors during the unattended batch but if they are turned off then the "on screen" log file the batch generates is not visible after turning the displays back on. I realize I could display the txt log file but that would be a big effort to display errors in colors to get my attention in the morning. I am running tests without a screensaver running but not having good results so far. I see that in another response you mention that you have found a hidden Power Management setting ('System Unattended Sleep Timeout'), so hopefully that's the way to go. Another problem is that after a reboot the NAS networked as "N:" will no longer connect and I must remove and then reattach it. That shouldn't happen. May I suggest you look in the UI of your NAS to see if there is a Workgroup setting? (Or do you address the NAS by specifying its IP address (which is a bad way to do things)?) |
#15
|
|||
|
|||
Group Policy Management and Mapped Drives
On 6/30/2020 10:36 AM, Frank Slootweg wrote:
Zaidy036 wrote: On 6/29/2020 10:06 AM, Frank Slootweg wrote: Zaidy036 wrote: Frank Slootweg wrote: Zaidy036 wrote: [...] It looks like it would work IF I was on a Domain but I am not so until I join one not available and cannot get my NAS to automatically reconnect on boot.. Long shot: My NAS (intentionally) goes to sleep when not used. So it disappears from 'Networks' in (Windows) File Explorer and I assume the mapped drive (N gets disconnected (haven't checked the latter). What I do to 'revive' it, is to address a folder on the NAS. Normally I do that with a path in the 'Run...' box, but I just checked that a 'dir' command ('dir \\DISKSTATION\Frank') works as well, so that's something which could be put in a startup/scheduled task. I will try but manually Net Use and other cmds always ask for password or "cannot identify requested". Does your Diskstation normally require a password to connect? The NAS itself, i.e. the Network *Share(s)*, is set up in my (Windows) Workgroup and the UI of the NAS defines which user can access what. When first connecting to a Network Share, you of course have to specify the remote user and password. Not remote, no Workgroup, only LAN and one desktop PC. I am trying various credential settings to see if that will help. With 'remote' (user and password), I mean remote from the computer to the NAS. As to no Workgroup, 'even' with one computer, you have a Workgroup, namely the computer and the NAS. At least in my NAS, I configure the Workgroup which the NAS belongs to. We 'happen' to have two computers (laptops), but even if I would have only one, I still would have/need a Workgroup. I have also mapped a Network *Drive* (N to \\DISKSTATION\Frank. When I configured ('Map network drive') that Network Drive, I ticked the 'Connect using different credentials' box and specified the remote user After that initial setup, neither the Network Share(s), nor the Network Drive ask for a password. I agree with Paul: If MS wants everyone on Win 10 they should include capabilities for non-enterprise users. Without Policy change I cannot run unattended batch since default policy for Screensaver is to disconnect network drives and NOT automatically reconnect on "unlock". I'm on Windows 8.1 (not 10) and use screen *lock* (not screen saver) and my network drives do not disconnect on screen lock/unlock. They probably disconnect on *sleep* (we have laptops), but reconnect when accessed. I cannot find a "screen lock"separate from a screensaver on Win 10 Pro Yes, you've got me there. I don't know where that is set and now I even doubt if I have a screen lock after a certain time, or only after Sleep (or Hibernate). So forget this bit. The main point is that I do not use a screensaver. BTW, I do not see any network related settings in the (8.1) 'Screen Saver's. So I wonder whether this problem isn't one caused by the particular screensaver you're using (whichever one that is). BTW2, why do you use a screensaver? Screensavers were for CRT displays which had no power control. These days, you just configure the display to go off (not 'blank') after X minutes of non-use. OTOH, if you want it to display pretty pictures when not in use, .... I do dim my two monitors during the unattended batch but if they are turned off then the "on screen" log file the batch generates is not visible after turning the displays back on. I realize I could display the txt log file but that would be a big effort to display errors in colors to get my attention in the morning. I am running tests without a screensaver running but not having good results so far. I see that in another response you mention that you have found a hidden Power Management setting ('System Unattended Sleep Timeout'), so hopefully that's the way to go. Another problem is that after a reboot the NAS networked as "N:" will no longer connect and I must remove and then reattach it. That shouldn't happen. May I suggest you look in the UI of your NAS to see if there is a Workgroup setting? (Or do you address the NAS by specifying its IP address (which is a bad way to do things)?) I have already tried various users/password combinations and the IPA, fixed on my system, with no success. The workgroup approach sounds interesting because I have never specified one but I see that the PC properties show workgroup = WORKGROUP. I just looked at the NAS and it reports a different workgroup probably from the previous Win 7 Home connection so I will either change the Win 10 or NAS to match and see what happens. Thanks for the suggestion. I think Win+L is equivalent to "RUNDLL32 USER32.dll,LockWorkStation" so I will test that CMD which presents a login window without a screensaver and is equivalent security. That would work if the batch operations are still able to function then. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|