# Miggui SR & Bug outstanding for a year...

**URL:** <https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037>\
**Category:** Talk to a SUSE Technical Services Manager\
**Created:** [October 12, 2018, 2:40am UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037 "2018-10-12T02:40:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![KEVIN1](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@KEVIN1](https://forums.suse.com/u/KEVIN1)\
**Post date:** [October 12, 2018, 2:40am UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/1 "2018-10-12T02:40:12Z")

</div>



---

<div class="post-metadata">

**Author:** ![KEVIN1](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@KEVIN1](https://forums.suse.com/u/KEVIN1)\
**Post date:** [October 12, 2018, 2:40am UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/2 "2018-10-12T02:40:12Z")

</div>

A year ago, 2017-10-18, I opened SR 101115523191:  
Unable to migrate files with MIGGUI

I was, of course, trying to migrate NSS files and trustees from NetWare  
to a new OES 2015 SP1 server in a new tree.

As a result of my SR, this bug was opened:  
Bug 1064687 - the mls command only returns files that have the archive  
bit set. and the mls command fails when issued from miggui.  
[https://bugzilla.novell.com/show\_bug.cgi?id=1064687&GoAheadAndLogIn=1](https://bugzilla.novell.com/show_bug.cgi?id=1064687&GoAheadAndLogIn=1)

Both the SR and the bug remain opened and there has been no change in a  
year.

Miggui certainly has had more than its share of issues. I browsed  
through dozens of TIDS and an equal number of bugs. I thought these  
issues might be addressed in a newer OES release but…  
[color=blue]

> Trustee migration across different tree is not working.[/color]  
> [https://www.novell.com/documentation/beta/open-enterprise-server-2018/oes\_readme/data/t42tv7tq9j8h.html](https://www.novell.com/documentation/beta/open-enterprise-server-2018/oes_readme/data/t42tv7tq9j8h.html)

I was more than a bit surprised to see this statement in the OES 2018  
SP1 readme, especially when miggui is the primary migration utility.

Is miggui so badly broken that it can’t be fixed?

Can I assume that miggui is still a supported utility?

Can anyone shed some light on what is being done to resolve these  
issues?

–  
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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [October 12, 2018, 3:54pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/3 "2018-10-12T15:54:02Z")

</div>

Kevin,

Your feedback has been shared with Support/Product/Engineering  
Management.  
Someone will update you as soon as possible.

Thanks  
Tarik

## – tbaki

tbaki’s Profile: [https://forums.novell.com/member.php?userid=13755](https://forums.novell.com/member.php?userid=13755)  
View this thread: [https://forums.novell.com/showthread.php?t=509666](https://forums.novell.com/showthread.php?t=509666)

---

<div class="post-metadata">

**Author:** ![KEVIN1](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@KEVIN1](https://forums.suse.com/u/KEVIN1)\
**Post date:** [October 12, 2018, 5:59pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/4 "2018-10-12T17:59:14Z")

</div>

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]

Thank you, Tarik!

–  
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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [October 16, 2018, 3:04pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/5 "2018-10-16T15:04:01Z")

</div>

From OES2018 onwards trustee migration across different eDirectory trees  
is NOT supported.

- Ramesh

## – mvramesh

mvramesh’s Profile: [https://forums.novell.com/member.php?userid=30321](https://forums.novell.com/member.php?userid=30321)  
View this thread: [https://forums.novell.com/showthread.php?t=509666](https://forums.novell.com/showthread.php?t=509666)

---

<div class="post-metadata">

**Author:** ![KEVIN1](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@KEVIN1](https://forums.suse.com/u/KEVIN1)\
**Post date:** [October 29, 2018, 7:40pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/6 "2018-10-29T19:40:29Z")

</div>

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.
> 
> - Ramesh[/color]

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.

---

<div class="post-metadata">

**Author:** ![kjhurni](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@kjhurni](https://forums.suse.com/u/kjhurni)\
**Post date:** [October 29, 2018, 9:26pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/7 "2018-10-29T21:26:01Z")

</div>

mvramesh;2488956 Wrote:[color=blue]

> From OES2018 onwards trustee migration across different eDirectory trees  
> is NOT supported.
> 
> - Ramesh[/color]

Hi Ramesh,

Might I suggest discussing this with the documentation team?

The OES2018 “what’s new” section clearly states that nothing has  
changed:

[https://www.novell.com/documentation/open-enterprise-server-2018/oes\_readme/data/t46l9bhs2yka.html](https://www.novell.com/documentation/open-enterprise-server-2018/oes_readme/data/t46l9bhs2yka.html)  
[color=blue]

> Section 1.3.17:
> 
> Besides bug fixes, there are no other changes to the following  
> components for OES 2018:
> 
> Apple Filing Protocol (AFP)
> 
> Distributed File Services (DFS)
> 
> Dynamic Storage Technology (DST)
> 
> Linux User Management (LUM)
> 
> - Migration Tool\*
> 
> Novell Cluster Services
> 
> Novell FTP
> 
> Novell Identity Translator (NIT)
> 
> Linux Volume Manager (NLVM)
> 
> OES User Rights management (NURM)
> 
> Storage Management Services (SMS)[/color]

## – The opinions expressed are my own. Check out my OES2 Guides: Installing OES2 SP2: [http://www.novell.com/communities/node/11600/oes2-sp2-installation-guide](http://www.novell.com/communities/node/11600/oes2-sp2-installation-guide) Upgrading to OES2 with ID Transfer: [http://www.novell.com/communities/node/11601/oes2-sp2-migration-guide-transfer-id-scenarios](http://www.novell.com/communities/node/11601/oes2-sp2-migration-guide-transfer-id-scenarios) GroupWise Migration with OES2 ID Transfer: [http://www.novell.com/communities/node/11602/groupwise-migration-netware-oes2-sp2-transfer-id](http://www.novell.com/communities/node/11602/groupwise-migration-netware-oes2-sp2-transfer-id)

kjhurni’s Profile: [https://forums.novell.com/member.php?userid=734](https://forums.novell.com/member.php?userid=734)  
View this thread: [https://forums.novell.com/showthread.php?t=509666](https://forums.novell.com/showthread.php?t=509666)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [October 30, 2018, 12:04pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/8 "2018-10-30T12:04:02Z")

</div>

Hi Kevin,

We are still following up on the issue.  
Of course we will not suddenly stop supporting you.  
However, any further official update needs to come from Product  
Management, and not Support.

As you have been dealing with Scott Barnum, please ask that he involves  
his Manager Chris to follow up with you.

Thanks  
Tarik

## – tbaki

tbaki’s Profile: [https://forums.novell.com/member.php?userid=13755](https://forums.novell.com/member.php?userid=13755)  
View this thread: [https://forums.novell.com/showthread.php?t=509666](https://forums.novell.com/showthread.php?t=509666)

---

<div class="post-metadata">

**Author:** ![KEVIN1](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@KEVIN1](https://forums.suse.com/u/KEVIN1)\
**Post date:** [November 4, 2018, 10:16pm UTC](https://forums.suse.com/t/miggui-sr-bug-outstanding-for-a-year/33037/9 "2018-11-04T22:16:01Z")

</div>

tbaki;2489782 Wrote:[color=blue]

> As you have been dealing with Scott Barnum, please ask that he involves  
> his Manager Chris to follow up with you.[/color]

I have done this but as yet there is no new information.

I will update this thread as I learn more.

## – 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. Thanks.

KBOYLE’s Profile: [https://forums.novell.com/member.php?userid=19359](https://forums.novell.com/member.php?userid=19359)  
View this thread: [https://forums.novell.com/showthread.php?t=509666](https://forums.novell.com/showthread.php?t=509666)
