Thursday, October 05, 2006

Methodically Troubleshooting

Today I spent a great deal of time trying to track down a problem with what appeared to be a problem with Novell Identity Management. User passwords were not syncing between Active Directory and eDirectory, which I needed so that machines running only the Microsoft agent could use ZENworks Desktop Management. It was a real pain as is many times, there were multiple causes for the failure.

I was reminded how critical is to methodically troubleshoot issues. You want to verify each part is working before you go to the next connector or piece of the puzzle.

In this case, passwords that were being set on the AD site were not unnque enough for eDirectory, but we never saw an error for this. I easily could have manually set the same password in eDirectory and tested it and would have seen the problem instantly.

A self-signed certificate had become invalid on the second day of troubleshooting. It seems that one of the engineers revoked the certificate without reimporting the new certificate. This was as a trick to find as I wasn't looking for this type of error as the system had been connecting just fine.