Talk:Novell Client Settings
From CoolSolutionsWiki
To a client acess a Novell network we should know: - UserName; - Password; - Tree Name; - Context; - Server.
With the DHCP Options I can send, Tree name, and Server. I could send the context but my IP networks don't correspond with the contexts. To solve the problem of the context I can use ContextLess. But for ContextLess to work I need: - Server; - Context. I mean where the client should look for the user. It could be the all tree but in my case with WAN I can't. It looks like the chicken and the egg problem, doesn't it?
The solution would be simple, create another DHCP Options for: - ContextLess LDAP Server and ContextLess Start Context, - or, just interpreted the Context and the server sent in the DHCP option, to be the ContextLess LDAP Server and ContextLess Start Context.
I've already asked for this enhancement request. We will just have to wait ;-)
Another important information, but not required, for the client is the SCOPE and the Directory agents. I also send that information through DHCP. To upgrade the clients I use ACU. When I tested the update Agent it didn't work very well. The idea is good though. I install NICI and NMAS because I use IDM2 (Identity Manager 2) My other client settings are: âClientâ¿, âFirst Network Driveâ¿: K (because some people connect to different Tree and the F: is there home directory). âLocation Profilesâ¿, âDefaultâ¿, âPropertiesâ¿. âServices â Login Service â Defaultâ¿, âPropertiesâ¿ RemoveâSave profile after successful loginâ¿ âUsernameâ¿ write the name of the user. âNDSâ¿: âTreeâ¿: <Tree_name> âContextâ¿: Context of the User. âServerâ¿: Preferred server of the User. âWindowsâ¿
âLocal Usernameâ¿ write the name of the user.
Dial-up, remove âEnable TABâ¿. NMAS, remove âEnable TABâ¿.
âAdvanced Loginâ¿
Clear Connections = ON; Force Logoff Button = ON; Remember Workstation Only Settings = OFF; Workstation only Default = OFF Workstation Only If Not Connected = ON; Copy Netware Username to Windows = ON; âAdvanced Settingsâ¿: Hibernate Reconnect Delay = ON; Use UTF8 Encoding and NCPs = OFF; âAdvanced Menu Settingsâ¿: Filter User List = ON; âDefault Captureâ¿ remove all. âProtocol Preferencesâ¿ select all except seleccionar âHost Fileâ¿. âLDAP Contextless Loginâ¿: âEnable LDAP Treeless Loginâ¿ off âEnable LDAP Contextless Loginâ¿ enabled. âEnable LDAP Context Search Scopeâ¿ enabled. Tree = <Tree_Name>, Properties: âSearch Context and Subtreeâ¿ enabled; It depends of the location for the workstation, I normally choose the location OU.
âServersâ¿ I choose the DSMaster/eDirectory Server of that location. âSingle Sign-onâ¿ Off
DHCP Settings Enabled âUse Serverâ¿; Enabled âBinary Dataâ¿; Enabled âUse Treeâ¿;
âDSCAT Contextless Loginâ¿ Off.
Update Agent disabled.
As you can see I write that information and sent it by DHCP, this is because:
- the case when installing a machine and there is a problem with DHCP; - there are always some changes in the Workstation before giving it to the user, so lets put the correct information.
http://www.ithowto.com/microsoft/w2kdhcpslp.htm and some tids explain how to send information to the client through DHCP.
I have used Group Policy Templates to push out client settings
These are excellent I strongly recommend these as a means to configure your Novell Clients for 4.90 and 4.91.
http://www.novell.com/coolsolutions/tools/14348.html
My thanks to Shaun for saving me lots of time and helping me to add value for my clients.
I don't know if this happens with anyone else, but some of the registry entries (i.e. Default WS Only, Remember WS Only, Check Workstation Only if Connected), work fine on desktop PC's but don't work on laptops with the same confguration
