I push out new/updated FE's (with linkded shortcuts) to all users as needed. The problem is that there are a few users who for whatever reason want to create their own shortcuts to the network FE. Is it possible to prevent users not be able to create a shortcut to the FE residing on the network? Any suggestions?
I pulled thses suggestions from another Forum:
Comment from GHemphill
Date: 08/23/2004 06:11AM PDT
A simple answer? Make the desk top Read Only to the user(s). Only allow the Adminsitration account.
Comment from bfens2
Date: 08/23/2004 06:12AM PDT
you could give them a mandatory profile.
then when they log off and then back on, any settings they have changed will be reverted back to origninal.
Comment from PeteLong
Date: 08/23/2004 06:14AM PDT
Disable "Save Desktop on Exit"
[Start] [Run] [Regedit]
Registry Key: HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer
Modify/Create the Value Data Type(s) and Value Name(s) as detailed below.
Data Type: REG_DWORD (Dword Value) // Value Name: NoSaveSettings
Setting for Value Data: [0 = Disabled / 1 = Enabled]
Exit Registry and Reboot
Comment from NIPPLES
Date: 08/23/2004 07:11PM PDT
You could create a program that deletes *.ink from the desktop that runs at startup. Or even add some lines to autoexec.bat like so...
cd C:/documents and settings/usename/desktop
those lines should delete all shortcuts whenever the computer starts up.
I prefer to do things by programming than use windows features ;o)
If you can work with VB then u use
followed by the pathname, then file name eg:
kill "C:/documents and settings/usename/desktop/*.ink"
Comment from LittleRed1
Date: 08/25/2004 03:39AM PDT
I usually remove user's write and execute permissions to the desktop. This prevents them from creating files or shortcuts on the desktop and prevents them from executing files if they happen to find a way of downloading stuff to the desktop. I use XCACLS to do this, something like:
Something I do is have the FE check its name (Currentdb.Name) on start up. If it is located on the network give a polite reminder to run using the provided shortcut and quit. Users can create their own shortcut (no need to play with policies for all users) but it won't work when they try to use it. They will get the message pretty quickly
I second pootle flumps suggestion. I would check the path the front end was being run from. If it wasn't the expected installation path (meaning they were trying to run it directly, usually from a shortcut) it would tell them to use their local copy, then bomb out (after sending me an email).