I need to disable login update for NDS and NMAS logins.
By default login update will be enabled in eDirectory. In order to disable login update, use iMonitor as mentioned below for NDS logins (Step 1 to Step 2) and follow Step 3 for NMAS logins.
Step 1. Login to iMonitor using https://ip address of eDirectory server: https port/nds and provide the admin credentials and click on login.
Figure 1: Showing iMonitor login page
Step 2. Go to Agent Configurations -> Login Settings -> uncheck “Login Update Enabled” and submit.
Figure 2: Showing the Agent configuration.
Figure 3: Showing the Login Settings.
Figure 4: Showing the check box to disable the Login Update.
Step 3: Login update attribute for nmas logins can be turned off by executing the command “nmas LoginInfo 1″.
Below are the steps to disable the login update on each platform.
The command “nmas LoginInfo 1″ should be added near the end of the autoexec.ncf. Unload and load ds after adding this command in the autoexec.ncf. The command can also be executed at the NetWare console.
When NMAS is started, it processes the commands in the file nmas.cfg . The nmas.cfg file must have the command “nmas LoginInfo 1″ and should be in the same directory as the dib files which is usually c:/novell/nds/dibfiles. This command can also be executed from the Novell® eDirectoryTM Services console by selecting nmas.dlm, typing the command in the Startup Parameters field, then clicking Configure. Restart eDirectory after making adding the command in the nmas.cfg file.
Create a file nmas.config and add the command “nmas LoginInfo 1″.
When NMAS is started, it processes the commands in the file nmas.config.The nmas.config file must be in the same directory as the dib directory. For example, if the dib directory path is “/var/opt/novell/eDirectory/data/dib” then the nmas.config file path would be “/var/opt/novell/eDirectory/data/nmas.config”. Restart ndsd after adding this command in the nmas.config. File permissions on this file should be set to at least 644. NMAS uses the same uid that ndsd uses so the owner should be root, unless it is a non root install. Then of course the owner should be the same user/uid that is running ndsd.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.