Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Wed, 18 Jun 2008 22:41:38 +0300,    group: microsoft.public.exchange.admin        back       


Public folder repliaction remove problem    
Hello,

 I doing migration from Exchange 2003 to Exhange 2007. When i tried to move Public Folders to new 
server some folders still exist in old server. After replication i removed old server from 
replication partners list, but some public folders still exist on old server when i look in old 
server Public Folder Instances :( In these Public folder properties i removed old server, bet when i 
look in "Details" of Replication Status in the server names old server still exists :( How it can by 
fixed - i need to remove old server, but i can't do it because some public folders still "exists" in 
old PF Db :(

Thanks for help !
date: Wed, 18 Jun 2008 22:41:38 +0300   author:   Diamondas

Re: Public folder repliaction remove problem    
No one have this problem - all replications removed without problems ?

"Diamondas"  wrote in message 
news:uTwmUtX0IHA.4500@TK2MSFTNGP03.phx.gbl...
> Hello,
>
> I doing migration from Exchange 2003 to Exhange 2007. When i tried to move Public Folders to new 
> server some folders still exist in old server. After replication i removed old server from 
> replication partners list, but some public folders still exist on old server when i look in old 
> server Public Folder Instances :( In these Public folder properties i removed old server, bet when 
> i look in "Details" of Replication Status in the server names old server still exists :( How it 
> can by fixed - i need to remove old server, but i can't do it because some public folders still 
> "exists" in old PF Db :(
>
> Thanks for help !
>
date: Thu, 19 Jun 2008 12:38:27 +0300   author:   Diamondas

Re: Public folder repliaction remove problem    
On Jun 19, 2:38 pm, "Diamondas"  wrote:
> No one have this problem - all replications removed without problems ?
>
> "Diamondas"  wrote in message
>
> news:uTwmUtX0IHA.4500@TK2MSFTNGP03.phx.gbl...
>
>
>
> > Hello,
>
> > I doing migration from Exchange 2003 to Exhange 2007. When i tried to move Public Folders to new
> > server some folders still exist in old server. After replication i removed old server from
> > replication partners list, but some public folders still exist on old server when i look in old
> > server Public Folder Instances :( In these Public folder properties i removed old server, bet when
> > i look in "Details" of Replication Status in the server names old server still exists :( How it
> > can by fixed - i need to remove old server, but i can't do it because some public folders still
> > "exists" in old PF Db :(
>
> > Thanks for help !- Hide quoted text -
>
> - Show quoted text -

Well, this has been a pain in the wrong place - pf replication from
E2k3 to E2k7 and subsequently removing E2k3 / E2k7. Worst part is when
u remove all PFs there would alwys be some instance staying back not
allowing you to remove E2k3 / E2k7.

The most fastest way to get rid of 2k3 is to take a SystemState backup
(thats to manage AD), take a backup of DB (thats to be on a safer
side). Use article 833396, drill down to server - information store
level - public folder store - delete this.

Now, since u are through with the PF part - you can go ahead and
uninstall the box (again, hoping you dont have any mailboxes on it)
date: Thu, 19 Jun 2008 18:33:02 -0700 (PDT)   author:   Tushar Shah

Re: Public folder repliaction remove problem    
Is there the only way to forcibly delete PF doing it by this way : ?

----------------
Run ADSI Edit.
Drill down to...

Configuration
+ CN=Configuration
 + CN=Services
  + CN=Microsoft Exchange
   + CN=YOUR ORGANISATION
    + CN=Administrative Groups
     + CN=First Administrative Group
      + CN=Servers
       + CN=SERVER NAME
        + CN=InformationStoreYou should be able to see your Storage Groups in this container. You 
can select it on the left, and see the stores within it in the righthand pane.

If you need to remove a store, delete it then stop/start the Microsoft Exchange Information Store 
service to be sure that it's removed, and you can now delete the files related to the store.

-----------------------------------

Is it safe or i can lost public folder that left in instances list ?


"Tushar Shah"  wrote in message 
news:648ed2e1-1256-4270-9b7a-73515b1e9bd6@u6g2000prc.googlegroups.com...
On Jun 19, 2:38 pm, "Diamondas"  wrote:
> No one have this problem - all replications removed without problems ?
>
> "Diamondas"  wrote in message
>
> news:uTwmUtX0IHA.4500@TK2MSFTNGP03.phx.gbl...
>
>
>
> > Hello,
>
> > I doing migration from Exchange 2003 to Exhange 2007. When i tried to move Public Folders to new
> > server some folders still exist in old server. After replication i removed old server from
> > replication partners list, but some public folders still exist on old server when i look in old
> > server Public Folder Instances :( In these Public folder properties i removed old server, bet 
> > when
> > i look in "Details" of Replication Status in the server names old server still exists :( How it
> > can by fixed - i need to remove old server, but i can't do it because some public folders still
> > "exists" in old PF Db :(
>
> > Thanks for help !- Hide quoted text -
>
> - Show quoted text -

Well, this has been a pain in the wrong place - pf replication from
E2k3 to E2k7 and subsequently removing E2k3 / E2k7. Worst part is when
u remove all PFs there would alwys be some instance staying back not
allowing you to remove E2k3 / E2k7.

The most fastest way to get rid of 2k3 is to take a SystemState backup
(thats to manage AD), take a backup of DB (thats to be on a safer
side). Use article 833396, drill down to server - information store
level - public folder store - delete this.

Now, since u are through with the PF part - you can go ahead and
uninstall the box (again, hoping you dont have any mailboxes on it)
date: Fri, 20 Jun 2008 12:15:31 +0300   author:   Diamondas

Re: Public folder repliaction remove problem    
On Thu, 19 Jun 2008 18:33:02 -0700 (PDT), Tushar Shah
 wrote:

					[ snip ]


>Well, this has been a pain in the wrong place - pf replication from
>E2k3 to E2k7 and subsequently removing E2k3 / E2k7. Worst part is when
>u remove all PFs there would alwys be some instance staying back not
>allowing you to remove E2k3 / E2k7.
>
>The most fastest way to get rid of 2k3 is to take a SystemState backup
>(thats to manage AD), take a backup of DB (thats to be on a safer
>side). Use article 833396, drill down to server - information store
>level - public folder store - delete this.
>
>Now, since u are through with the PF part - you can go ahead and
>uninstall the box (again, hoping you dont have any mailboxes on it)

Before you do that, have a look at this:
http://msexchangeteam.com/archive/2007/07/09/445967.aspx

The "dangling replica" is pretty common, but it may be that you have a
more general problem with PF replication.
date: Fri, 20 Jun 2008 20:30:47 -0400   author:   Rich Matheisen

Re: Public folder repliaction remove problem    
What is "dangling replica" ?
All Public folders replicated correctly except some of them - i tried to add and remove replication 
of that left folders but they don't still left on old server instances list :(

"Rich Matheisen"  wrote in message 
news:hmio54lsnmfrrleflq9m61h9is1eeieec2@4ax.com...
> On Thu, 19 Jun 2008 18:33:02 -0700 (PDT), Tushar Shah
>  wrote:
>
> [ snip ]
>
>
>>Well, this has been a pain in the wrong place - pf replication from
>>E2k3 to E2k7 and subsequently removing E2k3 / E2k7. Worst part is when
>>u remove all PFs there would alwys be some instance staying back not
>>allowing you to remove E2k3 / E2k7.
>>
>>The most fastest way to get rid of 2k3 is to take a SystemState backup
>>(thats to manage AD), take a backup of DB (thats to be on a safer
>>side). Use article 833396, drill down to server - information store
>>level - public folder store - delete this.
>>
>>Now, since u are through with the PF part - you can go ahead and
>>uninstall the box (again, hoping you dont have any mailboxes on it)
>
> Before you do that, have a look at this:
> http://msexchangeteam.com/archive/2007/07/09/445967.aspx
>
> The "dangling replica" is pretty common, but it may be that you have a
> more general problem with PF replication.
date: Wed, 25 Jun 2008 12:35:29 +0300   author:   Diamondas

Re: Public folder repliaction remove problem    
On Wed, 25 Jun 2008 12:35:29 +0300, "Diamondas"
 wrote:

>What is "dangling replica" ?

It where you have no replicas in the properties of the public folder,
but there's an instance of the folder still in the database.

>All Public folders replicated correctly except some of them - i tried to add and remove replication 
>of that left folders but they don't still left on old server instances list :(

http://msexchangeteam.com has lots of good information about the
process. Some of it's labeled Exchange 2007, but the information's
still good for Exchange 2003.

---
Rich Matheisen
MCSE+I, Exchange MVP
date: Wed, 25 Jun 2008 09:18:47 -0400   author:   Rich Matheisen

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us