Re: Rehome Public Folder Problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine ... member of the NLB cluster, setup NLB on it, plug the NICs ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Once again, ARP is an RFC standard, if you are having to make static entries in unicast mode, then your network device is not in compliance. ... Windows Server 2008 Readiness Team ... I was feeling nervous about our teaming-capable adapter as I read it might be sending out heartbeats, so I disabled it AND configured the cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine when no NLB is installed, but when it is, things start going screwy. ...
    (microsoft.public.windows.server.clustering)
  • Re: MSCS - arp cache/mac-address problems
    ... I just want to rule out the cluster and server/storage software/hardware ... MVP - Windows Server - Clustering ... On some clients I get problems when I failover one group with Virtual ... I make a arp -d to clear the cache then I ping again. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... One server with no cluster configured - all works ok. ... When static ARP mappings are added all works ok. ... I thought that the litmus test was that the router functions fine when ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... NLB is installed, but when it is, things start going screwy. ... The servers are a couple of switches away from the router so I ... 'exterior' to the NLB cluster itself. ...
    (microsoft.public.windows.server.clustering)