Shortcut problem
Dears,
I have some shortcuts on the Desktop of a Laptop attached to a domain (windows 2012 R2).
The application they access needs to have a drive name , so there is a command that maps a drive X: to the server folder
net use x: \\data-srv\Application
On the shortcut the user has on his laptop I am entering X:\Accounting\AccPack.exe
And it is to start in X:\Accounting.
My problem is that sometimes, instead of the X: , the shortcut gets changed to \\data-srv\application\acc
and it is to start in \\Data-Srv\Application\Acc
And this causes problems , I need to remove the \\ and put the right one (X:\)
Client Laptop is Windows 10.
Thanks.
I have some shortcuts on the Desktop of a Laptop attached to a domain (windows 2012 R2).
The application they access needs to have a drive name , so there is a command that maps a drive X: to the server folder
net use x: \\data-srv\Application
On the shortcut the user has on his laptop I am entering X:\Accounting\AccPack.exe
And it is to start in X:\Accounting.
My problem is that sometimes, instead of the X: , the shortcut gets changed to \\data-srv\application\acc
and it is to start in \\Data-Srv\Application\Acc
And this causes problems , I need to remove the \\ and put the right one (X:\)
Client Laptop is Windows 10.
Thanks.
Last Comment
I believe your problem is the tracking function of WIndows shortcuts.
If you have acces to the old NT4 resource kit, there was a shortcut.exe which was able to set a shortcut to "non-tracking"
I've found this question explaining shortcut.exe or, if you don't have access to shortcut.exe uses powershell to patch the -lnk file
https://superuser.com/ques
HTH
If you have acces to the old NT4 resource kit, there was a shortcut.exe which was able to set a shortcut to "non-tracking"
I've found this question explaining shortcut.exe or, if you don't have access to shortcut.exe uses powershell to patch the -lnk file
https://superuser.com/ques
HTH
Right, Michael, but that applied long ago. I never saw this tracking happen on any new OS'. Did you?
I have a tool here against tracking shortcuts, called scut.exe (stone old, 1999), I could provide it.
I have a tool here against tracking shortcuts, called scut.exe (stone old, 1999), I could provide it.
ASKER
Dear McKnife my question was obvious (or thought so)...
Sometimes the shortcut settings change to \\sharename instead of x:\ and thus making it not possible possible to run !
Sometimes the shortcut settings change to \\sharename instead of x:\ and thus making it not possible possible to run !
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks,
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
You can deploy shortcuts to applications on network drives. These shortcuts will point to say, x:\app.exe. Whenever x: is not there, they won't work - that's clear to anyone. As soon as x: becomes available, they will work. They will not change on their won, so I wonder what you are seeing. How can it be reproduced on win10, please name the steps.