Tor Emil
New Member.
1840 views

windows 10 novell client sp4 ir2 with insider preview build

Today I got a new insider preview from microsoft

Win 10 pro insider preview
evaluation. build 14342.rs1_release.160506-1708

It brok my logon to novell. I have to logon localy and then log on to Novell
I m not able to log in to novell or windows from the novell logon picture.
But I can logon locally or domain

Now on the logon screen I can see two Novell login logos both are labeled "No label"

They where before labeled
one with "Novell" and the other I am not shore of but it could have been "another user"

Someone out there with a solution?

Regards Tor
Labels (1)
Tags (1)
0 Likes
4 Replies
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: windows 10 novell client sp4 ir2 with insider preview build

torhowden <torhowden@no-mx.forums.microfocus.com> wrote:

> Win 10 pro insider preview
> evaluation. build 14342.rs1_release.160506-1708
>
> It brok my logon to novell. I have to logon localy and then log on to
> Novell
> I m not able to log in to novell or windows from the novell logon
> picture.
> But I can logon locally or domain


There are not any known, fundamental incompatibilities yet between the
Novell Client 2 SP4 (IR2) and the current 14342 build. We have the
IR2 client logging in successfully from that platform here.

Obviously the Windows 10 beta builds being delivered by Insider
Preview are not officially supported by Novell Client at this time;
but we are certainly looking to find and understand any key issues
being introduced by the Windows 10 changes.

In the past with Windows 10 upgrades (which includes upgrading from
one Windows 10 build to another), we have seen Windows undo critical
configurations during the upgrade process. e.g. Removing the
authentication package configuration, removing the network provider
configuration, removing the Novell Client from the Network Adapter
properties -- even though Windows 10 was specifically retaining the
fact that the "Novell Client is installed."

The current Novell Client 2 SP4 (IR1) and later clients address all
the known issues in this regard, and should restore those
configurations if Windows unexpectedly removes them. But its possible
that you might be seeing a new "upgrade configuration loss" we haven't
encountered yet.

Was this a clean installation of Windows 10 build 14342?
(Unfortunately Windows 10 build 14291 and later does have some new
functionalities which only kick in if the installation was not an
upgrade.) Or was in an upgrade from the previous Insider Preview slow
ring build? Or an upgrade from Windows 10 November 2015 (1511, 10586,
TR2)? Or an upgrade from Windows 8.1 or earlier? (If so,
specifically Windows 8.1? Windows 8? Windows 7 SP1?) With this
additional information we can test whether we can duplicate any
fundamental issue in the upgrade or installation path you had used.

For the state your machine is in now, what happens if you just re-run
the Novell Client 2 SP4 (IR2) SETUP.EXE to re-install Novell Client?
In the "upgrade configuration was lost" cases, that was the workaround
to restore the required settings. Or in the worst case, "install the
Novell Client again (so key Windows entries reflect Novell Client's
presence again), then un-install the Novell Client (so all settings
are removed), then finally install Novell Client again to run
normally."

> Now on the logon screen I can see two Novell login logos both are
> labeled "No label"
>
> They where before labeled
> one with "Novell" and the other I am not shore of but it could have been
> "another user"


Yes, this is a change that started in Windows 10 build 14328, where
the text associated to what is actually an image field being shown by
the credential provider is now displayed by LogonUI. In Windows 10
November 2015 and earlier -- and all the way back to Windows Vista --
only the image is shown and the text was ignored.

We expect to address this in the next release after Novell Client 2
SP4 (IR2), so that "No label" will not be shown next to the Novell
Client credential provider icons. For now though, this is the way
Windows 10 will display the Novell Client 2 SP4 (IR2) credentials.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com
0 Likes
Tor Emil
New Member.

Re: windows 10 novell client sp4 ir2 with insider preview bu

I have tried to reinstall the client, that did not work. I am not sure of the version of windows prior to this version. but I am sure it was a "normal" windows version.

I just got the text on the screen telling me that this was a insider preview last Monday. Have not had that before.

Going to try removing the client and reinstall it, later.
0 Likes
Tor Emil
New Member.

Re: windows 10 novell client sp4 ir2 with insider preview bu

Unistalled and installed the client it did work. But today I got a new update on the insider preview, and it was broken again.
This is my fault, because I had to choose this insider choice at installing windows, due to interest in the newest software.

Have to accept that this is happening. But still I am able to login after the windows login.
0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: windows 10 novell client sp4 ir2 with insider preview build

torhowden <torhowden@no-mx.forums.microfocus.com> wrote:

> Unistalled and installed the client it did work.


Good, I'm glad at least that aspect still remains true.

> But today I got a new update on the insider preview,
> and it was broken again.


I'm not finding any fundamental issue in the upgrade from TH2 (current
shipping November 2015 release of Windows 10), the RS1 14342 build
(the previous Insider Preview Fast Ring build), and/or the RS1 14352
build (the current Insider Preview Fast Ring build).

With Novell Client 2 SP4 (IR2) installed and able to login
successfully prior to upgrade, I found that the Novell Client
credential tiles were still successfully being displayed post-upgrade,
and I was able to login and use network resources successfully.

So I'm not sure what issue you're seeing yet. I would almost say that
those symptoms sound like a pre-Novell Client 2 SP4 (IR1) is installed
rather than IR2, so maybe just double-check which version is truly
installed. We'll keep looking for whether we can duplicate any kind
of upgrade scenario failure.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.