Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Client 4.83SP1 default field settings

Status
Not open for further replies.

thcmtgr

Technical User
Jun 27, 2000
2
US
Auto-installing the 4.83 SP1 client. The default user name, context, and server fields are not retained. Is there some way to retain the fields or to re-populate them before the user has to log in again? The "Save Profile after Successful Login" box is checked in the existing client. We have many different contexts and servers as we have multiple offices. We'd like to push the client out to
all users and for the default entries for the different users to be retained. Only the tree is constant and can be set in the unattent.txt file. We presently use NCIMAN to create an unattend.txt file. We are upgrading from 4.81 to 4.83SP1

 
Haven't seen this before, but I have used ACU many times. I have never set any tree, context, or server info in my unattend.txt file. I never hear back from the users who got updated from ACU, so I would assume they were fine and the NDS info from before was retained.

So just try doing nothing, it's nice when doing nothing solves problems. :)

Brent Schmidt CNE,Network + [atom]
Senior Network Engineer
Keep IT Simple [rofl]
 
Doing nothing leaves the fields blank. The pull-down button still displays the previously-used contexts and servers but we are trying very hard to simplify the process for our computer-unsavvy users. Even this task will create some consternation and confusion amongst our users.
 
Have you tried using the Cool Tool for contextless login? It copies two dll's to the system32 folder and sets a couple of registry settings.

When the user gets the login box they type in there user name then tab to the password field and the context is automatically filled by this little program.

It uses LDAP, so one of your Novell servers (for each tree)will have to have NLDAP loaded. It works great, and no one will ever have to even know their context.

Look on the Novell Cool solutions for this:
LDAP Contextless Login

JON
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top