Cool Solutions

Client for OES and Windows 10 RS2

Madhan

By:

April 6, 2017 12:54 pm

Reads:1,128

Comments:0

Score:5

Print/PDF

In testing the pre-release version(s) of the Windows 10 “Creators Update” (also referred to as “Redstone 2” or “RS2”), we found an issue where in the Client for OES, login settings are lost after applying this update (because of the manner in which the upgrade process uninstalls and re-installs the Client for OES).  The last logged in user name, eDirectory profile, etc., are lost and have to be filled in again.

Micro Focus noticed this in the version of the pre-release build where the issue was introduced and we have been working with Microsoft and have a case open to resolve the issue.  Since then, Microsoft has made the RS2 update available and this issue is not resolved yet.

Bottom line – if you use Client for OES on Windows 10 – you will face this issue when you update to RS2.  You can either defer the RS2 update until we have a resolution or choose to go ahead, but fill in the login profile information again.

For the latest on this you can follow this knowledgebase article.

2 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 5 (2 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Loading...

Tags: , , , , ,
Categories: Client, File & Networking Services, Open Enterprise Server, Open Workgroup Suite, Technical

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS