It was a full house in our training lab for the first week of LDAP class. The responsibility for supporting the Native LDAP client is transitioning back to the NETADM team in less than 2 weeks; training all the sites will take 4 weeks total. In the past 5 - 6 months, we have taken over support for NetConnect, security products and now LDAP client. This is the hardest that I have worked since I got into the computer support biz. I have a feeling that sentiment is shared by at least a few others in the group!

Once again, Sr. Tech Instructor Ken is back on the road to deliver product training. This past week, we were the "guinea pig" class. That means finding the typos in the workbooks and making sure the labs work. Unlike most of the other server/clients products in our portfolio, it can be difficult to draw the line between the "server" issues and the "client" issues. This is due to the interaction between the client, the directory server and the database being accessed or modified. We learned that in cases of questions/issues with ACIs (access control instructions), it can be a totally grey area.

The most important item that we all came away with from the labs: error 49 (seen either on the client's /var/adm/messages or the server's access logs) means check the proxy agent password.

Comments:

Post a Comment:
Comments are closed for this entry.

This blog copyright 2009 by swas