Re: Removing Empty, but Replicated Public Folders

Ed, see screen shot of ESM here:

http://www.flickr.com/photos/14900074@N02/1551630959/



"Bill Hobson" <Ih8spamwjh2@xxxxxxxxxxxxxx> wrote in message
news:uhmIJENDIHA.3332@xxxxxxxxxxxxxxxxxxxxxxx
There is *nothing* there. Yet E2K7 says it won't delete because it claims
there are replicas!

E2K7 is just not ready for prime time, IMHO.

"Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx> wrote in message
news:%230tXNsFDIHA.748@xxxxxxxxxxxxxxxxxxxxxxx
Using Exchange 2003 System Manager, under the Administrative Group,
Folders object, you should see the hierarchy of the public folders in
your Exchange organization, not under the server or database objects.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Bill Hobson" <Ih8spamwjh2@xxxxxxxxxxxxxx> wrote in message
news:elWMOBFDIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
You said:
"From Exchange 2003 ESM, remove the Exchange 2003 server replicas of the
Exchange 2007 folders"

Exactly where? When I go to the E2K7 Server's Public Folder Database,
Public Folder Instances, it will not let me remove the replicas -
period. I see no other place where I can even have an option to remove
the replicas. Do you?

"Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx> wrote in message
news:uZWfn$DDIHA.4836@xxxxxxxxxxxxxxxxxxxxxxx
Inline
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Bill Hobson" <Ih8spamwjh2@xxxxxxxxxxxxxx> wrote in message
news:umoB5pDDIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
See inline comments...
"Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx> wrote in message
news:O3wZ8ICDIHA.5856@xxxxxxxxxxxxxxxxxxxxxxx
Right. Look at the properties of the folder itself, Replicas tab.
What public folder servers hold replicas?
There are no Public Folders on the E2K7 server,
It is replicating the instances of global events, internal, Offline
Address Book, etc.to the E2K3 server - any attempts to remove replicas
meets with the comment "Can not remove the selected replica(s) becuase
a public folder must have at least one replica." It doesn't seem to
care that the %(&*#%(&^($ thinks are all 0K in size!

From Exchange 2003 ESM, remove the Exchange 2003 server replicas of the
Exchange 2007 folders, and if the Exchange 2003 server holds the only
replica of a folder that should be on the Exchange 2007 server, you
could either delete the folder or put the only replica on the Exchange
2007 server.


Remove the Exchange 2007 server and

Do you mean to turn the server off and then remove it? It won't allow
deleting while it is on. If so, will I then be able to bring it back
up and remove E2K7 fron the server so that all the Active Directory
junk is removed too? I really want a clean uninstall as it seems that
everything I do in E2K7 bites me badly.

No, I mean remove that server name from the list of replicas. You've
said you've done that, though.

then propagate the replicas settings down to all child folders. Do
the same for all other top level folders. Also remove replicas of
the Free/Busy and OAB system folders. Doing that will ensure that
your Exchange 2007 public folder store won't have any replicas
assigned to it of your Exchange 2003 public content. If you have
done all of this, then there should be no need to run the PowerShell
script you're trying to run becuase there will be no replicas in the
Exchange 2007 public store to move.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Bill Hobson" <Ih8spamwjh2@xxxxxxxxxxxxxx> wrote in message
news:OaoHDFCDIHA.972@xxxxxxxxxxxxxxxxxxxxxxx
Then I don't understand what you are asking me to do. When you say
"top level folder", what do you mean exactly? Top level under First
Administrative Group, Folders, Public Folders on the Exchange 2003
server? It shows no replication being done - the only server listed
under the Replication tab is the 2003 server itself for each folder
directly under Public Folders.

You said:
Using Exchange 2003 System Manager, on each *top-level folder*,
change the
replicas to remove the Exchange 2007 server, and then right-click
the
folder, select All Tasks, Propagate Settings, and choose to
propagate the
replicas. You can also use PFDAVADMIN to do this, or PFMIGRATE, but
I don't
think either are any easier for you if you're talking about ending
up with a
simple structure.

"Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx> wrote in message
news:uI33b8BDIHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
That isn't the way I told you to do it.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Bill Hobson" <Ih8spamwjh2@xxxxxxxxxxxxxx> wrote in message
news:%23Szo3iADIHA.5328@xxxxxxxxxxxxxxxxxxxxxxx
No can do - I tell the replicas on the Exchange 2007 server via
ESM, right-click the Exchange 2007 Public Folder Store, select
"Move All Replicas" to move back to the Exchange 2003 server and
get the following message:
"Your profile is not configured.
An unexpected, unknown error occurred.
Microsoft Exchange Server Information Store
ID no: 8004011c-0521-00000000

ID no: c1050000
Exchange System Manager"

I really hate working with Exchange 2007 - it appears to me that
it was rushed to market, disregarding all of the things really
necessary to make it work with Exchange 2003, IMHO.

Having given feedback to MS on the Message Tracking tool, I got
this response, which appears to strengthen my opinion:
"Thank you for the feedback Bill. We are sorry you aren't
satisfied with the new GUI (I assume you are talking about the GUI
since you are sending feedback on this alias). Since transport
was changed significantly in Exchange 2007, the message tracking
logic had to be completely reworked, and the bulk of our effort in
the admin area went into putting all of our business logic into
Powershell cmdlets. Due to resource and time constraints, the GUI
work was originally cut and then we decided to try to ease the
expected pain somewhat by providing a scripted UI using the same
framework we had developed for our troubleshooter tools. Since
its scripted, it is unfortunately less sophisticated."


"Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx> wrote in message
news:eMYHZ72CIHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
Using Exchange 2003 System Manager, on each top-level folder,
change the replicas to remove the Exchange 2007 server, and then
right-click the folder, select All Tasks, Propagate Settings, and
choose to propagate the replicas. You can also use PFDAVADMIN to
do this, or PFMIGRATE, but I don't think either are any easier
for you if you're talking about ending up with a simple
structure.

Don't forget to remove the replicas of any of the Exchange 2003
Schedule+ Free/Busy folders and the Offline Address Book folders.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Bill Hobson" <Ih8spamwjh2@xxxxxxxxxxxxxx> wrote in message
news:OMY4Ci0CIHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
I am throwing in the towel on Exchange 2007 until a ServicePack
or 2 are out - it has crashed my Exchange 2003 system too many
times. I am trying, after removing all mailbox databases, to
remove the Public Folder database, which I am forced to remove
before removing Exchange 2007. I am running the
moveallreplicas.ps1 script and get this:

[PS] D:\PROGRAM FILES\microsoft\exchange
server\Scripts>moveallreplicas.ps1 -ser
ver:"email2" -newserver:"email"
WARNING: Object Public Folder Store has been corrupted and it is
in an
inconsistent state. The following validation errors have been
encountered:
WARNING: "PublicFolderStore(EMAIL)" is not valid for Alias.
Valid values are:
Strings formed with characters from a to z (uppercase or
lowercase), digits
from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {,
|, } or ~. One or
more periods may be embedded in an alias, but each one of them
should be
preceded and followed by at least one of the other characters.
Unicode
characters from U+00A1 to U+00FF are also valid in an alias, but
they will be
mapped to a best-fit US-ASCII string in the email address which
is generated
from such an alias.
WARNING: Object Public Folder Store has been corrupted and it is
in an
inconsistent state. The following validation errors have been
encountered:
WARNING: "PublicFolderStore(EMAIL)" is not valid for Alias.
Valid values are:
Strings formed with characters from a to z (uppercase or
lowercase), digits
from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {,
|, } or ~. One or
more periods may be embedded in an alias, but each one of them
should be
preceded and followed by at least one of the other characters.
Unicode
characters from U+00A1 to U+00FF are also valid in an alias, but
they will be
mapped to a best-fit US-ASCII string in the email address which
is generated
from such an alias.
<end of output - I didn't copy it twice - this is the real
output!>

So what hurculean feat do I need to do to get rid ot the
replicas and get this ()*&()*& server system off my network and
out of my AD structure?























.

Loading