Remove Final Replicas prior to removing First Exchange Server (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Public Folders



Message

Scouser -> Remove Final Replicas prior to removing First Exchange Server (30.Nov.2006 1:26:10 PM)

I installed PFDAVadmin (as advised in aprevious post) hoping to resolve an issue I have regards removal of public folder replicas.
I am unable to remove replication on two system folders:
PUBLIC FOLDER HIERARCHY
SYSTEM CONFIGURATION

PFDAVadmin permissions on SYSTEM CONFIGURATIONS list:
\everyone role – reviewer
NT AUTHORITY\ANONYMOUS LOGON role = none

If I choose to add (Domain\administrator) I receive error on commiting changes: The remote server returned an error (401) Unauthorized?
This is also the case if I try from the old exchange server?
I feel it is a permission issue? Could it be within IIS?
Regards,
Phil.



jchong -> RE: Remove Final Replicas prior to removing First Exchange Server (30.Nov.2006 3:24:42 PM)

1. From your Exchange server or Domain Controller, go to Start, Run,
ADSIEDIT.MSC Click Ok. (ADSIEDIT is part of your Windows 2000\2003
Support Tools found on the CD)

Expand the Configuration Container.

CN=Services
CN=Microsoft Exchange
CN=Your Exchange Org
CN=Administrative Group
CN=First Administrative Group

Highlight CN=Folder Hierarchies.

On the right pane, highlight CN=Public Folders and select properties.
Scroll down to find the attribute, msexchowningpftreebl and double click it, does your old pf server show? If so remove it.



Scouser -> Error (1.Dec.2006 6:49:36 AM)

James many thanks for your reply. I applied your suggestion and it returned an error when I tried to apply the change:

quote:


The attribute cannot be modified because it is owned by the system"


Any ideas??
Many Thanks,
Phil.



jchong -> RE: Error (1.Dec.2006 10:30:17 AM)

You are correct, you cannot delete it this way because this attribute actually pulls that information by the system so you have to go to the source. If this pf server is not being used and planning on being decomissioned and you can't delete it through ESM because it says it has a replica, delete it through adsiedit. Then your system will remove it from msexchowningpftreebl.

http://msexchangetips.blogspot.com/2006/07/exchange-cannot-delete-public-folder.html



Scouser -> Do not quite understand? (1.Dec.2006 11:35:23 AM)

Hi James. I tried to implement your initial suggestion:
[quote
1. From your Exchange server or Domain Controller, go to Start, Run,
ADSIEDIT.MSC Click Ok. (ADSIEDIT is part of your Windows 2000\2003
Support Tools found on the CD)

Expand the Configuration Container.

CN=Services
CN=Microsoft Exchange
CN=Your Exchange Org
CN=Administrative Group
CN=First Administrative Group

Highlight CN=Folder Hierarchies.

On the right pane, highlight CN=Public Folders and select properties.
Scroll down to find the attribute, msexchowningpftreebl and double click it, does your old pf server show? If so remove it.


This generated error:
quote:

The attribute cannot be modified because it is owned by the system


Current Status:
I installed a second exchange server onto a 'Member Server' (better spec hardware) to replace the old exchange server currently installed on a DC. I migrated as per KB article 822931. Replication all seemed to go OK. I disconnected the old exchange server. I then noted a build up of messages in a queue relating to public folder replication? So now we arrive at my problem. I hope to remove the first exchange server then demote the old server back to a member server then format and rebuild. Can I remove the replication on PUBLIC FOLDER HIERARCHY & SYSTEM CONFIGURATION by implementing your previous post 'deleting the whole public folder using ADSI Edit'??

Sorry the lenght of post, just want to give you all the facts!!
Many Thanks,
Phil.



jchong -> RE: Do not quite understand? (1.Dec.2006 11:43:37 AM)

>Can I remove the replication on PUBLIC FOLDER HIERARCHY & SYSTEM >CONFIGURATION by implementing your previous post 'deleting the whole >public folder using ADSI Edit'??

Yes. The queue buildup is likely public folder hiearchy messages. You can delete your old servers pf store. However, sometimes you run into the issue where it says theres still replicas which can be a pain. If so just delete the old servers pf store through adsiedit.



Scouser -> Thanks (1.Dec.2006 12:40:37 PM)

James many thanks for the swift response. I will DELETE!!! :)
Many Thanks,
Phil.



Scouser -> One more question! (1.Dec.2006 1:29:45 PM)

If I delete the PF from my first exchange server using ADSI Edit, will my second exchange server still think replication is occurring?
Thanks,
Phil.



jchong -> RE: One more question! (1.Dec.2006 8:01:07 PM)

No because your pf tree hiearchy will remove this pf store from the  the attribute, msexchowningpftreebl. Remember when we tried to remove it here but it said it ws owned by the system? If you delete the store it will remove it from here automatically. However in some instances I have seen it where it won't remove it and you will have to go in here and remove it. This time it will let you because the store is now gone since you deleted it. Once you delete the store just check your queues to see if it's building up with pf replication messages.



Scouser -> just to clarify...... (2.Dec.2006 3:23:16 AM)

Hi once again James. Just to clarify!!
My original intention was NOT to delete just the PF from first exchange server. I wanted to ensure there were NO relicas prior to complete removal.

Server1 (original server) - Storage Group2 - PF Store
Server2 (new server) - Storage Group1 - PF Store

Server 1 was the First exchange server in the organisation. I migrated as per KB 822931. I was now hoping to put the exchange disc into server 1 and remove exchange (leaving only server 2 in the ESM!!).

I no longer have message appearing in any queues on server 2.
My only issue is I am unable to remove replicas on 2 folders (as posted previously). I have never tried to remove the PF from server 1 within ESM. I hoped complete removal would take care of that!! 

I hope I am making sense!! Sorry to drag this one out. You have been most helpful and patient!!
Many Thanks,
Phil.



jchong -> RE: just to clarify...... (2.Dec.2006 8:49:35 AM)

>My original intention was NOT to delete just the PF from first exchange server. I >wanted to ensure there were NO relicas prior to complete removal.

Absolutely [:)]

>Server 1 was the First exchange server in the organisation. I migrated as per KB >822931. I was now hoping to put the exchange disc into server 1 and remove >exchange (leaving only server 2 in the ESM!!).

Good [:D]

It's always good to shut down your server for a couple of days to see what issues you get incase say all your pfs were not migrated. Then if an issue comes up, say a user can't access some pf, which didn't get migrated, you can bring the server up and replicate it. Also, what you can do is, make a copy of your pf database and put it somewhere esle. Then if you removed Exchange and later found that, a pf is missing, you can mount that db on another server. This has actually been helpful to me in the past when I had to remove pfs in the past and a week or so later found that some pfs did not replicate.



Scouser -> Thanks (2.Dec.2006 10:02:14 AM)

Thanks once again James. So from that I take it is is OK to remove the PF from sever 1 using ADSI Edit therefore removing the remaining replicas PUBLIC FOLDER HIERARCHY & SYSTEM FOLDER.
Many Thanks for all your advice.
Phil.



jchong -> RE: Remove Final Replicas prior to removing First Exchange Server (2.Dec.2006 10:16:05 AM)

So from that I take it is is OK to remove the PF from sever 1 using ADSI Edit therefore removing the remaining replicas PUBLIC FOLDER HIERARCHY & SYSTEM FOLDER.

Yup [:D], if you want to be extra safe, copy the pf database from the old server to a file server so you have the ability to restore quickly without having to go to backup and restoring if you end up needing it later down the road.



Scouser -> Thanks (2.Dec.2006 10:30:42 AM)

Thanks James.



Page: [1]