- To use it, just follow the directions printed on the right.
- You need to know where the old shortcut was pointing on the network in order to make a new working one on the new server. If the server is no longer operational it can be a hassle to right-click-properties on the old shortcut because windows will lag and lag and lag trying to contact the old server before it finally shows you the path. To get around this issue you can drag the shorcut onto the white box and a notepad window will open showing you the path of the shortcut.
- The whole thing about the "F:" drive could be irrelevant or different for someone else. We started pointing our shortcuts to a dynamically mapped network drive instead of a UNC path in order to avoid this problem all together.
- Where it says "Class" is part of the cleanup process. We name our application folder "Classroom Applications." In a lab it might be "Lab Applications." What the program does is searches through every single profile's desktop and deletes any shortcut that starts with what you specify here.
- You can do a single PC by entering the name or a range of computers like PC1 through PC30 by putting in a prefix and then a range. You can also target a single IP address or range of IP address (as long as the first three octets are the same).
User contributed software
1 post • Page 1 of 1
The purpose of this utility was to make it easy to fix network application folders on remote and/or local machines. We use a single network folder which contains all of the application a user should need. Since machines have different software we have multiple folders for different machine builds. We place a shortcut to the network folder on the "all users\desktop" profile. Sometimes if a server gets replaced or a technician originally put the shortcut in the "default user\desktop" by accident it can become a real pain to clean up the mess with multiple shortcuts all over the place.