Migrating 2003 to 2010 - public folders - stuck in SmtpRelayToTiRg queue?

I'm in the process of migrating Exchange 2003 over to 2010. Both systems are DCs (2010 running on server 2012). The routing group connectors (which I believe this queue relates to) are in place. All the user mailboxes and mail flow has been migrated over
to 2010 already, users have been happily emailing internally and externally as normal for a few days now, and I wish to shut 2003 down. I've just moved over the OAB and followed instructions for moving public folder replicas which I found here : http://exchangeserverpro.com/migrate-public-folders-from-exchange-2003-to-exchange-server-2010/
The process began successfully about 12 hours ago, and after a while I noticed some of the PF instances from 2003 appearing over on 2010. But it hasn't progressed in a long time, with only a few of the instances having appeared on 2010, and none of them
have disappeared from 2003. Then I noticed a queue suddenly building up on 2010, under "SmtpRelayToTiRg". There's over 100 messages in there, and they're all apparently destined for 2003 but are unable to be delivered. This queue was definitely not
there before I began the PF "move all replicas" process. So I've got the process apparently stuck, and a queue building up. What can I do to fix this? Thanks in advance :)

Hi Statick,
Few days ago even I faced the same problem when I migrated from 2003 to 2010.Long queue got built in my test mailboxes and all mails stuck and were not getting delivered. When I was
trying to resolve the issue, I found that server was not able to deliver because it was not able to route correctly. This problem "SmtpRelayToTiRg queue"
generally arises in public folders while moving all replicas.
So in order to fix this problem, I just added IP address of new Exchange server 2010 and complete queue vanished in few minutes.
I hope this will work for you.

