tbaki wrote:
[color=blue]
Kevin,
Your feedback has been shared with Support/Product/Engineering
Management.
Someone will update you as soon as possible.
Thanks
Tarik[/color]
Hi Tarik,
As you can see Ramesh did follow up with a post to this thread and the
same comment was added to the bug:
[color=blue]
From OES2018 onwards trustee migration across different eDirectory
trees is NOT supported.
Obviously, telling customers they can no longer migrate eDirectory
trustees to a new tree is completely unacceptable.
I’m paying for support, on a supported product, and I’m having issues
trying to use a utility that is part of that supported product to do
something that the utility was designed to do. Never before have I seen
engineering suddenly claim a capability is no longer supported just
because they can’t fix it!
The whole point of paying for support is to get issues like this
resolved. I am extremely disappointed with the lack of support I have
received on this SR. The engineer assigned to this SR has been helpful
and has opened a bug to get a software defect resolved. That appears to
be where the problem lies.
In situations like this, I expect the Technical Support group to be my
advocate and work with other internal groups to bring about a timely
resolution to issues like this one and not simply relay responses back
to me.
My SR and the associated bug are a symptom of a much larger problem.
Certainly, I want my issue resolved but there are many other bugs
opened against miggui and other utilities. Resolving my issue alone may
still not be sufficient to allow me to complete the task at hand.
Customers need a simple and reliable way to deal with eDirectory
trustee migrations! This cannot be considered an enhancement request:
It is a fundamental and necessary capability that has existed in
software releases going back to the early NetWare days and is essential
if customers wish to continue using OES.
Should Micro Focus really intend not to support migration of eDirectory
trustees to a new tree, customers need some advanced notice and a
change in policy such as this cannot be made simply by someone in
engineering adding a one line comment to a bug!
Is this really Micro Focus’s new policy for dealing with eDirectory
trustee migration?
Why is there no advanced warning for such a major policy change?
Has anyone in Micro Focus even considered how such a policy change
might impact customers?
@Tarik: I trust you can follow up and help me make some sense out of
all of this. Since Ramesh has responded in this forum already, I feel
it is appropriate that any follow up information also be posted here so
that customers who have seen his response get the whole story.
Thank you.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.