Rami-which adsiedit steps did you do? There were additional adsiedit steps we had to do to remove the references on the DBs themselves that I didn't find online-I had called Premier/PSS on this one.
From: [email protected] [mailto:[email protected]] On Behalf Of Rami SIK Sent: Monday, June 09, 2014 4:18 PM To: [email protected] Subject: [Exchange] RE: Public Folders in Exchange 2013? Not yet since I am not sure if I should do this or do something with outlook clients first! Rami From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, June 09, 2014 4:13 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Public Folders in Exchange 2013? Have you removed all "PF databases" from all your mailbox databases? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rami SIK Sent: Monday, June 9, 2014 6:57 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Public Folders in Exchange 2013? I finally managed to decommission one of my Exchange 2007 servers: it did not go through smoothly because of the infamous Public Folders issue. I ended up using ADSIEdit to remove the PF entry for that server, and only then I was able to uninstall the product. Now, I have the last Exchange 2007 server to decommission. I can now follow the same process and use ADSIEdit to uninstall that, but I am worried about the Outlook 2010 clients that still show a connection to that Exchange 2007 server for Public Folders when I do CTRL+Click and select "Connection Status". So, more specifically, I wonder what happens to Outlook 2010 clients connecting to that old server for PFs when I uninstall the server. Is there anything I need to do for preventing Outlook clients from looking up for PF server? The other day, I just shutdown Exchange 2007 server to see what would happen, and all Outlook 2010 clients got connection errors and stop working until I brought that server backup again. Basically, I do not want to keep PFs anymore on my Exchange 2013 servers. Rami From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller Bonnie L. Sent: Friday, June 06, 2014 10:24 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: Public Folders in Exchange 2013? We finally migrated the last of our PFs when going from 2007 to 2013. You don't want to just drop or block them-if they really aren't in use and you don't want to migrate, then there is a procedure for removing them you'll want to follow through with. We did have trouble with the very last step and had to open a Premier case with Microsoft to remove via adsiedit-from what I was seeing online, it's a problem quite a few people have run into. If you haven't already, give this a read: http://technet.microsoft.com/en-us/library/cc164367(v=exchg.80).aspx I don't have any experience with migrating them to 2013, so can't speak to that. -Bonnie From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rami SIK Sent: Friday, June 06, 2014 9:34 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Public Folders in Exchange 2013? Hi All, I would like to get some feedback about dropping Public Folders (PFs) as part of a migration from Exchange 2007 to 2013. Although we are not using PFs on Exchange 2007, Outlook 2010s are still pointing to 2007 server. So, there are two options: (1) migrate the PFs and let Outlook point to 2013 servers so that I can take 2007 ones offline, (2) Disable/prevent Outlook 2010 from using PFs say through GPO if this is ever possible, and then just drop 2007 servers without enabling any PFs on 2013 servers. Any idea appreciated. Rami ________________________________ If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
