Michael – thanks for the commands.
The first one returned pretty much what I expected it to. All the public
folders that we’re currently using.
The second command threw out “Couldn’t find public folder
“\NON_IPM_SUBTREE”
“\NON_IPM_SUBTREE\EFORMS REGISTRY”
“\NON_IPM_SUBTREE\Events Root”
“\NON_IPM_SUBTREE\Events Root\EventConfig_servername” (several of these, all of
which are servers that no longer exist)
“\NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK”
“\NON_IPM_SUBTREE\OWAScratchPad{8E602B42-1573-4391-A444-EE25D4EAA6B5}”
“\NON_IPM_SUBTREE\OWAScratchPad{A6894718-A560-4698-A4EA-F907318358E2}”
"\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY"
"\NON_IPM_SUBTREE\StoreEvents{A6894718-A560-4698-A4EA-F907318358E2}"
"\NON_IPM_SUBTREE\StoreEvents{A6894718-A560-4698-A4EA-F907318358E2}\globalevents"
"\NON_IPM_SUBTREE\StoreEvents{A6894718-A560-4698-A4EA-F907318358E2}\internal"
All of are sitting System Public Folders.
I should be able to remove SCHEDULE+ FREE BUSY.
I should be able to remove the EventConfig servername ones because they are no
longer in existence.
I am concerned about the OFFLINE ADDRESS BOOK, OWAScratchPad, and particularly
the EFORMS REGISTRY which has an “Organization Forms” under it – and we use
Forms.
Initially I was also seeing some weirdness when I was using the Public Folder
Administration to change permissions, like “you don’t have permission to do
this”. That seems to have worked itself out after some time, after getting rid
of the old “admin group”. That was a relief as what I found using Google to
remedy that involved using ADSI to copy and paste distinguished names from
place to place.
I’m just looking for some reassurance before cleaning house.
From: [email protected] [mailto:[email protected]] On
Behalf Of Michael B. Smith
Sent: Tuesday, July 19, 2016 1:45 PM
To: [email protected]
Subject: RE: [Exchange] Public Folder email address non-deliverable after
decommissioning last Exchange 2003 server
Generally speaking, to look at all valid public folders takes two commands:
Get-PublicFolder –recurse ‘\’ | Get-PublicFolderStatistics
Get-PublicFolder –recurse ‘\non_ipm_subtree’ |
Get-PublicFolderStatistics
But yes, if your PF hierarchy had to be recreated at some point (or even when
migrating from Exchange 5.5 to 2000/2003) it is possible for PFs to become
orphaned.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Maglinger, Paul
Sent: Tuesday, July 19, 2016 2:32 PM
To: '[email protected]'
Subject: RE: [Exchange] Public Folder email address non-deliverable after
decommissioning last Exchange 2003 server
Seems to be. Now it seems I’ve opened a can of something else.
I’m finding Public Folders showing up in ADUC that I can’t find in
Get-PublicFolderStatistics or the Public Folder Administration tool. Trying to
determine if it’s safe to clean them up. Some seem to be quite old. I don’t
see them in Outlook either. Orphaned public folders?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Michael B. Smith
Sent: Monday, July 18, 2016 6:21 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [Exchange] Public Folder email address non-deliverable after
decommissioning last Exchange 2003 server
Yeah, the “old” admin group and the “old” server are the traditional issues.
Is replication working now?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Maglinger, Paul
Sent: Monday, July 18, 2016 4:42 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [Exchange] Public Folder email address non-deliverable after
decommissioning last Exchange 2003 server
Thanks Michael. I followed the steps outline here to decommission:
https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
Pretty straight forward stuff. Everything pretty much went without a hitch,
there were no error messages or anything like that.
We’re running SP3, UR11 – I saw something awhile back saying to stay away from
UR12.
In working through this I’m seeing some public folders that were mail-enabled
now are no longer that way. Strange that when I re-create them it gripes that
the email address is being used. When I go into ADUC I can still see the
object in the Microsoft Exchange System Objects which I have to delete to free
up the email address.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Michael B. Smith
Sent: Monday, July 18, 2016 3:19 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [Exchange] Public Folder email address non-deliverable after
decommissioning last Exchange 2003 server
Well, that got my attention. Busy day, I would’ve seen this tonight. ☺
Paul, did you update 2010 to SP3 UR12 (or whatever the latest is)?
How long have the supposed replicas existed on the server where you “cannot see
them”?
This actually sounds like two different problems, conflated. One of which is
that you may have corrupt security entries in AD for the PF databases
(basically that the 2003 server was not removed cleanly – was it?). The second
that PF replication is failing.
How did you decommission the 2003 server?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Richard Stovall
Sent: Monday, July 18, 2016 4:05 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [Exchange] Public Folder email address non-deliverable after
decommissioning last Exchange 2003 server
This is why you call our friend in Charlottesville to help with stuff like
this...
:-)
On Mon, Jul 18, 2016 at 10:11 AM, Maglinger, Paul
<[email protected]<mailto:[email protected]>> wrote:
Running Exchange 2010
I decommissioned the last Exchange 2003 server over the weekend. I come in
this morning to find out that several of the mail-enabled Public Folders are
now kicking out undeliverable messages:
"There's a problem with the recipient's mailbox. Please try resending the
message. If the problem continues, please contact your helpdesk."
The public folders on kept on the same mailbox servers that are part of a 3
node DAG. I have public folder replication set up between 2 of those servers.
On server 1 I can't see anything in the public folders in question. On server
2 I can.
Google pointed me to a technet thread from 02/2010 where the "solution" was to
export the data from the public folder, then create a new public folder and
import the data into it.
I haven't seen anything else newer, so is this my only option or has someone
come up with a fix in the past 6 years?
-Paul
