Under 'System Public Folders', Exchange 2007 and above, the only important (primary) folders are 'EFORMS REGISTRY', 'OFFLINE ADDRESS BOOK', and 'SCHEDULE+ FREE BUSY'.
You can delete all the rest. Now, determining what sub-folders of the above primary folders are actually important can be a little challenging. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Thursday, April 13, 2017 4:11 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Potentially OT: Exchange Objects in AD So *under* our 'System Public Folders'... Thanks, Geoff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Thursday, April 13, 2017 1:00 PM To: 'exchange@lists.myitforum.com' <exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com>> Subject: [Exchange] RE: Potentially OT: Exchange Objects in AD Michael, So user our 'System Public Folders', are all these "OWAScratchPad..." and "StoreEvents..." irrelevant/unused? [cid:image001.png@01D2B4A1.70018D90] I'm okay with doing test moves and seeing if stuff breaks, I would have to eventually take some sort of action. I was just hoping to avoid the "scream test" until I felt I exhausted all other options. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, April 13, 2017 12:14 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Potentially OT: Exchange Objects in AD ATTENTION: This email came from an external source. DO NOT open attachments or click on links from unknown senders or unexpected emails. So, the supportability of your existing scenario is doubtful. I can tell you that globalevent, internal, and OWAScratchPad objects are not used by Exchange 2007 or later, so they are irrelevant. Most - but not all - searches in Exchange 2007+ happen via GUID. Those that don't happen via GUID use a specific well-known location and look at specific object classes beneath that location. All I can suggest is to move a couple of PF objects and see what happens over a couple of days. If there is a problem, those particular PFs should break fairly quickly. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Thursday, April 13, 2017 2:49 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Potentially OT: Exchange Objects in AD Don't want to be a pest, just curious if anyone can comment on the below scenario. It boils down to: Can I move the AD objects without impacting the underlying services? Do Public Folders or any of the other Exchange resources care about where the objects exist in AD? Thanks, Geoff ------------------------------------------------------------------------------------------- This is more of an Active Directory question, but it relates directly to the Exchange objects. For whatever reason, we have two 'Microsoft Exchange System Objects' containers. One in the root of the domain, another one level down in another Organizational Unit, for example 'LegacyStuff'. CN=Microsoft Exchange System Objects,DC=domain,DC=com and OU=LegacyStuff,CN=Microsoft Exchange System Objects,DC=domain,DC=com The container under LegacyStuff seems to be where all the Public folder objects live. Dozens of globalevents, internal, and OWAScratchPad objects. The container in the root of the domain only contains SystemMailbox{GUID} objects and the 'Exchange Install Domain Servers' group. This was a 2003 to 2010 "move". It was not a migration according to my coworker who was here at the time-they did a fresh 2010 install and migrated mailboxes. My assumption is prior to installing Exchange 2010 someone moved the original container into another OU and let the Exchange 2010 install recreate the root container. My goal is to consolidate these objects under the root container and delete the other container and its parent 'LegacyStuff' OU. However, I don't want to break these existing objects. I can't find anything online about any impact of moving these objects, so I'm reaching out to some of the experts on this list. Though it may not really clarify the issue I am attaching a sanitized screenshot. Thank you in advance for any help. -Geoff Confidentiality Notice: This is a transmission from Montage Health. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Montage Health. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Montage Health. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
