This is for a new install of Windows Standard Server 2008 of Exchange 2007 standard with Windows update saying everything is current. It is a single Server hence Exchange is on the A/D domain controller. The production environment has Terminal Services loaded with Symantec's Backup Exec for Windows and the Exchange agent.The lab environments have neither Backup or Terminal Services loaded. There is 1 user and 1 room. I imported 702 contacts via Powershell. All contacts are in their own container.Using the OWA interface it shows only 600 in the default global address list and 531 in contacts lists.I have tried this on in three different environments with about the same approximate results, the numbers differer but it all are incomplete.results. (two test labs and a production server) All Contacts show in A/D and EMC. This has gone on for about a week.It appears that when I am in OWA, creating a letter and click on TO: and if I go to the end of the list and then work backwards I get a different listing than starting at the beginning and working to the end.Example Going Forward from 1 to 301 50 user/contacts at a time displays "Jack..." Going backward from the end to 301 50 at a time now displays "Mei...."Is there a way I can export the OWA address book as a csv file to determine which if any contacts are not being displayed by comparing it to the import CSV file.?Is there a limit I have exceeded?

Hi, How did you import the Contact? Import contact to public folder? Or import contact to GAL? OWA will do an LDAP query to get GAL. Please try to use the script from the article below to export SMTP proxy address. http://blog.drewery.net/2006/10/27/vbscript-to-export-smtp-proxy-addresses/ HOW TO: Find an email address in Active Directory http://exchangepedia.com/blog/2006/03/how-to-find-email-address-in-active.html Besides, how many entry in GAL,including all the users and contact? Larger than 1000? Regards, Xiu

To answer your first two questions: The contacts were imported via Powershell into their own container as Contact Objects. I allowed A/D and Exchange to build them into their lists.They show in active directory, in the Exchange Management Console. They are available to user who connect to Exchange using outlook.I have extracted the contacts again with powershell and compared them against the input file with no error.It is only in Exchange 2007' Outlook Web Agent that the problem exists.It appears to be a display problem with the OWA as contact #301 has two different names (one starting with a J, the other with the letter M) depending on if I start clicking from the beginning of the list or the end. I also noticed that when paging through the names there was a large skip between 401 and 451. From McDonald to Sutton. This reflects approx 158 names when only 50 was expected. These names became visible when I reversed direction with using the bottom arrows.There are anywhere between 704 and 725 email addresses (Users, Contacts, and Rooms) in the lists.What I was originally looking for was a way to extract the names being viewed by the user when they use OWA from off site.I am not more convinced than ever there is a problem with the way the list is being displayed. (I have changed options in OWA to display 100 at a time but it still lists only a portion of the contacts/users/rooms. This problem could be something I have configured incorrectly or a patch I am not aware of. Since this is happening on multiple machines and multiple domains/exchange servers I don't think it is a workstation problem (XP-Win7). IE8 for everyone. Exchange is set to send out 1000 names at a time.

Hi,Please try to apply the Sp2 rollup 2 for Exchange 2007. Since some issue about address book in OWA has been corrected in those updates.Besides, please try to use ADSIedit.msc to check the properties which would have vule like"Jxx" and "Mxx".Please check the contact between 401 and 451 and then try to find somting alike between them. Please try to find if those contact has large alais or disaplayname,etc.How manay Domain Controllers in your network? Can we get correct value when we use LDAP query to find the contact list. I recommend you to install Exchange Server seperatly from Domain controllers and then test the issue again.Regards,Xiu

So did updating exchange to sp2 fix the problem? Or did you find another solution?