locked
Address Book how does it work ?

    Question

  • hello

     

    I would like to know how does it work on a client computer with communicator to get this famous GalContacts.db file.

     

    Apparently the Communicator client get informations from https://<externalpoolname>/Abs/Ext , but in this folder there are only three type of files.

    *.lsabs , *.dabs , and one .txt

     

    So how does Communicator use a .lsabs or .dabs file to create a .db file ?

     

    I ask this question because I don't understand why a client computer with Windows XP and communicator beta could create this GalContacts.db file, whereas an other client computer with Windows Vista an communicator beta could not create it. (both in same configuration and environment exept the OS)

    The result is that my Vista client say that it can't synchronise address book.

     

    Thanks

    Friday, May 11, 2007 2:32 PM

Answers

  • Hello,

     

    The AddressBook service is primary pupose is to provide updated GAL information to the OC 2007 client. It will also provide phone number normalization service for OC 2007 clients. The ABServer.exe is scheduled to query AD periodically for updates to user / group /information and provide this delta of updated information to the AddressBook share as .dabs files. After the initial installation and at 1:30 AM every day after that  ABServer.exe will provide a full update to the AddressBook share  with a lsabs file.

     

    The OC 2007 client will use in band provisioning to access the URL https://<externalpoolname>/Abs/Ext/f-0901e.lsabs from the Abs\Ext virtual folder during its user sign in process the contents of this file will provide the OC client with the information that will be imported into a galcontacts.db file.

     

    The OC client will inherit the proxy server configuration that is used by IE and cache the Abs/Ext/f-0901e.lsabs at the proxy and locally on the Windows client. Also, The OC client configuration for automatic DNS lookup and manual TLS configuration can render different results in the HTTP URL that is used for accessing the ABS virtual folders. So there can be several different items that come into play that may cause issue with the creation or update of the  galcontact.db file on the OC client.

     

    The galcontacts.db file is located at %userprofile%\Local Settings\Application data\Microsoft\Communicator folder. Signing out of OC 2007 and moving this file then signing back into OC 2007 should import a new lsdabs file and a new galcontact.db should be created. If that is taken care of then we know that issue that you are having is not a permission issue with the AddressBook share or a network connectivity issue. If you cannot download the galcontact.db file:

     

    1. Make sure this symptom is the same on all of your Vista clients. Then take a network capture on the Vista client while signing into OC 2007. This will take a Vista compatible Network Sniffer like Netmon 3.0. Prior to taking the capture sign out of OC 2007, make sure that the Web Proxy client is disabled, Delete IE cache on the client, use c:\>ipconfig /flushdns on the client. Start the network sniff and Open / Sign into OC 2007. Stop the network capture.

     

    2. On the Vista client try turning off User Access Control and then use the steps above to import the galcontact.db

     

    3. If you can create a new galcontact.db without any issues using the steps above then our problem may lie elsewhere. If this is the case I would like to send youa link to our MSDT utuility that will gather logging from your Vista client and mail it back to me.

     

    Please include an email address that I can use to send the MSDT information to you.

     

     

    Thursday, May 24, 2007 10:39 PM

All replies

  • Hello,

     

    The AddressBook service is primary pupose is to provide updated GAL information to the OC 2007 client. It will also provide phone number normalization service for OC 2007 clients. The ABServer.exe is scheduled to query AD periodically for updates to user / group /information and provide this delta of updated information to the AddressBook share as .dabs files. After the initial installation and at 1:30 AM every day after that  ABServer.exe will provide a full update to the AddressBook share  with a lsabs file.

     

    The OC 2007 client will use in band provisioning to access the URL https://<externalpoolname>/Abs/Ext/f-0901e.lsabs from the Abs\Ext virtual folder during its user sign in process the contents of this file will provide the OC client with the information that will be imported into a galcontacts.db file.

     

    The OC client will inherit the proxy server configuration that is used by IE and cache the Abs/Ext/f-0901e.lsabs at the proxy and locally on the Windows client. Also, The OC client configuration for automatic DNS lookup and manual TLS configuration can render different results in the HTTP URL that is used for accessing the ABS virtual folders. So there can be several different items that come into play that may cause issue with the creation or update of the  galcontact.db file on the OC client.

     

    The galcontacts.db file is located at %userprofile%\Local Settings\Application data\Microsoft\Communicator folder. Signing out of OC 2007 and moving this file then signing back into OC 2007 should import a new lsdabs file and a new galcontact.db should be created. If that is taken care of then we know that issue that you are having is not a permission issue with the AddressBook share or a network connectivity issue. If you cannot download the galcontact.db file:

     

    1. Make sure this symptom is the same on all of your Vista clients. Then take a network capture on the Vista client while signing into OC 2007. This will take a Vista compatible Network Sniffer like Netmon 3.0. Prior to taking the capture sign out of OC 2007, make sure that the Web Proxy client is disabled, Delete IE cache on the client, use c:\>ipconfig /flushdns on the client. Start the network sniff and Open / Sign into OC 2007. Stop the network capture.

     

    2. On the Vista client try turning off User Access Control and then use the steps above to import the galcontact.db

     

    3. If you can create a new galcontact.db without any issues using the steps above then our problem may lie elsewhere. If this is the case I would like to send youa link to our MSDT utuility that will gather logging from your Vista client and mail it back to me.

     

    Please include an email address that I can use to send the MSDT information to you.

     

     

    Thursday, May 24, 2007 10:39 PM
  • Hi all,

    Mike's post helped us finding the problem we had. All Windows 2000/XP clients could download the galcontacts.db whereas my Windows Vista machine could not.

     

    The problem was, that Vista by default had the IE security setting 'Check for server certificate revocation*' enabled. This doesn't play very well with our standalone PKI (hint: expired CRL's).

     

    Hope this helps,

    Regards,

    Marco

    Thursday, December 27, 2007 8:18 AM
  • I have the same problem I have checked the IE Option the problem is still there.

    from the vista workstation i can type https://fqdnofmyocsserver  it's work fine. No warning

    I read the techent about adresse Book i dont find any information.  I just have a fresh install from OCS Std Edition

    i ran BPA for OCS 2007 all is Green ! in dont know where to search

     

    thanks

     

    laurent Teruin

    lteruin@hotmail.com

     

     

    Thursday, January 24, 2008 4:58 PM
  • I'm having the same problem, on windows Vista.

     

    I read you note with interest, but I have question: why would communicator read from " https://<externalpoolname>/Abs/Ext/f-0901e.lsabs from the Abs\Ext" when sitting on the internal network ? Wouldn't it read from https://<internalpoolname_or_server/abs/int/... instead ?

     

    This problem has been plaguing me for days. It's a brandnew installation. Standard edition. Communicator running on Vista business.

     

    Thanks.

     

    Denis.

    Tuesday, May 20, 2008 11:19 PM
  • Correct, it reads from INT.

     

    Answer: turn off certificate revocation list checking in IE: Tools, Internet Options, Advanced.

     

    Wednesday, May 21, 2008 7:53 AM
  • If this all didnt work then try these too

    1. Within IE add the Address Book URL that users will download the AB files.  IE > Internet Options > Security > Trusted Sites > Add the URL to trusted sites (ex.  https://ocsfrontend.local  )
    2. Verify that User Access Control is Off on the vista machine
    Monday, July 06, 2009 4:17 PM