This error message keeps appearing within Event Viewer on our organization's Exchange 2010 SP1 email server: Log Name: Application Source: MSExchangeMailboxAssistants Date: 24/02/2011 4:17:23 PM Event ID: 14031 Task Category: FreeBusy Assistant Level: Error Keywords: Classic User: N/A Computer: exchange.domain.local Description: Unable to find freebusy public folder: EX:/O=ORGANIZATION/OU=FIRST ADMINISTRATIVE GROUP on the server: exchange.domain.local for the user: Barret Newman:123d19a1-ea55-433a-a470-81db4980a214:ee171e75-9b79-459e-89cf-da37bc7322ae:exchange.domain.local with legacy DN: /o=Organization/ou=First Administrative Group/cn=Recipients/cn=brgnewman Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchangeMailboxAssistants" /> <EventID Qualifiers="49156">14031</EventID> <Level>2</Level> <Task>15</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-02-24T23:17:23.000000000Z" /> <EventRecordID>152741</EventRecordID> <Channel>Application</Channel> <Computer>exchange.domain.local</Computer> <Security /> </System> <EventData> <Data>EX:/O=ORGANIZATION/OU=FIRST ADMINISTRATIVE GROUP</Data> <Data>exchange.domain.local</Data> <Data>Barret Newman:123d19a1-ea55-433a-a470-81db4980a214:ee171e75-9b79-459e-89cf-da37bc7322ae:exchange.domain.local</Data> <Data>/o=Organization/ou=First Administrative Group/cn=Recipients/cn=brgnewman</Data> </EventData> </Event> Now, from a user experience perspective, I haven't heard any complaints or had any issues logged that coincide with these error messages on our Exchange server. The error messages appear for numerous users in our organization and is not limited to just one. Suggestions? There appears to be quite a few of these messages logged each day for numerous users in our organization - so it's not limited to a certain time range, or a certain user.

On Fri, 25 Feb 2011 08:13:53 +0000, brgnewman wrote: [ snip ] >Now, from a user experience perspective, I haven't heard any complaints or had any issues logged that coincide with these error messages on our Exchange server. The error messages appear for numerous users in our organization and is not limited to just one. > >Suggestions? There appears to be quite a few of these messages logged each day for numerous users in our organization - so it's not limited to a certain time range, or a certain user. If the F/B site folder doesn't exist you could rebuilt the site folders. http://technet.microsoft.com/en-us/library/bb331972(EXCHG.80).aspx --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

When I go into the Public Folder Management Console on our Exchange 2010 SP1 server, I can see the following system folders: EFORMS REGISTRY (which contains nothing) OFFLINE ADDRESS BOOK SCHEDULE+ FREE BUSY Inside the "SCHEDULE+ FREE BUSY" folder, it contains two folders: "EX:/o=Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)" (which contains only 16 items, and takes up only 7KB) "EX:/O=Organization/OU=EXTERNAL (FYDIBOHF25SPDLT)" (which contains nothing) If you take a look at the error messages in my original post, it says "First Administrative Group" in the error messages, not "Exchange Administrative Group". Now, I'm starting to get a bit concerned that we have an underlying issue with our Public Folders on Exchange. Yesterday, in addition to this topic, I posted one regarding our clients being unable to download the OAB (http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/eeec5a46-197c-4691-b205-5b603614b670). Once I disabled the Public Folder distribution method, clients were able to download the OAB in under 30 seconds with no sync issues. All our calendars, contacts, notes, etc that are stored in the Public Folders seem to be working - but, I think something is wrong with our System Public Folders.

