If you search the Novell Support Site, you'll find a number of different Technical Information Documents (TIDs) that explain how to set up a workstation to automatically log in to a NetWare network.
The big problem is that Novell seems to change the procedures required to set up automatic logins with each release of the Novell Client. Not to mention that the TIDs designed to explain each of these procedures are quite long and difficult to digest.
Because this leads to spending a lot of time whenever you have to configure a workstation to automatically log in, I wrote a small application that can set auto login up on a workstation in a split second.
Here's how it works:Since I discovered that the Novell Client simply ignores the registry keys it doesn't need, I designed my application to write all the registry keys necessary to enable auto login for each of the different Novell Client versions.This version of Autolog writes the registry keys for all Novell Client versions from 4.6 to 4.83. This version also checks the desktop operating system to make sure it supports the automatic login functionality.How to use Autolog:Simply run the autolog.exe from the workstation in question, fill out the form with the necessary credentials, and click the "Enable AutoLogin" button.The next time you boot the workstation, you will not be prompted for a username or password but will automatically be logged in to both the workstation and the network.Warning!To automatically log in to a Novell network and a Windows workstation, the account password is stored, in clear text, in the workstation's registry. This can be a security issue. To be safe, make sure the workstations you enable for automatic login don't have access to sensitive areas of your network.
What's new with version 126.96.36.199:
Jeremy also requested that the current settings of NMAS could be
preserved during AutoLog disable.
His request is now how Autolog works.
What's new with version 188.8.131.52: (Version never made it public)
Tony also discovered that I got a key messed up, and changed its
This bug was also reported by Jeremy Mlazovsky.
This is now fixed.
What's new with version 184.108.40.206:Lars Adelvard from Danish Service Team found that I didn't disable NMAS when running mode 2.Tony Pedretti from TransUnion LLC discovered that I cleared some settings like "Clear Current Connections" etc. Autolog now no longer clears those settings.Autolog made an error, if ServerName was set with a bindery key, this will from now on just be ignored, since DHCP will kick in.
What's new with version 3.0.1:Enabled support for NMAS. (This is as default installed with Client 4.90, but it breaks Autologon.)Autolog will now disable NMAS when autolog is enabled, and reenable when autolog is disabled.
What's new with version 220.127.116.11:Added the /LockWS option to commandline.Added a new GUI button that will copy GUI to the clipboard, allowing you to paste this into a login script as commandline parameters.Changed behavior off mode=1, making it switch to MSGina instead of disabling NDS, thereby making it possible to do an NDS logon later.
What's new with version 18.104.22.168:Changed behavior of Commandline /Disable, so it now accepts parameters as well.Added Version info to title line off the GUI Window.Removed req. for the Novell Client32. Autolog is now THE AUTOLOG TOOL, even if you are running without Novell Client32. Added support for ACU !!!!This can now be used to update an existing client already running with autolog !!!!This can also be used with ZfD Image or any other Image tool to rollout the client, and set autolog parameters in one go !!!!
What's new with version 2.5:Did a lot of Code CleanupFound a bug that used to be corrected :-( causing Wkstn logon to fail the second time, if the used account had a blank password.Michael McNally found that you can use the Wkstn's own environment variables and pass them on to Autolog.Corrected a bug discovered by Greg Sopcak, who found that I didn't set NDS Pararms when doing a M$ logon only
What's new with version 22.214.171.124:Chris Gibbs discovered that I didn't follow TID 10065981, which caused autolog to fail on the windows part if the Admin held down the Shift button during relogon. Fixed that, so I now follow that TID.
What's New 11-11-02:Added the possibility to use a blank password.Added the possibility to uninstall by command line.Added the possibility to show result window when doing an unattended install.Added switch to try to guess the username and or context automatically.Dropped Switch named /WkstnOnly and /AutoWSLog, and replaced those with the mode switch.Added possibility to just set parameters without doing any logon.Fixed a bug that caused Autolog to fail if the Mode-switch wasn't touched in GUI-mode, but was left in default setting. To see the command line switches etc, please see the Usage and FAQ tab.
What's New 9-11-02:Corrected a bug with Scripting.Corrected a bug that caused password change to be disabled when autolog was disabled on a workstation.Added possibility to make a prompted logon to eDirectory, but an automatic logon to the workstation....(Haven't got ZfD...Anyone...)
Updated 9-3-02 to fix a bug that caused autolog to fail on W2K with Client 4.83SP1.
What's New June 2002:Fixed a bug causing "Run Script"-button not to workAdded support for Windows 9xAdded support for unattended setup. To see command line parameters, run autolog.exe /?
To bypass the autolog tool, hold down the "Shift" button during boot of the workstation.
Updated May 2002 to recognize operating systems that don't support the automatic logon functionality. Have you ever tried to make a workstation running Windows NT, 2000, or XP automatically log in to the network and to itself?
See this article for more information.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.