MC+A

Last year we assisted our customer Legal Services of Northern California with our JumpStart service. It has been nearly a year and I am happy to see how much they’ve come along. They’ve recently launched a website showcasing their project.

Their Findability Project is the public face of a special technology search project undertaken by Legal Services of Northern California (LSNC), a legal services program assisting low-income clients in 23 counties in the upper third of California. Made possible by a grant from the LSC Technology Initiative Grant Program, the goal of the project is to implement a Google Enterprise Search Appliance as the principal building block of a modest but secure, well structured, fully web accessible knowledge-content system. If you have some time please read up on their initiative. If you are interested in how we can help you please contact us.

Many of our customers find it difficult to figure out which LDAP query to run in their Google Search Appliance (GSA) or Google Mini (Mini) LDAP setup wizard.  When configuring LDAP on the GSA, a common issue that the user may run into is finding the correct information for the “Distinguished Name” (DN) field.

Our solution to this problem is a handy command that can be executed on your server providing Active Directory.

In order to quickly find the DN, open a command prompt and enter the command “adsiedit.msc”.

After you execute this command navigate to the account in which you are seeking the distinguished name (This is typically your account).

Right-click on that account and select “properties”.

Then find the “Distinguished Name” category, double-click, and you will have the answer you seek.

Google Enterprise has released the long awaited 5.0.4 release.  Most notably in this release is support Microsoft Office 2007 documents and the connector manager auth prompt bug fix.

Existing customers can goto:

https://support.google.com/enterprise/doc/gsa/00/update_index_page.html

to download the new system and software versions.  I’ll updated this thread with any discoveries that we find in our upgrades.  Please write your findings as well.

Update:

We’ve attempted to update two GSAs.  The first last week went fine.  The one we attempted today twice had a checksum error….

Downloading URL http://support.google.com/enterprise/updates/XXXXXXX

Percent completed: 100%
MD5 Checksum = 74f78e89c09d4be143c3b1d5ca1a4fb7

** Unpacking downloaded file **

ERROR: Downloaded file is not properly signed or corrupted. Please try again one more time.