Link to home
Start Free TrialLog in
Avatar of Tony Giangreco
Tony GiangrecoFlag for United States of America

asked on

Global Address Book won't publush on Win 2008 / Exchange 2007 Server

Last year, I installed a new Dell Win 208 server std with Exchange 2007 for a 30 employee client. I migrated the employees from Win 2000 to 2003 to 2008. Since then every time I add an employee, the Global Address book in Exchange does not get updated for the employees who all use Outlook 2007 on Win 7 Pro and Win XP Pro systems. I had one guy come in and push the address book out using powershell, but he hever showed me what to do and he is gone.

Last Monday morning, I went into Exhcange and put a custom publish schedule of every Monday at 1PM, but no employees see the new employee.

Please provide details on how do I correct this issue?
ASKER CERTIFIED SOLUTION
Avatar of Exchange_Freak
Exchange_Freak
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Tony Giangreco

ASKER

They tried this and it didn't bring down the new employee:
Tools > Download Address Book > Full Address Book
Did you check the events ?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I checked the Applications log on the server and found this entry just about the time she pulled fown the address book. She cannot find the new employee listed.

Log Name:      Application
Source:        MSExchangeFDS
Date:          9/19/2011 12:33:05 PM
Event ID:      1008
Task Category: FileReplication
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      myDomain8.myDomainconsulting.local
Description:
Process MSExchangeFDS.exe (PID=5792). Offline Address Book data synchronization task has completed successfully. OAB name: "myDomain OAB", Guid: dbc3a83d-4839-4850-82af-aa11e3b8c2e2
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeFDS" />
    <EventID Qualifiers="16388">1008</EventID>
    <Level>4</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-19T17:33:05.000Z" />
    <EventRecordID>286679</EventRecordID>
    <Channel>Application</Channel>
    <Computer>myDomain8.myDomainconsulting.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSExchangeFDS.exe</Data>
    <Data>5792</Data>
    <Data>myDomain OAB</Data>
    <Data>dbc3a83d-4839-4850-82af-aa11e3b8c2e2</Data>
  </EventData>
</Event>
Try to run the command in the link below and then check the even after it completes
http://technet.microsoft.com/en-us/library/aa997982%28EXCHG.80%29.aspx
Is there a log file I can view on the exchange server that shows what powershell commands were executed last time when the publish worked?
the link contains that powershell command that will force the OAB to execute