Recently we migrated from 2000 Exchange to 2007. we are now 100% exchange 2007 with the old box decommissioned, connector deleted, uninstalled and removed from the directory. however i forgot to do the public folders migration and it seems to be a causing some minor issues. We don't really use public folders as a company anymore but there are some replication issues and OAB is having issues and i figured that i would be able to alleviate these issues by deleting all the old stuff or the whole public folders edb and recreating it. What steps should i take to clean this up with minimal downtime?Keyboard Not Detected - Press F1 to continue

Hello,We only need public folder if you have legacy OLT client. ie. prior to Olt2k7 client.Do you see first administrative group in ADSIEDIT? or have you deleted?, if you have delete First administrative group then Yes you'll face the issues which you're describing, including schedule free busy also.Removing first administrative group from exchange organization is not recommended. Check the following threadremove "First Administrative Group" in Exchange System Manager?http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/11403e66-847d-49fb-8076-7457486bf2c0You can use the following KB for resetting the system folder in exchange 2007 folder if you haven't deleted first administrative group and you still have public folder hierarchy and public folder storeHow to Reset System Foldershttp://technet.microsoft.com/en-us/library/bb331972.aspxIf you have deleted first administrative group and even deleted public folder hierarchy then you have to follow the following steps.To recreate the Folder Hierarchies msExchPublicFolderTreeContainer:1. Launch adsiedit.msc.2. Expand Configuration | Configuration | Services | Microsoft Exchange | Orgname | Administrative Groups 3. Create a new container called First Administrative Group. This is assuming the name of the administrative group for Exchange 2000/2003 was First Administrative Group. 4. Right click on First Administrative Group6. Select New Object7. Select msExchPublicFolderTreeContainer for the class and click Next8. Enter the following for the value: Folder Hierarchies, click Next9. Click FinishCreate Public Folder Tree Object10. Right click CN=Folder Hierarchies -> New Object11. Selected msExchPFTree for the class12. For the Value, enter Public Foldersand click Next13. Click on the More Attributes button, select msExchPFTreeType and set the value to 1. This is very important as a value of 1 tells Exchange that this is a MAPI Tree14. Click Ok and then finishPopulate msExchOwningPFTreeBL attribute object of the PF Stores in the Exchange 2007 organization 15. Right-click the Public Folders object just created in step 12.16. Copy the distinguishedname value to the clipboard and then click cancel.17. Still within ADSIEdit, expand the Exchange 2007 Administrative Group | Servers | <servername> | Information Store | Second Storage Group18. Right-click Public Folder Database on the right-hand pane and choose Properties.19. Locate the msExchOwningPFTree attribute and paste in the value that was copied to the clipboard in step 16. Click OK.20. Now, wait a few moments and try to mount the Exchange 2007 Public Folder store. If the process was successful, the PF database will mount and Outlook clients will be able to login to Exchange once again.If the Public Folder databases fails to mount within a few minutes, restart the Information Store Service and try to mount the public folder database once again.before you follow the above steps, i would suggest you to implement the same on the lab machine before you try playing around with adsiedit on production environment.let me know how it goesArun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

i still have someone of a public folder heirarchy i guess as i have the public folder store and database mounted. i just only removed the folders we created in the "default public folders" the "system public folders" still remains too. So you're saying that if i still have "first administrative group" that i should use the KB article instead of removing it and just reset my system public folders?Keyboard Not Detected - Press F1 to continue

Yes, only if you're 100% sure that all the public folder has been replicated to the new exchange 2007 server.Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

well i am not worried about our files in there. plus the old exchange server is 100% offline. Keyboard Not Detected - Press F1 to continue

Cool, lets give a shoot!Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

I followed the guide on how to reset the system folders. however i am still receiveing the error in the event view Event Type: Error Event Source: MSExchangeFBPublish Event Category: General Event ID: 8207 Date: 5/14/2009 Time: 2:07:29 PM User: N/A Computer: MICKY Description: Error updating public folder with free/busy information on virtual machine MICKY. The error number is 0x80004005. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. i did restart the exchange services and my 2003 clients are still getting a 0X8004010F Keyboard Not Detected - Press F1 to continue

Okey, can you create new OAB, set that as a default and point that to your mailbox store?Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3