Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1581 views

Windows 10 Netware client on Surface Pro 4

Hi,

I have a Surface Pro 4. Its running Windows 10 Enterprise set up from a Windows installer, not the default Surface installation.

I cannot get the Netware client for Windows 10 working on the Surface. After its installed I reboot Windows as requested and on the reboot Windows goes straight into an automatic repair. Windows can't repair.

I can have the Netware Windows 8 client running on this Surface. It works but there are issues. I have been able to get the Netware Windows 10 client working on the Surface factory Windows setup. I have also been able to get the Netware Windows 10 client working on a non Surface computer running the same Windows 10 Enterprise as what I've installed on the Surface.

Any help or ideas appreciated.

Thanks.
Labels (1)
0 Likes
5 Replies
Absent Member.
Absent Member.

kdegraa,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.novell.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Novell Forums Team
http://forums.novell.com


0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Kdegraa,
> I can have the Netware Windows 8 client running on this Surface. It
> works but there are issues. I have been able to get the Netware Windows
> 10 client working on the Surface factory Windows setup. I have also been
> able to get the Netware Windows 10 client working on a non Surface
> computer running the same Windows 10 Enterprise as what I've installed
> on the Surface.
>
> Any help or ideas appreciated


What version of client? I just installed Novell Client 2 SP4 for Windows
IR2.exe on a surface

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
https://www.novell.com/products/enhancement-request.html

0 Likes
Micro Focus Expert
Micro Focus Expert

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

> I cannot get the Netware client for Windows 10 working on the Surface.
> After its installed I reboot Windows as requested and on the reboot
> Windows goes straight into an automatic repair. Windows can't repair.
>
> I can have the Netware Windows 8 client running on this Surface. It
> works but there are issues. I have been able to get the Netware Windows
> 10 client working on the Surface factory Windows setup.


I checked around but do not have access to a Surface Pro 4, so I can't
make any direct observations or confirmations.

What that sounds like it /could/ be is the Windows 10 Enterprise
custom installation that was performed (as opposed to the factory
installation) has enabled Device Guard by default (and Secure Boot
which is used as part of Device Guard), such that Windows is
intentionally requiring that all boot-time drivers are signed by
Microsoft, and considers anything else "an intruder."

As opposed to the factory Windows 10 installation, which was either
not Enterprise and/or did not leave this feature enabled. (As
presumably would have been intentionally done for the factory install,
presumably to maximize compatibility with whatever unknown
applications the customer would install next.)

I have not investigated Device Guard extensively yet, but my
understanding is that it /would/ be possible to indicate which
additional applications and signatures should be allowed to execute on
the device, by pushing signed catalog files and additional policies to
the machine. So if someone was truly intending to have Device Guard
enabled, they would be committing to this additional management of
specifically "whitelisting" which application signatures were allowed
to execute on their devices, in exchange for being able to mitigate
zero-day threats because Windows refuses to run anything else.

It may be that's really not what was intended for the custom Windows
10 installation performed on this Surface Pro 4, and what really needs
to be achieved is to re-install Windows 10 again without allowing
Device Guard or Secure Boot to become enabled. But I don't have a
device in front of me to say whether that's something you have to
allow in firmware, during Windows installation, or both.

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

aladams;2421620 wrote:
kdegraa <kdegraa@no-mx.forums.microfocus.com> wrote:

> I cannot get the Netware client for Windows 10 working on the Surface.
> After its installed I reboot Windows as requested and on the reboot
> Windows goes straight into an automatic repair. Windows can't repair.
>
> I can have the Netware Windows 8 client running on this Surface. It
> works but there are issues. I have been able to get the Netware Windows
> 10 client working on the Surface factory Windows setup.


I checked around but do not have access to a Surface Pro 4, so I can't
make any direct observations or confirmations.

What that sounds like it /could/ be is the Windows 10 Enterprise
custom installation that was performed (as opposed to the factory
installation) has enabled Device Guard by default (and Secure Boot
which is used as part of Device Guard), such that Windows is
intentionally requiring that all boot-time drivers are signed by
Microsoft, and considers anything else "an intruder."

As opposed to the factory Windows 10 installation, which was either
not Enterprise and/or did not leave this feature enabled. (As
presumably would have been intentionally done for the factory install,
presumably to maximize compatibility with whatever unknown
applications the customer would install next.)

I have not investigated Device Guard extensively yet, but my
understanding is that it /would/ be possible to indicate which
additional applications and signatures should be allowed to execute on
the device, by pushing signed catalog files and additional policies to
the machine. So if someone was truly intending to have Device Guard
enabled, they would be committing to this additional management of
specifically "whitelisting" which application signatures were allowed
to execute on their devices, in exchange for being able to mitigate
zero-day threats because Windows refuses to run anything else.

It may be that's really not what was intended for the custom Windows
10 installation performed on this Surface Pro 4, and what really needs
to be achieved is to re-install Windows 10 again without allowing
Device Guard or Secure Boot to become enabled. But I don't have a
device in front of me to say whether that's something you have to
allow in firmware, during Windows installation, or both.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com



Thankyou for the response. It is great. Thanks to the others too.

Its a strange issue. Since I've posted this a few things have changed. I'm pretty sure we are not going to be distributing Surfaces to staff. They have a major issue in that they are not WiDi compliant. The Surface wifi adaptor is made by Marvell. I tried a Surface with the WiDi adaptor we are planning to use and it barely worked, very laggy and then Windows blue screened. I could not install the Intel WiDi application as it said there the computer did not have compliant hardware.

Since that time I've made a few more Windows 10 images on different computers and I have not had the same issue as I've reported here. So at this stage I don't think further investigation is needed on my part.
0 Likes
Micro Focus Expert
Micro Focus Expert

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

> Since that time I've made a few more Windows 10 images on different
> computers and I have not had the same issue as I've reported here.


Fair enough. It's not clear to me what the real issue was either, for
what its worth. I was able to test a few Secure Boot-related
configurations -- including an install of Windows 10 Enterprise where
Secure Boot was enabled by default -- and never hit that kind of
outcome. (Nor did manually enabling the non-default
EnableVirtualizationBasedSecurity and HypervisorEnforcedCodeIntegrity
in Windows 10 Enterprise, to achieve kernel-mode code integrity
protection.) Both Windows and the current shipping Novell Client 2
SP4 (IR2) continued loading successfully in these scenarios.

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.