On Sat, 26 Feb 2011 04:25:21 +0000, brgnewman wrote: > > >When I go into the Public Folder Management Console on our Exchange 2010 SP1 server, I can see the following system folders: EFORMS REGISTRY (which contains nothing) OFFLINE ADDRESS BOOK SCHEDULE+ FREE BUSY Inside the "SCHEDULE+ FREE BUSY" folder, it contains two folders: "EX:/o=Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)" (which contains only 16 items, and takes up only 7KB) "EX:/O=Organization/OU=EXTERNAL (FYDIBOHF25SPDLT)" (which contains nothing) If you take a look at the error messages in my original post, it says "First Administrative Group" in the error messages, not "Exchange Administrative Group". Now, I'm starting to get a bit concerned that we have an underlying issue with our Public Folders on Exchange. Yesterday, in addition to this topic, I posted one regarding our clients being unable to download the OAB (http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/eeec5a46-197c-4691-b205-5b603614b670). Once I disabled the Public >Folder distribution method, clients were able to download the OAB in under 30 seconds with no sync issues. All our calendars, contacts, notes, etc that are stored in the Public Folders seem to be working - but, I think something is wrong with our System Public Folders. So you HAD Exchange 2003 (or 2000, or 5.5) and you removed the servers from the organization and then you removed the Administrative group from the organization? That not a "good thing". The AG should have remained in place as long as you have objects in the AD that have a legacyExchangeDN that refers to the AG. If you still have an Exchange 2003 ESM installed somewhere you can recreate the missing "First Administrative Group" and use ADISEDIT to assign the Exchange 2007 server's public folders as the site folder server for that AG. Then recreate the site folders for the AG. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Rich, Yes, you are corrected - we originally did have an Exchange 2003 server in our organization. Last year (July/August 2010) we worked on implementing Exchange 2010 into our organization to phase out our dying Exchange 2003. Once we had Exchange 2010 actually running, the transition was pretty smooth - wellllll, with the exception of Public Folders. We had all mailboxes on the Exchange 2010 server, but none of the Public Folders would copy, sync or migrate over. It finally reached the point where I resurrected an Exchange 2003 mailbox, copied the Exchange 2003 Public Folders directory to a PST, and imported it to Exchange 2010 (oops). Frankly, I'm not surprised that the "First Administrative Group" is missing - we did encounter numerous Public Folder issues as I stated above, and I'm pretty sure that object was deleted entirely last year (September 2010) when we encountered another Public Folders issue. So where does this leave me? Where do I go from here (Please don't say go find a time machine...)? What do I have to do to fix my mistake? We do not have any servers in our organization running Exchange 2003 - we are a purely Exchange 2010 organization. Thanks!

On Sat, 26 Feb 2011 22:57:09 +0000, brgnewman wrote: >Yes, you are corrected - we originally did have an Exchange 2003 server in our organization. Last year (July/August 2010) we worked on implementing Exchange 2010 into our organization to phase out our dying Exchange 2003. Once we had Exchange 2010 actually running, the transition was pretty smooth - wellllll, with the exception of Public Folders. We had all mailboxes on the Exchange 2010 server, but none of the Public Folders would copy, sync or migrate over. It finally reached the point where I resurrected an Exchange 2003 mailbox, copied the Exchange 2003 Public Folders directory to a PST, and imported it to Exchange 2010 (oops). Frankly, I'm not surprised that the "First Administrative Group" is missing - we did encounter numerous Public Folder issues as I stated above, and I'm pretty sure that object was deleted entirely last year (September 2010) when we encountered another Public Folders issue. > >So where does this leave me? Where do I go from here (Please don't say go find a time machine...)? What do I have to do to fix my mistake? We do not have any servers in our organization running Exchange 2003 - we are a purely Exchange 2010 organization. You don't need any Echange 2003 servers, just a machine that has the Exchange management tools installed. Use the ESM to add another AG named "First Administrative Group" to your organization. After that, see this: http://technet.microsoft.com/en-us/library/aa996485(EXCHG.80).aspx No time machine needed. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Rich, I've been through EMC and I'm unable to find a spot to create a new Administrative Group - can you provide me with further instructions for this? Thanks, - Barret

On Mon, 28 Feb 2011 00:09:54 +0000, brgnewman wrote: >I've been through EMC and I'm unable to find a spot to create a new Administrative Group - can you provide me with further instructions for this? Not 2010 EMC, the 2003 ESM. Install the Exchange 2003 Management Tools on a workstation and create the Admin Group. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Additional Info: “There’s a fairly easy way to fix the problem. If you still have Exchange System Manager, you can use it to recreate the legacy admin group. Alternately, you can use ADSI Edit to do the same. The important thing is to make sure the legacyExchangeDN is correct - make sure it matches the legacyExchangeDN on the users that were created in that old admin group. On the new admin group object, make sure you have a siteFolderServer that points to an existing public store in some other admin group. Within 24 hours, the free/busy folder for that admin group will get recreated” ---------Refer to <Public Folder Replication Fails Due To Empty Legacy Administrative Group>Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

i am thinking if i am using exchange 2010 outlook 2010/2007 do i need still pf for publishing free/busy information ? as is service dedicated to this ?