Cool Solutions

Teaming 1.0 to 2.0 Upgrade – Tell Teaming Server to NOT look for eDirectory Admin Account PLUS Duplicate User IDs



By:

December 22, 2009 12:07 pm

Reads: 3151

Comments:0

Score:0

Teaming 1.0 to 2.0 Upgrade – Tell Teaming Server to NOT look for eDirectory Admin Account PLUS Duplicate User IDs – Novell has an article written but it is for a “New install” of Teaming 2.0. This article explains how to fix it if you are upgrading!

Scenario

Upgrading from Teaming 1.0 to 2.0

Followed excellent Novell Docs and things went well, however we got 500 errors once we tried to login as Admin after the install.

Well, I knew there was a fix for the LDAP error login fix. Doc # 5058027 HOWEVER the path to the Kablink file is DIFFERENT when you upgrade from 1.0. Here it is.

Installation:

  1. Stop Teaming on the server
  2. Rename the existing “kablink-teaming-main.jar” file located in the following default directories to “kablink-teaming-main.200″ (/opt/icecore/apache-tomcat-6.0.18/webapps/ssf/webinf/lib
  3. Now drop that new kablink-teaming-main.jar into the same folder
  4. Restart Teaming

We also had an issue with a few users with the same ID yet in different OU’s. Either clean that up or change the UNique ID on the “Other” Tab.

I hope this helps as it was time consuming for us.

_____________________________
Norm O’Neal
2010 Novell Knowledge Partner
Novell Users Group of Indiana (NUGI)
Integrity Network Solutions
“Serving One Community

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

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