How are you starting HS?
Announcement
Collapse
No announcement yet.
Mapped Network Drive
Collapse
X
-
I've found that Windows will "soft" disconnect mapped drives so I run a batch file before I have HS (or one of its plugins) try to use a mapped drive. The batch file is just something like this and is called from an event:
Code:net use t: \\server\share t:
HS 4.2.8.0: 2134 Devices 1252 Events
Z-Wave 3.0.10.0: 133 Nodes on one Z-Net
Comment
-
Originally posted by sparkman View PostI've found that Windows will "soft" disconnect mapped drives so I run a batch file before I have HS (or one of its plugins) try to use a mapped drive. The batch file is just something like this and is called from an event:
Code:net use t: \\server\share t:
Thanks
Jim
Comment
-
Guest
-
Originally posted by larrywal32 View PostI would like BLBackup to backup my Homeseer directory onto a server that I have on the network. That server is protected by domain credentials, so I created a mapped network drive (e.g. Z:\) on the Homeseer Hometroller that had the credentials baked in. When I navigate to the drive in Windows on the hometroller, it works fine. So the share and mapped drive are set up properly.
But BLBackup doesn't seem to work with this. It won't accept the drive as a destination.
Bug?
HS3 runs as an elevated app.
This behaviour is documented by Microsoft
https://support.microsoft.com/en-us/...when-uac-is-co
I used the registry edit method at the end of the article and now all the shares are seen by my elevated applications including HS3.
Comment
-
Originally posted by Blade View PostI am using Windows 10 Pro and HS3 and I backup all of my folders in BLBackup to a network drive using a UNC path
I even backup folders from other machines on my network using the UNC path
\\networknas\backup etc.
Tried differing the slashes or adding to the end no joy .
Comment
-
Have you tried this:- Click Start, click Run, type regedit, and then press ENTER.
- Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Policies\System
- If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
- On the Edit menu, point to New, and then click DWORD Value.
- Type LocalAccountTokenFilterPolicy, and then press ENTER.
- Right-click LocalAccountTokenFilterPolicy, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor.
Comment
Comment