Re: Rehome Public Folder Problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

I guess I should clarify some info: I already have a stand alone exchange
server that has PF replicas. I have already moved all mailboxes to the stand
alone server.

My problem is with Outlook XP users caching a pointer to the original PF
store. These clients are not updating to point to the new server. All PFs
have been moved to the new server and replication has been stopped. If I
shut down the cluster these clients will not see any public folders unless I
recreate the users Outlook profile.


"John Fullbright" wrote:

Take a staged approach. Evict one node from the cluster. Build your first
server and create PF replicas there. Repoint the PF tree to the newly built
server. Let it cook a few days. Retire the remaining cluster node and
rebuild ....


"MASIV" <MASIV@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:97D7D77D-344C-4EC6-BCD1-7F1D65CBEAEF@xxxxxxxxxxxxxxxx
As I understand it Exchange cannot be removed unless all stores are
removed.
If I were to shut down the source server (retiring cluster) users running
Office XP would not be able to see the public folders. Office 2K3 users
would be fine.

Once I remove exchange and break the cluster the hard drives in these
servers will be replaced with new drives and new servers loaded.

If I shut down the cluster, the only option I would have is to recreate
each
users Outlook profile. This affects aprox. 600 users.

All public folders have been replicated to the new destination server and
replication has been removed from the retiring server. The outlook
profiles
for Office XP users are not updating automatically like the Office 2K3
users.

"Nuevo" wrote:

What about just pointing the public folder tree on server to be retired
to
the new server rather than dismounting. Allow clients to pick up new pf
server themselves.

Nue
"MASIV" <MASIV@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6B39F2D9-BD03-4E9C-9793-2F45ACCBABE3@xxxxxxxxxxxxxxxx
Situation: Have a Windows 2003 cluster with Exchang 2003. Need to
remove
Exchange from this cluster, break cluster, redeploy the servers as
stand
alone Exchange servers.

Problem: Rehomed public folders per MS KB article (822931). We are
running
a mix of Office XP and Office 2003. If I dismount the public folder
store
on
the server that is retiring, Office 2003 clients work fine but Office
XP
clients get a public folders cannot be displayed error.

I found multiple entries in the Office XP clients registry that point
the
default public folder store to the server that is retiring. If I
delete
and
create a new Outlook profile everything works fine and the client will
be
able to connect to the public folders after the public folder store on
the
retiring server is dismounted.

Question: How can I resolve this without logging on as each affected
user
and recreating the Outlook profile. Or, make the registry changes
without
touching each desktop. The registry entries appear to be in different
GUID
entries so a .reg fix might not work.

Thanks in adavance






.

Relevant Pages

  • Re: Public folder replication between Exchange 2007 and Exchange 2010
    ... If you see the hierarchy then it's replicating. ... Replicas won't magically appear in the Exchange 2010 public store except for those system folders that automatically get created. ... You will need to go through your public folders and add the 2010 server's public store as a replica. ... Verifying that your server has the public folder hierarchy by using the Get-PublicFolderStatistics cmdlet. ...
    (microsoft.public.exchange.admin)
  • Re: Rehoming Public Folders in E5.5
    ... my understanding is that PFAdmin is just a tool that allows you ... Some artciles describe creating replicas. ... Add the target exchange server to the Replicas tab under the ... the public folders properties page. ...
    (microsoft.public.exchange.admin)
  • Public Folder Replication Problems (during E2K -> E2K3 migration)
    ... We recently brought up a new E2K3 SP1 server and have run the pfmigrate.wsf ... to create replicas on the new server, so there are 2 replicas for ... public folders appeared to be replicating without incident. ... error messages on either Exchange box or any of our DCs. ...
    (microsoft.public.exchange.admin)
  • Re: moving public folders exchange 2003 and 2007
    ... E2K3Serv1 and 2 have common public folders, ... Okay, Homer, let's clear something up. ... So are you saying that E2k3Serv1 and E2k3Serv2 both have replicas of one subset of folders and E2k3Serv3 has replicas of a different subset? ... (incorrect server and not the server specified in the exchange management ...
    (microsoft.public.exchange.admin)
  • Re: Moving public folders
    ... when I look in public folders on the new server they are empty. ... I have been reading about the changes in SP2 and would like to use the move ... It told me that all the replicas were already moved to the new ...
    (microsoft.public.exchange.admin)