Verify Services are working with Common Proxy Functionality in OES2 SP3

During installation of any/all of the following OES services, you will need to verify that Common Proxy and its related functionality is working correctly and there are no failures due to existing configurations of users,policies on the tree.

Services: Linux User Management(LUM), AFP, Novell CIFS, iFolder, NetStorage, Novell Cluster Services(NCS)

Listed below are 3 possible error conditions and how to overcome them.

1. Avoid Installation Failures: During the installation of OES2 SP3, if you choose to use Common Proxy ensure either of the following

   a. Select the box that allows a new password policy to be associated with the common proxy in the Common Proxy installation YAST screen.

   b. If you have a password policy that enforces a special character, disable it or change it to ensure that a password policy with ASCII characters is allowed for the common proxy user object.

2. Failure in Post Installation Scenario: If you post install any of the above services on a OES2 SP3 server and would like the service to use a pre-created Common Proxy, ensure one of the following.

   a. Set an ASCII character password for the common proxy using the command line tools.

   b. Configure the service to use the Common Proxy after the installation. ie during the installation allow the service to use different proxy during the installation time.

3. Novell Clustering Services fails to start: In case clustering fails to start, modify the cluster configuration to use the LDAP Admin user e.g. cn=admin,o=novell. See https://www.novell.com/documentation/oes2/clus_admin_lx/?page=/documentation/oes2/clus_admin_lx/data/h4hgu4hs.html#h4hgu4hs ) and start clustering service using rcnovell-ncs start