See TID 7009517
http://www.novell.com/support/kb/doc.php?id=7009517

>>> On 6/14/2012 at 5:55 AM, in message

<VikCr.7712$EH6.3766@kovat.provo.novell.com>,
Mysterious<Mysterious@heaven.com> wrote:
> On 14/06/12 11:06, dwolter wrote:
>>
>> Hi!
>> Have installed the IR3 Client on a blank machine (no

> upgrade of the
>> Novell Client), but no registry keys were created?!?
>> Did you find the information you shared somewhere on the


> Novell pages?
>>
>> Thanks & regards
>> dwolter
>>
>>

>
> With the installation of Novell client sp2 ir3, registry
> settings won't be
> created automatically. you have to manually set them.
> The details are given
> below.
>
> To enable the "Computer Only Logon If Not Connected"
> feature:
>
> 1. Log on to the Windows machine with administrative
> privileges.
>
> 2. Edit the registry and navigate to the existing
> \HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Login\ key.
>
> 3. Create a subkey named "Computer Only Logon If Not
> Connected", such that a
> key path of
> \HKEY_LOCAL_MACHINE\Software\Novell\Login\Computer
> Only Logon If
> Not Connected\ now exists.
>
> 4. Under the "Computer Only Logon If Not Connected" key,
> create the
> following
> entries:
>
> A DWORD (32-bit) value named "Enable". If the value of
> this entry is set
> to 1,
> the "Computer Only Logon If Not Connected" feature is
> enabled. If this
> value
> does not exist or is set to 0 (zero), the feature is
> disabled.
>
> Optionally, create a Multi-String (not String) value
> named "Network Category
> List". This Multi-String can be set to one or more of the


> following values,
> which correspond to the names Windows uses to describe
> network categories:
> "Home", "Work" and "Public".
>
> Optionally, create a Multi-String named Network Name
> List. This Multi-String
> can contain a list of one or more names that have been
> assigned to networks
> identified by Windows. For example, "Network 1",
> "Network 2",
> "My-Residence",
> "My-Office" and so on.
>
> The "Computer Only Logon If Not Connected" feature takes
> effect when the
> "Enable" value is set to 1, even without the "Network
> Category List" or
> "Network Name List" values being defined. When the
> "Computer Only Logon
> If Not
> Connected" feature is enabled, at minimum the Novell
> Client will
> automatically
> perform a Computer Only Logon instead of a Novell Logon
> if Windows reports
> there are not any active network interfaces when the
> logon attempt is
> initiated.
>
> If the "Network Category List" is defined, the Novell
> Client will query
> Windows
> to determine what category each identified network
> belongs to. ("Work",
> "Home", or "Public".) The "Network Category List" names
> which Windows
> network
> categories the "Computer Only Logon If Not Connected"
> feature should
> assume CAN
> NOT access Novell eDirectory servers.
>
> Note this means if any one of the currently active
> networks detected by
> Windows
> is assigned to a category which does NOT appear in the
> configured "Network
> Category List", the "Computer Only Logon If Not
> Connected" functionality
> will
> not engage. For example, assume the "Network Category
> List" has been
> configured with "Home" and "Public". During the next
> logon attempt, Windows
> reports there are two "Public" networks detected and one
> "Work" network
> detected. In this case the Novell Client will perform a
> normal Novell
> Logon,
> because there one network present (the "Work" network)
> which isn't in the
> "Network Category List".
>
> If the "Network Name List" is defined, the Novell Client
> first performs the
> "Network Category List" processing described above if
> the "Network Category
> List" is defined. After matching the active network
> categories against the
> "Network Category List", if there is still one or more
> active Windows
> networks
> which hasn't been excluded based on category, the Novell
> Client will match
> those network names against the "Network Category List".
> The "Network
> Category
> List" names individual Windows network names the
> "Computer Only Logon If Not
> Connected" feature should assume CAN NOT access Novell
> eDirectory servers,
> regardless of what Windows network category the named
> networks belong to.
>
> For example, assume the "Network Category List" has been
> configured with
> "Home"
> and "Public", and the "Network Name List" has been
> configured with
> "RemoteOffice". During the next logon attempt, Windows
> reports a "Public"
> network and also a "Work" network named "RemoteOffice".
> Even though
> based on
> the "Network Category List" alone a Novell Logon would
> have been
> attempted due
> to presence of the "Work"-category network, because the
> "Work" network
> is named
> "RemoteOffice" and this network name appears in the
> "Network Name List", the
> Novell Client will actually consider that none of the
> active networks
> detected
> by Windows qualify for attempting a Novell Logon. A
> Computer Only Logon
> will
> be initiated instead.
>
>
> To use the "Computer Only Logon If Not Connected"
> feature:
>
> 1. Logout of Windows, or reboot the machine.
>
> 2. Select the "Novell Logon" link on the Windows logon
> page, if the Novell
> Client login is not already in "Novell Logon" mode. If
> "Computer Only
> Logon"
> mode is explicitly selected, the "Computer Only Logon If
> Not Connected"
> feature
> does not need to engage.
>
> Note by default, the Novell Client remembers whether
> "Novell Logon" or
> "Computer Only Logon" was last used, and will default to
> that mode
> during the
> next logon. If you want the Novell Client to always
> come up in "Novell
> Logon"
> mode and then just let the "Computer Only Logon If Not
> Connected"
> automatically
> decide whether a Novell Logon attempt is actually
> appropriate, change the
> "Computer Only Logon Default" setting from "Automatic"
> to "Never" in the
> "Advanced Login" tab of the Novell Client Properties.
>
> 3. Now attempt to logon in Novell Logon mode. Once you
> enter your
> password and
> press the submit button, the Novell Client will begin
> the "Computer Only
> Logon
> If Not Connected" processing of querying Windows for
> connected network names
> and categories, and matching those names and categories
> again any configured
> "Network Category List" and "Network Name List" values.
>
> 4. If the Novell Client determines there are one or more
> active Windows
> networks present over which a Novell Logon attempt will
> be appropriate, the
> Novell Client will simply proceed with normal Novell
> Logon processing of
> attempting to login to both eDirectory and the Windows
> account.
>
> 5. If the Novell Client determines that all of the
> active Windows networks
> match either the configured "Network Category List" or
> "Network Name
> List", or
> if Windows reports there simply are not any active
> Windows networks, even
> though the Novell Client was in Novell Logon mode when
> the logon attempt was
> initiated, the eDirectory login will be transparently
> skipped, and only the
> Windows account logon attempt will be made.
>
> 6. Note in cases where the Windows account password is
> not the same as the
> eDirectory account password - for example, because the
> Windows account
> password
> was normally supplied from a Novell ZENworks Dynamic
> Local User (DLU)
> policy,
> or the password was expected to be retrieved by
> NMAS-based Single
> Sign-On - the
> Windows-only account logon attempted by "Computer Only
> Logon If Not
> Connected"
> will not be able to succeed using the eDirectory
> password.
>
> The Novell Client will still skip the eDirectory logon
> attempt and will
> perform
> just a Computer Only Logon, but the user will have to
> manually enter their
> Windows account password. This is only an issue in
> cases which
> otherwise would
> have retrieved their Windows account passed from Novell
> eDirectory-based
> sources.
>
>
> P.S : The same information will be updated in Novell
> client
> documentation Live
> by the beginning of next week and a TID will be created
>
> Thanks