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.
Knowledge Partner Knowledge Partner
Knowledge Partner
764 views

OES2018 in tree with older DS versions?

What is the oldest version of DS/eDir that we can have in a tree to
safely upgrade to the new eDir in OES2018?

Several of my clients still have the odd NetWare box left in their tree
for one reason or another. Can the new eDir 9.x peacefully coexist
with those NetWare boxes in the tree that have to have a replice just
for NLS to work (i.e. No replicas on NetWare is not an option)?

For the most part we are talking NetWare 6.5.8, I think fully patched
or very close to. The clients with older than that are no where ready
for the new OES, but knowing the breaking points will help me in
prodding them along to either getting them off those old boxes or
splitting them off the primary tree.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
Labels (2)
0 Likes
6 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

I have clients with eDirectory 9.0 along with NetWare boxes. Unless you
enable the new Enhanced Background Authentication (EBA) which is NOT yet
an option with OES (even 2018), you should be fine. eDirectory
engineering is very good about interoperability among versions.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

At least with 8856 (build 20506.07) you should be fine. I'd guess that even older stuff such as 8737 on NW51 would work. I'll check a VERY mixed tree next monday.
If you like it: like it.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

In article <KwQxC.905$VM7.745@novprvlin0913.provo.novell.com>, Ab wrote:
> I have clients with eDirectory 9.0 along with NetWare boxes. Unless you
> enable the new Enhanced Background Authentication (EBA) which is NOT yet
> an option with OES (even 2018), you should be fine. eDirectory
> engineering is very good about interoperability among versions.


Ahh, feeling much better knowing this.
For when we get to having EBA as an option, what is the oldest we eDir we
can have in that case? Just so that I can use that as a prod with clients
with the older stuff.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

In article <mathiasbraun.8fbodz@no-mx.forums.microfocus.com>,
Mathiasbraun wrote:
> I'd guess that
> even older stuff such as 8737 on NW51 would work. I'll check a VERY
> mixed tree next monday.


Looking forward to hearing that. Oldest in my active client base is
NW6.04 Previously it had been NW3.2 as the oldest and then strait up
to 6.04
Such baby steps sometimes, others its prepare for the giant steps all
at once.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

If you enable EBA then you will need to be all on eDirectory 9.x, which is
relatively new and never ran on NetWare, or even older versions of Linux
(SLES 11 and SLES 12 only I think are supported, but check the docs for
verification. There is no big reason to enable EBA, though, until you are
already on eDirectory 9.x throughout, at which point you get a lot of
other benefits in terms of performance, security, etc.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Played around a little, one thing which won't work:
If you try to install a fresh NW51 box from a SP8 overlay CD into a tree running 40005.13 on OES2018 and 20506.07 on NW65 the process will fail due to schema handling issues with DS8.51w which ships in the overlay. Not too surprising, 15 years difference of age might be a problem with human beings, too. So essentially i had to bring the fresh NW51 box to 8737 (10552.79) in a temporary tree first, afterwards i could install it into the mixed tree without issues. No problems of any kind with sync, adding replicas a.s.o.
For a "classic" tree (file, print, ...) you should definitely be fine with such an offset.
If you like it: like it.
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.