shortcuts and junction points being ignored
- Posts: 28
- Joined: 24 Oct 2018
I launched FFS 11.27 as admin, yet it wanted to copy a shortcut as a shortcut and for a junction point, it claimed falsely that the path could not be found.
- Posts: 1038
- Joined: 8 May 2006
I'll take it that they point to mapped drive letters?
(I'm going to say this wrong, but) drive letters are mapped at a "user" level.
So if you, as user "maurice" map X: to \\NAS\Backup, when you then "run as administrator", you, maurice, are not longer you, but rather "admin", & for user "admin", there is no mapping between X: and \\NAS\Backup.
You could not run FFS "as admin".
Test & see if that works.
You could, "as admin", map X: to \\NAS\Backup.
Or you could use UNC paths rather them mapping, so, \\NAS\Backup.
(Now, if that is allowed in a shortcut/junction, I'm not sure offhand?)
(I'm going to say this wrong, but) drive letters are mapped at a "user" level.
So if you, as user "maurice" map X: to \\NAS\Backup, when you then "run as administrator", you, maurice, are not longer you, but rather "admin", & for user "admin", there is no mapping between X: and \\NAS\Backup.
You could not run FFS "as admin".
Test & see if that works.
You could, "as admin", map X: to \\NAS\Backup.
Or you could use UNC paths rather them mapping, so, \\NAS\Backup.
(Now, if that is allowed in a shortcut/junction, I'm not sure offhand?)
- Posts: 28
- Joined: 24 Oct 2018
The destination is a mapped drive, but the source is a regular mounted drive. Why would the destination impact what FFS sees in the source?
Second, it was working yesterday.
Second, it was working yesterday.
- Posts: 1038
- Joined: 8 May 2006
Were you running "as admin" yesterday?
- Posts: 28
- Joined: 24 Oct 2018
I launched FFS as admin yes.
