I'm at my wits end. I have no GAL. I've removed it, recreated it, updated it, verified that it does in face recreate the folder structure with the correct ID parameter but at the end of the day, the directory is empty. I've followed every guideline I could find online which had me restarting services etc to ensure the directory was populated but nothing. Nol OAB.XML, no .lzx files jsut an empty folder. This of course winds up generating event errors 9328,9373 and 9369 all of which fall into the "well duh" category and basically creates the "the error is because the file is missing and check the log to see why the file is missing" loop. This may or may not have been related to us removing the old Exchange 2000 front end server and making the 2007 server stand-alone but I believe it was happening before that. I'm not entirely sure what to do next. Any advice would be appreciated.

Oh, and just to help, here is the output of "get-offlineaddressbook" Server : SRVR-MAIL1 AddressLists : {\Default Global Address List} Versions : {Version3, Version4} IsDefault : True PublicFolderDatabase : SRVR-MAIL1\First Storage Group\public PublicFolderDistributionEnabled : True WebDistributionEnabled : True DiffRetentionPeriod : 30 Schedule : {Sun.5:00 AM-Sun.5:15 AM, Mon.5:00 AM-Mon.5:15 AM, Tue.5:00 AM-Tue.5:15 AM, Wed.5:00 AM-Wed.5:15 AM, Thu.5:00 AM-Thu.5:15 AM, Fri.5:00AM-Fri.5:15 AM, Sat.5:00 AM-Sat.5:15 AM} VirtualDirectories : {SRVR-MAIL1\OAB (Default Web Site)} ExchangeVersion : 0.1 (8.0.535.0) AdminDisplayName : Name : GF-Address DistinguishedName : CN=GF-Address,CN=Offline Address Lists,CN=Address Lists Container,CN=GHSLOCAL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=GHSLocal,DC=com Identity : \GF-Address Guid : e86b2fd1-3c41-4031-8f5b-efeb20c10000 ObjectCategory : GHSLocal.com/Configuration/Schema/ms-Exch-OAB ObjectClass : {top, msExchOAB} WhenChanged : 6/8/2012 9:21:49 AM WhenCreated : 6/7/2012 7:26:43 PM OriginatingServer : srvr-ad1-v1.GHSLocal.com IsValid : True

Hello, Then this should be an OAB generation issue. You can raise the log level on the MBX and force the OAB generation. After that, please post the detailed error message in the Application log. Thanks, Simon

Hello, Then this should be an OAB generation issue. You can raise the log level on the MBX and force the OAB generation. After that, please post the detailed error message in the Application log. Thanks, Simon