Exchange 2007 - Public Folder Access

Hello,
i have a little problem. I'm using my iPhone in my company like some other guys here. I want to synchronize the Exchange Public Folders through the iPhone. I already know thats not possible in a direct way. Does anyone know a good Tool to synchronize Folders in Exchange? I found some Tools, but only Add-Ins, no standalone applications which work without Outlook and completely alone. I'm searching for some kind of tool which runs in a process on a webserver.
MfG KeRn

I know this is an issue, Microsoft are so backwards in their way of thinking.....Most companies use public folders in one way or another.
I have a Kerio Mail Server it's identical to Exchange but better and more stable and costs a fraction of the price, they released a version of their software by accident that synced and supported public folders to my iPhone, they removed it in the next update, I have contacted them on this issue and they say that they are working on solving this problem and it is due to a bug in the syncing process. So I am waiting with anticipation for them to release it very soon, so up that Microsoft!!!!!! Get with the real world!!

Similar Messages

  • Exchange 2007 Public Folder Database cannot be deleted

    We are in the process of decommissioning exchange 2007 server from 2007 <-> 2013 coexistence.
    All user MailboxDatabases have been sucsessfully removed, however PF Mailbox databases return an error. 
    “The public folder database 'Public Folder Database' cannot be deleted”
    Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (8.0.535.0).
    I am suspecting the presence for 2 OAB is the reason why we can’t delete Public folder database from 2007 server.
    Get-OfflineAddressBook on 2007 returns
    Name               
    Server             
    Versions           
    AddressLists
    Default Offline ... ex07                
    {Version4}         
    {\Default Global...
    Default Offline ... Offline Address ... {Version4}         
    {\Default Global...
    Get-OfflineAddressBook on 2013 returns
    Name                                   
    Versions                               
    AddressLists
    Default Offline Address Book           
    {Version4}                             
    {\Default Global Address List}
    Default Offline Address Book (Ex2012)  
    {Version4}                             
    {\Default Global Address List}
    Questions:
    How can I check if both exchange servers are still OAB generation servers?
    I am not sure if the previous service provider moved OAB,  can I potentially cause any problems by executing  
    Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
    Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server EX13
      3. Is it safe to delete 2007 OAB ?
    Thanks

    Default and System public folders show up under PF Management Console, however their preview pane on the right says "There are no items to show in this view" for both of them.
    below is the output from Get-PublicFolderStatistics on ex07
    Name                                     ItemCount              
    LastAccessTime
    Marketing                                   479              
    1/4/2014 10:15:14 AM
    Default                                  0                
    3/16/2014 1:34:35 PM
    EX:/o=First Organization/ou=Exchange Adm 2                 3/13/2014 1:00:00 AM
    inistrative Group (FYDIBOHF23SPDLT)
    EX:/o=First Organization/ou=Exchange Adm 0                 3/13/2014 1:00:00 AM
    inistrative Group (FYDIBOHF23SPDLT)
    exchangeV1                               401              
    3/16/2014 1:34:35 PM
    globalevents                             0                
    3/16/2014 1:34:35 PM
    internal                                 0                
    3/16/2014 1:34:35 PM
    Sales                                     713              
    1/4/2014 10:15:15 AM
    microsoft                                0                
    3/16/2014 1:34:35 PM
    OAB Version 2                            0                 
    1/4/2014 4:09:49 AM
    OAB Version 3a                           0                 
    1/4/2014 4:09:49 AM
    OAB Version 4                            0                 
    1/4/2014 4:09:49 AM
    OWAScratchPad{8382AFC4-6D63-4804-AC49-7B 0                 3/16/2014 1:34:35 PM
    4FDA2A4514}
    schema-root                              0                
    3/16/2014 1:34:35 PM
    Accounting                                 953              
    1/4/2014 10:15:16 AM
    StoreEvents{8382AFC4-6D63-4804-AC49-7B4F 0                 3/16/2014 1:34:35 PM
    DA2A4514}
    /o=First Organization/cn=addrlists/cn=oa 0                 3/13/2014 1:00:00 AM
    bs/cn=Default Offline Address Book

  • Syncronizing a Exchange 2007 Public folder to SP 2010 Caledar

    Greetings
    I am running Share Point 2010 Enterprise and Exchange 2007.  We have a large amount of Public Folders that we need to migrate to Share Point.  I was wondering if there is a way to do this without having to buy any extra software.  I have researched
    some and all that I have read is that you can use a the Outlook sync button to link the calendar to Outlook which I am fine with.  All our workstations are using Outlook 2010.  But I have read that if you copy the appointments from one calendar to
    this SP linked calendar all appointments will sync from that point on, which is incorrect.  Moreover, when I select list view to copy the appointments over and then open appoints in calendar view none of the appointments show I am assuming
    that this is a permissions issue.  So I guess I am asking two questions here.  1) what is the best way to migrate Exchange Public Folders into SharePoint?  And why are the appointments that I copy over from the public folder are not showing
    up when I change the view back to calendar view in Outlook.  I really appreciate you time for reading my post.  Thanks in advance.

    Hi,
    According to your post, my understanding is that you wanted to migrate the exchange public folders to SharePoint 2010 calendar.
    If you hava a small number public folders, you can migrate the public folders manully.
    Here is an article which about migrate public folders to SharePoint manully(although it’s about SharePoint 2007, I think it’s helpful for you).
    http://www.messageops.com/manually-migrating-public-folder-content-to-sharepoint-online
    If you have a large number of Public Folders it would be recommended that you take a look at 3rd Party Migration Tools,
    such as the Quest or AvePoint products:
    http://www.quest.com/public-folder-migrator-for-sharepoint/
    http://www.avepoint.com/exchange-public-folder-to-sharepoint-migration-docave/
    More reference:
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/planning-architecture/using-sharepoint-provide-public-folder-functionality.html
    Thanks,
    Jason
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Jason Guo
    TechNet Community Support

  • Migrating Exchange 2007 Public folder to SharePoint 2010

    Hello,
    I have an exchange 2007 SP3 Rollup 11 that hosts public folders, I need to migrate these folders to maintain the hierarchy and folders permissions to MS Sharepoint 2010.
    Is there is any tool that could assist me in this migrations, or any article that leads me through this migration.
    please advise.
    BR
    Ahmed Salah
    BR Ahmed Aboutabl

    Hi
    Maybe this helps:
    http://www.tzunami.com/products/td-exchange-migration/
    Hope this helps. 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 2013 Public Folder Accessability Issues

    After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders.  Issues range from a hung server requests to on-screen errors like this one:
    “Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
    We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
    ./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
    The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
    Ideas?

    Hi Niko,
    Firstly, apologies for the delayed update...
    We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
    I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation.  While migrating from Exchange 2010
    to Exchange 2013 we did follow the migration process.
    Here is what our current settings from Get-OutlookAnywhere -Server %Server%
    RunspaceId                         : e2e4f324…
    ServerName                        
    : %server%
    SSLOffloading                     
    : True
    ExternalHostname                  
    : <set>
    InternalHostname                   : <set>
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods          
    : {Basic, Ntlm, Negotiate}
    XropUrl                           
    ExternalClientsRequireSsl         
    : True
    InternalClientsRequireSsl         
    : True
    MetabasePath              
            : IIS://%server%/W3SVC/1/ROOT/Rpc
    Path                              
    : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags           
    ExtendedProtectionSPNList         
    AdminDisplayVersion               
    : Version 15.0 (Build 775.38)
    Server                             : %server%
    AdminDisplayName             
    ExchangeVersion                   
    : 0.20 (15.0.0.0)
    Name                              
    : Rpc (Default Web Site)
    DistinguishedName                 
    : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                        Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
    Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
    Identity                           : %server%\Rpc (Default Web Site)
    Guid                              
    : 0bf08d0e…
    ObjectCategory                    
    : %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                       
    : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                       
    : 5/5/2014 3:08:31 PM
    WhenCreated                       
    : 2/20/2014 2:13:17 PM
    WhenChangedUTC                    
    : 5/5/2014 8:08:31 PM
    WhenCreatedUTC                    
    : 2/20/2014 8:13:17 PM
    OrganizationId                    
    OriginatingServer                 
    : %server%
    IsValid                           
    : True
    ObjectState                       
    : Changed

  • How to view Exchange 2007 Public folders, calender on iphone

    How to view Exchange 2007 public folders mainly the calenders on the iphone?

    Not possible.
    Sent from my iPad.

  • Exchange 2010 - Public Folder Managment

    I seem to have hit a bit of a stale mate with our exchange 2010 public folder management and while i think i see things set up wrongly - i'm not sure how to fix or what the consequences are if i did (and since i haven't yet built a sandbox test environment) i thought i would ask the spiceworks community for some helps and tips.So a little back ground first :two physical locations - one UK one USStretch DAGS with US-MBX replicating to UK-CAS and UK-MBX replicating to US-CASALL servers on the same domainProblem i am trying to resolve :One of our users based here in the UK travels to and manages some US staff now. US staff put holidays into a calendar in a public folder. The UK based manager would like to see this calendar.Sounds easy right? (maybe it is and i just need a clip around the napper with the manual).When i look at the public...
    This topic first appeared in the Spiceworks Community

    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 2013 user cann't access exchange 2013 public folder

    Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
    problem, thanks.
    belows are information about outlook anywhere in our exchange.
    exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
    exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
    Identity                           : SHCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHCAS02\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : WXCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL04\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}

    Hi,
    I have found an article said that we need to set the external host name the same. See more details in the following link:
    http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
    To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
    Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
    The following configuration is set on each Exchange 2007 server:
    The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
    Sent By
    Silver

  • Public Folder access on Exch 2007 from exch 2013 user

    I have an issue with my test user that I migrated from 2007 to exch 2013 being able to access public folders that reside on the 2007 server. 2007 users accessing public folders on 2007 have no issues. I have it narrowed down to autodiscover. Please see the
    below exerpt from autodiscover. The "<PublicFolderServer>ex2013.accessDOMAIN.net</PublicFolderServer>" section shows that autodiscover is giving the name of the exchange 2013 server as the publicfolderserver
    instead of the exchange 2007 server.  My question is how do I reflect the correct server "Exch2007" on this autodiscover output?
    <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <MicrosoftOnline>False</MicrosoftOnline>
          <Protocol>
            <Type>EXCH</Type>
            <Server>[email protected]</Server>
            <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
            <ServerVersion>73C0834F</ServerVersion>
            <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
            <PublicFolderServer>ex2013.accessDOMAIN.net</PublicFolderServer>
            <AD>DC.domain.local</AD>
            <ASUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</ASUrl>
            <EwsUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</EwsUrl>
            <EmwsUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</EmwsUrl>
            <EcpUrl>https://ex2013.accessDOMAIN.net/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.local</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=domain.local</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-photo>
            <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-tm>
            <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-tmCreating>
            <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-tmEditing>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.local</EcpUrl-extinstall>
            <OOFUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</OOFUrl>
            <UMUrl>https://ex2013.accessDOMAIN.net/EWS/UM2007Legacy.asmx</UMUrl>
            <ServerExclusiveConnect>off</ServerExclusiveConnect>
          </Protocol>

    Thank you for your time. I verified that the build number on outlook is greater than SP1. This would indicate that the hotfix was applied as it was included in cumulative rollups.
    The output from the geet-outlookanywhere command is found below. I have adjusted the auth to basic as that is where I would like it to be.
    [PS] C:\Windows\system32>Get-Outlookanywhere | fl Identity,*auth*,*hostname,*ssl
    Identity                           : Exch07\Rpc (Default Web Site)
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    ExternalHostname                   : legacymail.DOMAIN.net
    InternalHostname                   : legacymail.DOMAIN.net
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    Identity                           : Exch13\Rpc (Default Web Site)
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ExternalHostname                   : webmail.DOMAIN.net
    InternalHostname                   : webmail.DOMAIN.net
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True

  • Exchange 2013 - Public folder search not working

    Hi There,
    We have Exchange 2013 install on server 2012 and clients using Outlook 2010 on Windows 7.
    Since we have installed the system a search of the public folders always returns no results even if we know the email is there. Any suggestions?
    Thank you
    Dave

    Hi Triumphtech,
    Yes, if our Exchange 2003 environment is healthy, it will work.
    Please forgive me for the silly clarification. If we used Exchange 2003 and wanted to migrate to Exchange 2013. We must migrate to Exchange 2007/2010 first, then to Exchange 2013.
    So please make sure we have moved the public folder successfully first.
    And great information from Tarique Noorain.
    According to  the article, I found some points for your reference:
    1. Although a full text search of public folder content is available, public folder content isn't searchable across public folders and the content isn't indexed by Exchange Search.
    2. You must use Outlook 2007 or later to access public folders on Exchange 2013 servers.
    Feel free to contact me if there is any problem.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 to Exchange 2013 Public Folder Problem

    Dear Experts,
    I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
    1) Parent Domain in Site A (abc.com)
    2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
    3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
    I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
    Anyone help will be highly appreciated.
    Thanks & Regards,
    ZB

    so you want users to access the PF in site B.
    Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
    run this for Exchanger 2013 DA
    Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
    Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
    Where Technology Meets Talent

  • Exchange 2010 Public folder database size grown upto 1.22TB

    I have situation to discuss , have three exchange public folder server with 2010Ent edt. One of Pub folder dtabase has been reached 1.22TB . Problem is that we cant increase more storage as its reached over limit. We are unable to do backup as its need to
    split in multiple chunk . I cant do offline defrag as if now casue of LUNs limit.
    Do someone has such sitaution faced and have any recommendation is this ? I can do create a new PF database. More over I am looking some short of solution to split whole database in two part hosted by two PUB server and each database just do content replication
    with each hosting own database on each server.Will really appriciate for any good suggestion. I am open for all other possibilities.
    Saty

    I have executed whole project to move from 2010 to 20103. Public folder was a big pain. It was 3 copy of 1.32 TB. Plan started from implementation of Archiving tool for exchange.
    1- First level pulled all detail reports for PF name,size last access time ,update time ,type9 mail enable or normal.
    2- Pull the report and calculate the free white space with all calculation of individual server wise, and get the actual data size ,
    3- Target to one PF server holding passive copy of public folders (Not Master copy)
    4- Target the public folder keeping 0KB size and create script to delete in non recurs mode so only folders which has size 0 will be delete and rest all be left just like that .
    5- later target the folder size keeping huge data and foliter it out with root folder and check out the permission and reach out people if the really need the data .Get the sign off and delete it through recurs script.
    If you not put recurs delete it will never allow to delete whole folder in one way.
    6- Target folder which data are important and move them to shared mailbox . Using soem restore tool which can export pst of those folder and import into mailbox. Set the permission accordingly. And set Enterprise erchiving policy for that shared.Same above
    two exercise need to apply for all public folders.
    7- Target those folders which are in use and try to convince and move them to shared mailbox with unlimited mailbox size with EV archiving.
    8- And at the end move replica of target server to master copy.
    9- Once replica move is complete you can plan to delete the PF data edb file. It wont allow to delete directly as you have to go through ADSIEDIT method only.
    10- while same exercise need to do for all other passive copy.
    11- Create a fresh edb and now you can move pf replica content to new edb which will help to move actual data with very limited whitespace.
    12- And this way whole PF will be in actual size and all junk and unwanted files/data/emails/meetings etc will be removed.
    13- There will be one common issue of form created through outlook so you need to import them carefully using default system folder.

  • Exchange 2010 Public folder permission issue

    When i select the public folder and click the permission tab to set the permission, below error message will be pop up. This error message only happen in few sub public folder, another folder without this problem. There are two replica
    in different mail store server.
    Microsoft Corporation
    Microsoft® Windows® Operating System
    6.1.7600.16385
    Exception has been thrown by the target of an invocation.
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.ConstraintException: Column 'Identity' is constrained to be unique.  Value 'gcr.geg.local/Managed OU/Galaxy Corporate/HR&A/Esther
    Chan (Corp HR&A)' is already present.
       at System.Data.UniqueConstraint.CheckConstraint(DataRow row, DataRowAction action)
       at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
       at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Int32 position, Boolean fireEvent, Exception& deferredException)
       at System.Data.DataTable.InsertRow(DataRow row, Int64 proposedID, Int32 pos, Boolean fireEvent)
       at System.Data.DataRowCollection.Add(DataRow row)
       at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.AddEntry(DataTable table, ADObjectId identity, String name, MultiValuedProperty`1 accessRights)
       at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.GenerateClientPermissionDataSource(Object clientPermission)
       at lambda_method(ExecutionScope , String )
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Delegate.DynamicInvokeImpl(Object[] args)
       at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateLambdaExpression(ColumnExpression expression, Type dataType, DataRow dataRow, DataRow inputRow)
       at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateCore(DataRow dataRow, DataRow inputRow, IList`1 query)
       at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.FillColumnsBasedOnLambdaExpression(String changedColumn)
       at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.UpdateTable(DataRow row, String targetConfigObject, Boolean isOnReading)
       at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandler.OnReadData(CommandInteractionHandler interactionHandler, String pageName)
       at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.Read(CommandInteractionHandler interactionHandler, String pageName)
       at Microsoft.Exchange.Management.SystemManager.WinForms.DataContext.ReadData(CommandInteractionHandler interactionHandler, String pageName)
       at Microsoft.Exchange.Management.SystemManager.WinForms.ExchangePage.<OnSetActive>b__0(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Common, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.ActiveDS, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.TroubleshootingTool.Shared, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.RightsManagementServices.Core, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Transport, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Common.IL, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Sqm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Management.SnapIn.Esm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
    Microsoft.Exchange.Management.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35

    Hi,
    This issue appears to be related to
    data access from their ASp.Net application.
    To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft
    Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
    http://support.microsoft.com/contactus/?ws=support
    FIX: "Exception has been thrown by the target of an invocation"
    error message
    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 2010 Public Folder import .pst

    Hi
    I have Exchange 2010. I exported a public folder to pst-file and then deleted it. Because i could not uninstall our 2007 servers
    How do i import it again. When i do it in Outlook it says that Posts cannot be created on root level in the common information archive. Translated from Swedish.
    Anyone have a step by step solution for this.
    Best regards
    Matthias

    Hi,
    How did you import the pst-file? Please try to open the pst-file in Outlook and drag and drop all items in it to your Public Folder. See:
    http://www.rackspace.com/knowledge_center/article/migrating-public-folder-data
    Hope this helps.
    Best Regards,
    Steve Fan
    TechNet Community Support

  • Exchange 2010 public folder description property

    In Outlook, if you display the properties of a public folder, on the general page is a field called "description".
    In Exchange 2003 I waqs able to access this field using wmi and the microsoftexchangev2 object (comment field).  This object does not exist in Exchange2010.
    The description field does not appear in powershell commands get-publicfolder, get-mailpublicfolder or get-publicfolderstatistics.
    I have been able to find this field using ldap in the "microsoft exchange system objects" container in a field called info.
    Unfortunately, this field is not always populated.  Out of about 6000 folders that have the description field populated, the info field is only populated for about 800.
    So, my question is, is there a reliable place where the public folder description filed is accessible in exchange 2010?

    Hi,
    To manage public folders, we can use the Public Folder Management Console. But we can't use it to manage description field.
    Based on my knowledge, I'm afraid there is no built-in Exchange 2010 tool or cmdlet to get the description field of public folder.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

Maybe you are looking for

  • How do I share my iTunes Library

    Hi, I was wondering if anybody can tell me how to fully share my iTunes library with other accounts on the one mac. Recently my boyfriend got an iPod Shuffle and obviously wants to put music on it. He did used to have his own login so he could change

  • Add new line item in VA02 by copying same Order line details

    Hi All, I've a requirement where i need to add new line items in the Sales Order (T Code VA02) with reference to the same Order lines . For e.g an Order 80000100 which has 2 line items and the requirement is to create a new line i.e. line item 0030 b

  • Configuring IDSM in promiscuous mode?

    Hello, I have two switch catalyst 6500 in VSS each with a IDSM module, I want monitor four VLANs three of them are vlans of users and one of servers, I am planning use VACLs to capture the traffic. My first quetion is how to configure the data ports

  • Please help with query

    Hello, I'm trying to write a query which is of the form below: select (aa.name || bb.name) full_name from (select * from per_positions where name = 'Igwe') aa, (select * from per_positions where name = 'OSHS.Application.Specialist.Head Office') bb Th

  • USB error while system is loading

    Hi! when ArchLinux is loading shows this line: usb 3-1.1: string descriptor 0 read error: -22 What it means? Is there anything not working right? Thanks!