Need help: Exchange 2003 Public Folder migration to Office365

Been working on this Office365 migration for awhile and down to public folders migration. Its been a VERY difficult experience dealing with India techs, but I am almost done. Here are the details: Migrating from Exchange 2003 to Office365. All users have been migrated. Now we are left with the public folders and shared "Master Calendar". I have exported the public folders to a PST file and I now need to import to Office365. Google results on this topic are not clear to me. Can somebody please walk me through the best way to finish my migration? 
Hopefully we can finish the cutover before Friday so we can change the MX record before the weekend. 
This topic first appeared in the Spiceworks Community

Hi,
Please check if the links below are helpful:
http://technet.microsoft.com/en-us/library/bb331970(v=EXCHG.141).aspx
http://exchangeserverpro.com/migrate-public-folders-from-exchange-2003-to-exchange-server-2010/
Since this issue is more related to the Exchange side, I'd recommend you post your question to the Exchange forum:
http://social.technet.microsoft.com/Forums/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.

Similar Messages

  • Exchange Contact Public Folder Migration Question

    I am migrating our Exchange 2010 environment to Exchange 2013.  We are migrating all of our public folders into SharePoint before we continue with the migration.  Most of our public folders are calendars, so it has been a pretty cut and dry migration.
     We do have one public folder that is designated for emergency contacts.  It contains the personal contact information for the CEO as well as other high up execs and managers from around the company.
    Here is my dilemma.  I need to migrate this out of public folders, but it still needs to remain in Exchange somewhere.  I need to accomplish the following
    1. Be able to view all user contact info, not just email address
    2. Be able to apply permissions to the folder so that only certain individuals can gain access to these contacts
    3. Be available to sync with said user's mobile devices, so that they have 24X7 access to that information
    I am not real sure how to accomplish this and am open to any ideas.  I am very new to SharePoint, so not sure how you might be able to leverage SharePoint to do the same thing.  Any information that anybody could provide would be greatly appreciated.
    Thank you in advance,
    --Scott

    Hi Scott,
    Since this is Exchange Server Forum, if you have any problem on SharePoint, I suggest ask SharePoint Forum for help so that you can get more professional suggestions. For your convenience:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=sharepoint
    Here is some information related to Exchange for your reference.
    Based on my knowledge, Exchange 2013 is different from previous version of Exchange server. For example, public folder. Public folder in Exchange 2013 doesn’t based on public folder database, it is a mailbox level, called public folder mailbox.
    We can follow following article to perform the public folder migration.
    Use serial migration to migrate public folders to Exchange 2013 from previous versions
    https://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    Thanks
    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]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 Public Folder Migration Not Listed

    I started a public folder migration from my 2010 SP3 Exchange server to my new 2013 SP1 Exchange server. Somewhere during the process I failed. Not sure where but I am now at the point where if I try to create a new public folder on teh 2013 box i get a
    warning like this.
    An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch.
    So I then run Get-PublicFoldermIgrationRequest to see what is still waiting... I get no migration listed in Exchange Management Shell.
    I would like to find the place in AD or in the Server that thinks there is still an active request out there and remove it so I can start again with a clean slate. How do I do that?
    Thanks!

    Hi Zulea,
    This is a known issue, I recommend you refer to the following article to resolve the issue:
    http://support.microsoft.com/kb/3004062/en-us
    Cause:
    This problem occurs when the Exchange organization coexists with an earlier version of Exchange Server, and one or more public folder databases from the earlier version of Exchange still exist.
    Resolution:
    To resolve this issue, use one of the following methods.
    Method 1: Create the mailbox by using the -HoldForMigration switch:
    This option lets an administrator create a public folder mailbox in order to begin a migration from the existing public folders:
    Open the Exchange Management Shell.
    Run the following cmdlet to create the public folder mailbox:
    New-Mailbox "Public Folder Mailbox" -PublicFolder -HoldForMigration
    Method 2: Remove all public folder databases from earlier versions of Exchange Server
    To remove existing public folder databases, see the following TechNet websites, as appropriate for the version of Exchange that an existing public folder resides on.
    Exchange 2010:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
          (http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx)    
    Exchange 2007:
    http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx
          (http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx)    
    Create the public folder mailbox by using either the Exchange Admin Center (EAC) or the Exchange Management Shell (EMS). To do this, see the following TechNet website:
    http://technet.microsoft.com/en-us/library/jj552410(v=exchg.150).aspx
    Best regards,
    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]
    Niko Cheng
    TechNet Community Support

  • EXCHANGE 2013 Public Folder Migration across Domain Forest

    Hi
    I am planning to migration public folder across the forest but unable find any documentation. can you guys share the step by step guide to move/migrate public folder. we have exchange 2013 in source and target forest.   
    Please help!

    Hi,
    Currently, there is no official document about Exchange 2013 cross-forest public folder migration. Maybe some third party software can help you to do cross forest public folder migration.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Public Folder Migration Problem

    Hi All,
    Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
    I have followed the guide for public folder migration here
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
    We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
    However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them
    fine from the ECP - just not from outlook.
    It also appears some users cannot see some folders that they have permissions to.
    Can anyone assist with some ideas to resolve ?
    Thanks.

    Question?
    Are you able to create the Folder in OWA?
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:
       LinkedIn:
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
    it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
    My Bad, that's what I was trying to say.
    Testing the same thing in the LAB, should have some update tomorrow morning.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2003 Public folder move to exchange2010

    we have been running exchange 2010 and exchange 2003 for some time and now its time to remove exchange 2003 while its been running it hasn't been doing anything.
    Exchange 2003 is replicating already to exchange 2010 a while ago I did do a move replication (over a 2 months ago got side tracked)
    now under public folder instance on exchnge2003
    I just see one folder "Schedule + free Busy information -First Administrative Group"
    and when you look at replication status on exchange 2003 I see this
    PUBLIC FOLDER HIERARCHY                   12/08/2014 2 In Sync
    Schedule+ Free Busy Information- first                      2 both Modified
    System Configuration                             10/08/2012 2 local modified
    I need to get the information over to exchange 2010.
    Do I go with a move MoveAllReplicas.ps1 will this overwrite whats on 2010 ?
    What is the safest way for me to get this information over to exchange 2010 any suggestions?
    Thanks for your time

    Hi,
    Please check if the links below are helpful:
    http://technet.microsoft.com/en-us/library/bb331970(v=EXCHG.141).aspx
    http://exchangeserverpro.com/migrate-public-folders-from-exchange-2003-to-exchange-server-2010/
    Since this issue is more related to the Exchange side, I'd recommend you post your question to the Exchange forum:
    http://social.technet.microsoft.com/Forums/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.

  • 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 2003 Public folders and OAB to Office365?

    Hi guys,
    I am trying to migrate exchange 2003 public folders to office 365. I have read various documentation however they were either out of date or half-solutions.
    The company stored OAB's in each public folder as well, how do I go about migrating these lists into office 365? Will it just "work" if I migrate the public folders across?
    Thanks,
    Alex

    Hi,
    If you are migrating from inhouse 2003 to office 365, then the best options for you are-
    1. Either you can go for the manaul process. You can create PST files and can upload them to mailboxes through office 365 account.
    Kindly refer the below mentioned link for the same 
    http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx 
    2. Or you can go for any 3rd party tool using the same you can migrate your public folders to office 365. This is required when you need to avoid the risks associated and need to keep your environment up and running even while migration process. Respond
    back for third party tool suggestions.

  • Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations

    I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months.  I have followed every link I can find on how to do the migration properly.  It will stay in a queued state for hours until the MRS is
    restarted.  It will then start copying messages.  After reaching 28% I get RelinquishedWlmStall as Status Detail.  Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)
    Status                           : InProgress
    FailureTimestamp                 :
    IsValid                          : True
    ValidationMessage                :
    OrganizationId                   :
    RequestGuid                      : ff4af794-f31e-4334-959f-7d6c4ccbe310
    RequestQueue                     : PublicFolders
    ExchangeGuid                     : b12c1f83-c4ae-46bb-a26a-0422d90800e4
    Identity                         : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
    DiagnosticInfo                   :
    Report                           
                                       4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
                                       4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
                                       00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                       4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
                                       10.
                                       4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
                                       folders total.
                                       4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
                                       mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                       4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
                                       'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
                                       00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
                                       98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
                                       manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
                                       with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                       3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
                                       can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                       migration completes.
                                       4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
                                       with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                       3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
                                       can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                       migration completes.
                                       4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       '96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
                                       00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
                                       03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
                                       by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       '82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
                                       0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
                                       5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
                                       manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
                                       'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
                                       4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
                                       complete: 15.
                                       4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
                                       processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                       4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
                                       processed.
                                       4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
                                       4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
                                       items loaded. Total size: 149 MB (156,253,810 bytes).
                                       4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
                                       4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
                                       bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                       4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
                                       4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
                                       (7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                       4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
                                       unfavorable server health or budget limitations.
    ItemsTransferred                 : 3660
    PercentComplete                  : 25
    4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
    unfavorable server health or budget limitations.
    It never tries to restart.  Can anyone please help?  The server checks for health all come back ok.   I will be more than glad to include further information.  

    Hi,
    Basic on the error message, I notice that public folder migrate slow and display that “Relinquishing job because of large delays due to unfavorable server health or budget limitations” .
    If I misunderstand your concern, please do not hesitate to let me know.
    Since it is just slow and not failing, please do not stop the batch, it might connect to another server for sync.
    Meanwhile, please refer to below link so that get details about Exchange Online migration performance and best practices:
    https://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
    If the issue persists, please collect the relevant migration report for further troubleshooting.
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Exchange 2010 to 2013 Public Folder Migration -- Token Serialization

    Here is the log entry,Failed to save admin audit log for this cmdlet invocation. Organization: First Organization Log content:Cmdlet Name: New-PublicFolderMigrationRequestObject Modified: f0daff33-6a93-4367-b609-662cfa0b92de\71fc0595-b5d7-4f15-8b7c-bffcefbd810fParameter: SourceDatabase = Public Folder Database Parameter: CSVData = VGFyZ2V0TWFpbGJveCxGb2xkZXJQYXRoDQpDb2JvY28gUEYsXA0KQ29ib2NvIFBGLFxJUE1fU1VCVFJFRVxBcg==...Caller: ExternalAccess: FalseSucceeded: TrueRun Date: 2015-07-07T12:41:45OriginatingServer: (15.00.0995.012)Error:Microsoft.Exchange.Data.ApplicationLogic.AuditLogAccessDeniedException: The requesting account doesn't have permission to access the audit log. --- System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. at...

    Hey Guys!
    I'm in the process of testing a Public Folder migration from Exchange 2010 to 2013, I've been following the recommened migration scenario from Microsoft but have ran into this issue when running New-PublicFolderMigrationRequest. I let the request sit at a queued status for over 6 hours and then decided to look at the event logs. I'm receiving an access denied, requesting account does not have permission to serialize tokens.
    Luckily this is just a test and not in a production environment :-)
    Any suggestion or help to point me in the right direction would be appreciated
    Thanks Guys
    This topic first appeared in the Spiceworks Community

  • Exchange Public Folder Migration - Public Folder Mailbox "LockedforMigration"

    I've recently started a SBS2008 (Exchange 2007 - Latest SP3) migration to Exchange 2013CU6.  
    Most of the Migration has gone to plan however I've been following a few guides on the Public Folder migration and have seen more errors and time spent than what it is worth.
    I've now decided to abandon the Public folder migration as there wasn't really anything of importance in the old 2007 Public Folders, and just setup a new Public Folder Mailbox and PF Folder on the 2013 environment, however... as I started with the migration
    the 2013 Server is stuck in "LockedforMigration" mode and will not allow me to create a new Public Folder.
    Is there anyway to forcibly 'unstuck/release' the "LockedforMigration = True value. 
    Or can I just start decommissioning the old 2007 Box and that will force the unlocking of Migration flag
    By no means is this the only guide, but here is what I've been following if that will help
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Thanks Ian

    Hi Ian,
    According to the error message above, please make sure you are running the command as Administrator, and make sure the Administrator is a member of Organization Management Group and Server Management Group. Then try to run command to release "LockedforMigration
    $True".
    Since Public Folders on Exchange server 2013 can't be coexisted with legacy Public Folders within an Org, you should delete Public Folder Database from legacy Exchange server 2007 first, then create a new Public Folder Mailbox on Exchange server 2013.
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 - 2013 Public Folder Migration target database gets much bigger than source database

    Hi,
    i have a question about the pf migration from Exchange 2010 to Exchange 2013. The source database ist about 370 GB. The migration process is still running. At the moment the target database is already 491GB big. Is that a normal behaviour during the migration
    process.
    Thanks

    Hi,
    After you have finished the public folder migration process, you can compare the item count of public folders to make sure all public folders have been moved to Exchange 2013.
    You can check this by comparing the snapshots before and after the migration. You can refer to the "How do I know this worked?" section in the following article.
    Migrate Public Folders to Exchange 2013 From Previous Versions
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Namespace for Exchange 2003 == 2010 == 2013 Migration

    Hi
    Hope someone can help.  I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use.  I am aware that if I do not do this right at the 2003
    to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
    Some background:
    2003 Functional Level Domain - 2 x 2008 DC's
    Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
    We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
    We have two Kemp load balancers ready for Exchange 2013.
    Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
    Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
    Our main website etc is www.company.com
    Our public facing services are at https://service.mycompany.com
    Our 2003 RPC address is https://webmail.mycompany.com
    I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
    Two Questions:
    Do we have to use the HTTPS same namespace for 2013 as we do in 2010?  Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
    https://mail.mycompany.com would allow a migration, rather then a cutover.
    Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com?  Can autodiscover still work?
    Thanks in advance for any guidance
    Cheers
    Steve

    1. No, but you can.  Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
    2.  Your web services can be published with any domain as long as the hostname is in the certificate.  Only Autodiscover needs to match the e-mail domain(s).  So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
    at owa.mycompany.com.  You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com.  If all users have a company.com e-mail address,
    the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices.  If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
    instead because it can greatly simplify your certificate requirements.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • 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.

  • 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

Maybe you are looking for