Help, we have a user who doesn’t have access to alter his own ECL… tried recertifying ID and trashing deskop.ndk but still no luck. User doesn’t have correct permissions so preventing him opening files on computer. Does anybody know how to give user full access to update his own ECL apart from complete reinstall of client??Thanks alot for any suggestions.
Rina
Subject: User not Manager of own ECL - help!!
I am not an admin, but it sounds like you will need to re-install the client. I am only basing this upon what is stated in the admin client help on ECL administration:
Note: The administration ECL has a setting that prevents users from changing their workstation ECLs.
When you set up the first server in a domain, Domino creates a default administration ECL, which you can then customize. The administration ECL is the template for all workstation ECLs. Whenever a new Notes client is installed, the setup program copies the administration ECL from the Domino Directory to the Personal Address Book on the Notes client workstation. The user’s Notes ID is added to the workstation ECL, with all access allowed. For example, when John Doe’s Notes client is being set up, John Doe is automatically added to the client ECL signer list.
If the home server is unavailable when a Notes client is installed – for example, when a user is disconnected --the workstation ECL is created with default settings, rather than being created from the administration ECL.
Note Technically, when a server is initially installed, there is no Admin ECL. When a client attempts to edit the workstation ECL, or refresh it from an admin ECL that does not exist, the client creates an ECL with default settings that are coded into the client. The Admin ECL exists on disk, once an administrator modifies and saves it. Once the modified administration ECL is saved to disk, then that is the ECL that is copied to user workstations.
You use the administration ECL to define and deploy customized ECLs for your users. You can control ECL changes or allow users to modify their own ECLs. Furthermore, you can update your users’ workstation ECLs as security requirements change – automatically, through the use of a security settings document deployed through a policy, or manually, by asking users to refresh their workstation ECLs.
To create customized ECLs that can be deployed for specific groups of users, you must use a security settings document that is deployed through a server policy. For example, you can create one ECL exclusively for contract employees and another ECL for full-time employees.
Subject: User not Manager of own ECL - help!!
Hi you have to delete local names.nsf, cache.dsk and desktop6.ndk.You also have to delete all entries form notes.ini exept this lines:
[Notes]
KitType=1
Directory=C:\notesr6\data
InstallType=2
FaultRecovery_Build=Release 6.5.2
Timezone=-1
DSTLAW=3,-1,1,10,-1,1
UPDATE_TIMER=25.10.2002 06:31:09
SUDIALOG_ON=1
DST=1
MailType=0
This causes the client to run into the “after-install” setup again, and creates all the client db’s and also the ECL which is stored in the local names.nsf.
HTH
Klaus
Subject: Simple solution to ECL problem
It is not necessary to delete Desktop6.NDK, Cache.NDK or to strip down the Notes.ini.
Instead create a new Personal Address Book (namesTEMP.nsf) and copy all of your contacts, connections, locations, etc to it.
Shut down Notes. Use the OS to rename Names.nsf to NamesBACKUP.nsf and to rename NamesTEMP.nsf to Names.nsf
Restart Notes.
You will have a new ‘default’ ECL and will have preserved the user’s personailizations.
Marc
[FOR SEARCH INDEX: Problem was loss of ownership of Execution Control List ( ECL ) - unable to update ECL]
Subject: Simple solution to ECL problem
It is not necessary to delete Desktop6.NDK, Cache.NDK or to strip down the Notes.ini.
Instead create a new Personal Address Book (namesTEMP.nsf) and copy all of your contacts, connections, locations, etc to it.
Shut down Notes. Use the OS to rename Names.nsf to NamesBACKUP.nsf and to rename NamesTEMP.nsf to Names.nsf
Restart Notes.
You will have a new ‘default’ ECL and will have preserved the user’s personailizations.
Marc
[FOR SEARCH INDEX: Problem was loss of ownership of Execution Control List ( ECL ) - unable to update ECL]
Subject: Try this first
Rina, You should be able to use the key to solve this, add it to your administrative ECL with the desired rights:-jmw