Password Management plug-in disappears after iManager 2.5 upgrade

iManager 2.5 has been installed in the tree and the collection object and all RBS modules have been updated to iManager 2.5
Password Management plug-in disappears after iManager 2.5 upgrade
iManager 2.0.2 Role Based Service Collection has been updated to iManager 2.5
iManager 2.0.2 and iManager 2.5 servers using the same collection object
Password Management Role shows up fine if logging in to iManager 2.0.2 in Unrestricted Mode

To verify you have this problem, you can do one of two things:

1.  Force Unrestricted Mode on the iManager 2.0.2 server (see TID TID #10090014 - Switch between Unrestricted and Collection Owner/Assigned Access)

OR

2.  Temporarily delete your RBS Collection object (WARNING:  You will lose all role member associations if you do this)

You will only see this problem if you are using a Role Based Services Collection object in your tree.  The iManager documentation states that if you have an iManager 2.0.2 and an iManager 2.5 server reading from the same collection object in the tree, you should update all of the "Out-of-Date" modules in the collection to the latest iManager 2.5 version through the RBS Configuration.  The Passwords Role will NOT show up in iManager 2.5 (assuming that the plug-in is already installed in iManager 2.5) until you update the collection.

Screenshot from iManager 2.5 - Modules that needs to be updated

Once the collection has been updated, iManager 2.5 will show the Passwords Role correctly, but if you log back into iManager 2.0.2, the Password Management Role will be missing and you'll see a message similar to the one below if you select the Details link on the page.



To fix this problem you need to go to https://dl.netiq.com and type the following into the Keyword field:  Password Management 2.0.2 for Novell eDirectory for iManager 2.x.  Install this updated plug-in on your iManager 2.0.2 server.  Once the plug-in has been installed, the Passwords Role (formerly Password Management) will show up in iManager 2.0.2.

NOTE:  This problem will also happen if you create a separate iManager 2.5 collection as long as you are a member of both collections and you are a member of the Passwords Management Role in the 2.0.2 collection and the Passwords Role in the 2.5 collection.