Exchange 2007 Public Folder


Can anyone explain me the public folders on Exchange 2007 ?
I know that they are only there for historic reasons and in case Office 2003 is still used.
I'm looking at them now as I'm migrating to new server so I read that I need to set-up replicas.
And here is another one in my never ending chain of confusions.

I have 2 public folder containers - Default and System.

When looking into Default, I can see lots of user created folders, and folder has replication set to itself. So when I'm looking at public folders at Exchange1, they are all set te be replicated to Exchange1.
Why is that ? Should I add onther replication destination to be my Exchange2 ?

Now, lets look at System public folder. Thats a really confusing one.
Looking through the subfolder properties, I cant understand what is going on in here.
For example:

EFORMS REGISTRY - not showing any items - even 0 items - just says Not available on this server. No replication set.
Events root - again,  says Not available on this server, but replication is set ??
OFFLINE ADDRESS BOOK - no items, no replication on top level but it's subfolders contain some items and replication is set for all of them.

Now I have few OWAScratchPad folders - in here - every possible combination - some items / no replication - Not available on this server / replication set. One random of these folders is email enabled.

and so on...

Can someone please help my to understand this mess? Is there any place explaining all these folders and their default settings ? Is there a way of maybe recreating that structure if its messed up ?

If anything is wrong in here, how will it affect users ? Is it only for pre-Outlook 2007 ?

Who is Participating?
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
"I know that they are only there for historic reasons and in case Office 2003 is still used."

That isn't correct.
Public Folders can still be used by the clients and exist in all versions of Exchange.

The legacy bit are the system folders, which are held in the Public Folder container which is for Outlook 2003.
All public folders need to have at least one replica listed, which is basically where the email is stored. If you have two Exchange servers then it makes sense to have both servers listed as a replica as it will allow to maintain multiple copies. If the two servers are geographically separated it also means the users can access the content locally.

The system folder behaviour you are seeing is what I would expect and shouldn't be causing you any problems. The OWA scratchpad has to come from Exchange 2003 and could probably be removed.

If system folders get messed up then it can be reset.

However from what you have written, it wouldn't appear there is anything wrong. Running the Exchange best practises tool from the Toolbox will soon indicate if there is anything wrong through.

tp-it-teamAuthor Commented:
Is it safe to delete some system public folders ?

I have now:

eforms registry
events root
offline address book
owascratchpad (several folders)
schedule+free busy
schema-root (several folders)
storeevents  (several folders)

I understand that I need to keep offline address book and schedule+ free busy for 2003 outlook but what about others ? Can I delete them without any consequence ?
(Exchange 2003 -> 2007 migration was good few years ago).

If yes - should I just delete them using Public Folder Management Console ?
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
It is never safe to delete system folders unless you are doing the removal of the public folders completely. Therefore the only one you can remove from that list is the OWA Scratch Pad stuff, everything else has to stay.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.