Similar Messages

  • Public folders stuck in Mail queue when replicating to Exchange 2010

    This last weekend I installed Exchange 2010. Moved everyone over the same night to the new server. Mail flows in and out in ex 2010. The problem is I can't get the Public folders to replicate across. At the same time I found I can't send mail between the
    two exchange servers. In the message Queue on the Ex 2007 box I see the public folders are just sitting there waiting to be sent but stuck. Along with my test emails.
    I found an artical that talks about going into ADSIEdit and delete the old exchange 2003 empty server folder. Did that and email is still not flowing.
    Servers are in the same AD same subnet. ex 2007 is installed on a 2003 box. ex 2010 is on 2008r2.
    Thanks,
    Steve

    Hi vasdavidson,
    For this issue, I suggest you follow these steps to troubleshoot the problem:
    1.      
    Please paste the exact error you got in queue viewer.
    2.      
    On Exchange 2007, (use telnet) send emails to Exchange 2010, then check whether it can receive email or not.
    Thanks,
    Evan
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Exchange 2003 to 2010 Public folder Migration issue

    I have successfully replicated our Exchange 2003 public folders to our exchange 2010 public folders using the addreplica script in exchange 2010 PS. I have moved all mailboxes to use the public folders on Exchange 2010.  A couple of days ago I ran the
    "moveallreplicas.ps1", and the command successfully ran and has removed all replica pointers in the exchange 2010 PF database pointing to the exchange 2003 database. In Exchange 2003 ESM, I still have the replication to all the PF databases, and
    the 2k3 has not been removed, nor has the public folder instances folder count changed at all. In searching through the logs I am getting this error on the exchange 2003 event viewer for applications about every minute or less. 
    This is an SMTP protocol log for virtual server ID 1, connection #58254. The client at "xxx.xxx.xxx.xxx" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first  ". The full command
    sent was "xexch50 1076 2".  This will probably cause the connection to fail. 
    The client IP indicated in the error is a Exchange 2010 server with the HUB/CAS roles loaded onto it. I am not sure if this is related or not.
    I see some people have ran the move all replicas from the Exchange 2003 ESM, should I do that now? Is this even something to worry about since all my mailboxes are using the PF on 2010?
    Thanks for any assistance!

    I have looked at KB http://support.microsoft.com/?id=843106 and
    it did not resolve the issue on the Exchange 2003 server or 2010. 
    Last night I put in the fix for the Event ID 36885, method three of this article http://support.microsoft.com/kb/933430/en-us,
    and the errors on both servers seemed to go away, but then have started back up this morning after about seven hours of no errors. I thought the registry entry would fix the issue, and it appears it did, but not sure why it would come back like this. I may
    try restarting the servers tonight, but kind of confused how this could still be an issue with the registry entry in place. 

  • Migrate Exchange 2010 public folders cross forests

    Hi,
    Due to some Exchange and Active Directory issues (with remnants of old Ex 2003 server), we are going to migrate Exchange 2010 Mailboxes and public folders to a new Exchange 2010 Sp3 server, which is created in a new AD forest.
    One thing we still have to decide, which is how to migrate public folders.
    Apparently there are 2 ways:
    1. To export PF data to PST and then import using Outlook in destination Exchange server
    2. To use interorg replication tool to replicate PFs cross forest in target Exchange Server.
    I would really appreciate if someone suggests which one is best. We have around 100GB of PF data.
    Also, should we migrate Public Folders first? We think that we should move Mailboxes first.
    Thanks in anticipation.
    Regards, David Johnson

    Hi,
    Yes, when we decide to migrate from one Exchange server to another server, we need to move mailbox first.
    About migrating public folders, both of these two solutions are available, I think that the first one is simpler.
    Here is a similar thread for your reference.
    http://social.technet.microsoft.com/Forums/exchange/en-US/e3a23acd-efd2-4e51-bf4d-cb94b4b88a9f/exchange-2010-public-folder-cross-forest-replication-tool?forum=exchange2010
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2003 to Exchange 2010 Public Folders

    Hi Gurus, I’m in the process of moving public folders from Exch03 to Exch2010 and I have some clarifications before I proceed with this task. As I have understood the replication process between public folders working in a multi-master environment, I still
    need some deep understanding. Okay, the task is to ensure that we don’t lose any PF when I remove the last Exch03 where there’s a lot of PF residing. From my understanding, these PFs found at Exch03 are only replicas from Exch2010. From testing I can verify
    that the Outlook clients are looking at Exch2010. The way I tested this is by creating a test PF from Outlook and it did reflected on Exch2010 PF. Looking Exch03 for a couple of days, the test PF never reflected there so I'm just just assuming that there's
    no replication happening between Exch2010 and Exch2010.
    Please verify on this. Does it mean that Exch2010 is not replicating to Exch03?
    If yes, if I remove the PFs from Exch2003 without moving the replicas first to Exch2010, like plainly removing them for decommission, will that delete/remove the PFs on Exch2010?
    I have a feeling that it don’t because the PFs I’m creating/deleting at Exch03 are all replicas and I don't see any of the PFs that I deleted at Exch03 to also get deleted at Exch2010. More likely the PFs I'm creating at Exch2010 are not replication across
    to Exch03 and therefore removing these PFs at Exch03 should not affect the PFs at Exch2010.
    Please confirm on this before I proceed.
    Note that I've already taken copy of these Exchange servers because these are all VMs.
    Thanks....

    Hi,
    When you add Exchange 2010 to the replica list on Exchange 2003 server, it will replicate the Exchange 2003 Public Folder hierarchy and content to Exchange 2010, not from Exchange 2010 to Exchange 2003.
    You can remove public folders on Exchange 2003 without affecting the public folders which have been replicated to Exchange 2010.
    Before you decide to remove Exchange 2003 server, I recommend you put the Exchange 2003 server offline temporarily to check if Exchange 2010 works well.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 Public Folders Cannot Change Permissions Errors from Management Console and Powershell

    This problem does not affect new public folders, only old ones that have probably been on Exchange 2000/2003 servers in the past. Migrations I believe did go smoothly but now have errors.
    Error Reported is:
    Microsoft Exchange Error
    The following error(s) occurred while saving changes:
    Add-PublicFolderClientPermission
    Failed
    Error:
    Failed to modify the MAPI.NET table property of the object "000000001A447390AA6611CD9BC800AA002FC45A030064004E9CC2F8DD46B5E1E4578DE6D8030000000278E90000" on server "FQDN.Server.Name". See inner exception for more information.
    MapiExceptionNonCanonicalACL: Unable to modify table. (hr=0x80004005, ec=2409)
    Diagnostic context:
        Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=218]
        Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=356][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropModifyACL [64]
        Lid: 17082   ROP Error: 0x969    
        Lid: 27745 
        Lid: 21921   StoreEc: 0x969    
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropModifyACL [64]
        Lid: 22086 
        Lid: 27128 
        Lid: 27232   StoreEc: 0x8004010F
        Lid: 27128 
        Lid: 27232   StoreEc: 0x8004010F
        Lid: 22086 
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x3D210102
        Lid: 19149   Error: 0x0
        Lid: 24509   Error: 0x0
        Lid: 31229   Error: 0x0
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 6671    StoreEc: 0x8004010F
        Lid: 24976 
        Lid: 24952 
        Lid: 25472 
        Lid: 7972    StoreEc: 0x969    
        Lid: 26532 
        Lid: 4920    StoreEc: 0x969    
        Lid: 5119    StoreEc: 0x969    
        Lid: 5247    StoreEc: 0x969    
        Lid: 17916   StoreEc: 0x969    
        Lid: 4814    StoreEc: 0x969    
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x969    
        Lid: 29150 
        Lid: 20446   StoreEc: 0x969    
    OK
    From ExFolders we get error "Exception: Object Reference not set to an instance of an object"
    Any thought on how to fix permissions, people who already had permission in the past can see and access them OK and all objects, but we cannot change/update or remove permissons
    We alos receive similar error from the powershell.

    Hi,
    Could
    you please  add a new public folder hierarchies with ADSIEdit as following setups.
    For how to use ADSIEdit ,you can access:
    http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx
    1.Run ADSIEdit, right click Exchange Administrative Group under “Configuration \ services \ Microsoft
    Exchange \ Organization name \ Administrative groups”.
    2.Select New Object.
    3.Select msExchPublicFolderTreeContainer for the class and click Next.
    4.Enter the following for the value:
    Folder Hierarchies, click Next.
    5.Click Finish.
    6.Create
    Public Folder Tree Object.
    7.Right click CN=Folder Hierarchies -> New Object.
    8.Selected msExchPFTree for the class.
    9.For the value we entered, "Public Folders" and clicked next.
    10.Clicked on the "More Attributes" button, selected msExchPFTreeType .
    11.Set the value
    to 1.
     Note: This is very important that this value is set
    to a value of 1 as This tells Exchange that this is a MAPI Tree.
    12.Click Ok and then finish.
    13.We then went
    to the properties of the newly created "Public Folders" Tree object in
    ADSIEdit.
    14.Copy the distinguished name value
    to the clipboard and then click cancel.
    15.Navigate
    to the Storage group that contains the Public
    Folder Store for this server and get properties of the server.
    16.Locate the msExchOwningPFTree attribute and paste in the value that was copied
    from the Public folders Distinguish name attribute.
    17.Restart the Information Store Service.
    18.Mounted and dismount the PF store.
    19.Open Outlook with administrator,give full permission to default owner.
    Hope it can help you!

  • Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

    I currently have an Exchange 2010 server with all the roles installed.  Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error.  When I installed Exchange 2013, I got an error saying I
    had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left.  There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group.  This deletion caused my access
    to my public folders to get messed up.  I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA.  I also get this error when
    trying to access either Default or System Public Folders.  "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
    -server 'ExchangeServer' "
    My Public Folder Database exists and is mounted.  Any help is appreciated.

    Hi Belinda,
    Thank you for responding.  Yes you do understand my problem correctly.  One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA.  I followed these steps in the below article:
     http://blog.bruteforcetech.com/archives/766
    After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
    Here are the results to your requests:
    et-PublicFolder -Recurse | Format-List Name
    Name : IPM_SUBTREE
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    [PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
    Name : NON_IPM_SUBTREE
    Name : EFORMS REGISTRY
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
    CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

  • Exchange 2013 Mailbox Using 2010 Public Folders

    Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while.  Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company.  Our environment consists of
    8 Ex2010 servers and now the one Ex2013.  I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine.  How is that server discovered, and can we specify which one it uses?  I understand the way 2013
    public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

    Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
    You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
    http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
    Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
    between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

  • Merging existing 2013 Public Folders and 2010 Public Folders from different organization.

    Following recent acquisition of another company we faced the following situation:
    Company A has Exchange 2013 Organization up and running and already using new Public Folders migrated from 2010 when we upgraded.
    Company B has Exchange 2010 Organization with their own PF infrastructure.
    When it comes to migration, there's already public folder mailbox which was created when first migration occured.
    I cant figure next steps to merge those PF infrastructures at the moment, as removing public folder mailbox prior migration is not an option, since we already have big amount of data in 2013 Organization.
    Have anyone done similiar task and if so, how did you overcome this limitation?

    You're looking at a third-party product.  MigrationWiz does public folders.  There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Migrate Large Items in Public Folders - OnPremise

    Hi,
    we are currently in the progress of migrating more and more customers to Exchange 2013. Now there is a limit for large Items within public folders. We do know that we have large items and it is OK to wait for the replication to be done but how can we also
    migrate those large items?
    For instance within the public folder Migration-Request log we find:
    15.06.2014 22:28:37 [EXCHANGE] A large item was encountered: Item (IPM.Note) Subject:"MESSAGESUBJECT",
     Size: 22.69 MB (23,795,978 bytes), Folder:"PF Folder Name"
    Now I'm aware of the switch -LargeItemLimit but with that we will loose those large items. I haven't found any switch to enable the move of those large items - anyone an idea to also get those items moved to modern public folders?
    Thanks!
    Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

    Hi Peter,<o:p></o:p>
    <o:p> </o:p>
    As I know, if we have too many large items
    within the Public Folders being migrated, the migration may fail with error
    message like  “TooManyLargeItemsPermanentException”. If the large
    items can be copies without any issue, please just wait for the replication, I
    believe the replication will not take too much time(always be copied within
    10-15 minutes).<o:p></o:p>
    <o:p> </o:p>
    If we have too many large items that can’t
    be migrated, please try to set the migrated request attribute “LargeItemLimit”
    to 0(0 means it will not lost any large items). If issue persists, since it
    can’t replicate so much large items, we need to specify the “BadItemLimit”,
    “AcceptLargeDataLoss” “LargeItemLimit" attributes. So please first export
    the public folders that have large items to PST file(login Outlook with an
    account with access to all the public folders and export the public folders),
    then start a new migration request with the “BadItemLimit”, “AcceptLargeDataLoss”
    “LargeItemLimit" attributes, it will skip the large items. After that, we
    can export the PST file with contains the large item back to the public
    folders.<o:p></o:p>
    Regards, Eric Zou

  • Is there any option to see ms exchange 2010 public folders on my mail.app?

    Hi all,
    I wonder to know if it is possible to work with public folders with my mail.app. The corporate server is a Ms Exchange Server 2010 v14.02.
    Thanks in advance,

    Welcome to the Apple Support Communities
    Microsoft will launch Office for iOS next year, so you have to wait, Instead of Outlook, use Mail on the iPad

  • Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

    Dear All,
    I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
    For example: in exchange 2010 PF:   
    In exchange 2013
               \Public Folder\sales\A1_calendar
              --->
               \ Public Folder\sales\A2_calendar 
    ---> ?
                \Public Folder\sales\A3_calendar 
    --->  ?
                \Public Folder\sales\A4_calendar 
    ---> ?
    Thanks in advance.
    Regards,
    Willis Wong

    Hi Willis,
    This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Steve Fan
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Exchange 2010 public folder not showing on exchange 20003 mailbox

    Hi,
    I have public folder on exchange 2003 and separate public folder on exchange 2010. On exchange 2010 user mailbox, I can see both 2003 and 2010 public folders. On exchange 2003 user mailbox, I can only see 2003 public folders. It is not the permission issue
    as I have given the user "owner" right and see not able 2010 public folder inless i move 2003 user mailbox to 2010 exchange.
    Appreciate if anyone could help me if to point me to directions or any hotfix I can run?
    Thank you very much.
    Pwint

    Are you using OWA or Outlook to view the public folders?
    If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
    If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
    It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
    like authentication.

  • Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

    We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
    We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
    I see this in the outlook connection status in outlook:
    I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
    the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
    Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007  in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
    else that needs modified before decom?
    Thanks,
    Josh

    So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010. 
    I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
    What is the correct way to move the default public folders to a 2010 public folder?
    I'm using the below URL as a template to migrate this info to a 2010 PF db.
    https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
    "The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
    all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
    by entering the CD $ExScripts command,
    and execute the following script:
    AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\" 
    -ServerToAdd 2010MBX"
    My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
    Do I have to have public folders for free-busy and default exchange services at all in 2010?

  • Unable to open Public Folders in Outlook or OWA (Exchange 2010)

    Exchange 2010 Public folders can not be opened from Outlook or from OWA, in the ADIS I do not see Folder Hierarchies.  Under the public folder Management Console,i get an error that states "You cant perform this operation because public folder
    database isnt mounted.  Please mount it and try afain,  It wsas running the command ger-publicfolder -getchildren -identity "\"-server 'MBXserver'"

    Run "Get-PublicFolderDatabase" and see what it says the status of the database is.  This error implies that the database in offline.  You will also want to find the status of your public folder copies.
    Get-PublicFolder -Recurse | Ft
    or
    Get-PublicFolder -Recurse | Export-Csv PublicFolderStatus.csv -NoTypeInformation
    The first will work if you are checking a small number of folders, but you'll want the latter if you have many of them.

Maybe you are looking for