Exchange 2003 migrate to Exchange 2010 - single forest multiple domain. Active Sync problem

Hi All, 
I have AD single forest and multiple domain. for example, the forest domain is jakarta.co.id, and the other domain is bali.co.id.
Exchange 2003 deployed in jakarta.co.id, User mail enabled in domain jakarta.co.id and bali.co.id.
Then, I upgrade to Exchange 2010 (deploy in jakarta.co.id) and move mailbox from Exchange 2003 to Exchange 2010.
All users in bali.co.id are able to access email from Owa, BlackBerry (BIS), Outlook, but cannot access from Android, Windows Phone. (Active-Sync).
I got error information generated from https://testconnectivity.microsoft.com, as following:
Attempting the FolderSync command on the Exchange ActiveSync session.
The test of the FolderSync command failed.
Tell me more about this issue and how to resolve it
Additional Details
Exchange ActiveSync returned an HTTP 500 response (Internal Server Error).
Active-Sync still not work even I check option "Include inheritable permissions from this object" in security tab.
any idea to fix this issue?
Thanks.
Endrik
Endrik | blog: itendrik.wordpress.com 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.

Hi Sathish, 
We are planning to migrate Exchange 2003 to Exchange 2013, all user already in Exchange 2010 and Exchange 2003 was decommissioned
Event Viewer log as following:
Log Name:      Application
Source:        MSExchange ActiveSync
Date:          1/17/2014 10:00:48 PM
Event ID:      1008
Task Category: Requests
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EXC2010.jakarta.co.id
Description:
An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case,
Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. 
URL=/Microsoft-Server-ActiveSync/default.eas?Cmd=Sync&User=bali%5Csteveng&DeviceId=SAMSUNG123456789&DeviceType=SAMSUNGGTN7000
--- Exception start ---
Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
Exception message: A null value was received for the NTSD security descriptor of container CN=ExchangeActiveSyncDevices,CN=Steven Gerrard,OU=IT,DC=bali,DC=co,DC=id.
Exception level: 0
HttpStatusCode: 500
AirSyncStatusCode: 110
XmlResponse: 
This request does not contain a WBXML response.
Exception stack trace:    at Microsoft.Exchange.AirSync.ADDeviceManager.SetActiveSyncDeviceContainerPermissions(ActiveSyncDevices container)
   at Microsoft.Exchange.AirSync.ADDeviceManager.CreateActiveSyncDeviceContainer(Boolean retryIfFailed)
   at Microsoft.Exchange.AirSync.ADDeviceManager.CreateActiveSyncDevice(GlobalInfo globalInfo, ExDateTime syncStorageCreationTime, Boolean retryIfFailed)
   at Microsoft.Exchange.AirSync.ADDeviceManager.CreateActiveSyncDevice(GlobalInfo globalInfo, ExDateTime syncStorageCreationTime)
   at Microsoft.Exchange.AirSync.Command.UpdateADDevice(GlobalInfo globalInfo)
   at Microsoft.Exchange.AirSync.Command.CompleteDeviceAccessProcessing()
   at Microsoft.Exchange.AirSync.Command.WorkerThread()
--- Exception end ---.
I think KB817379 is not related because Exchange 2003 was decommissioned.
Regards, 
Endrik
Endrik | blog: itendrik.wordpress.com 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.

Similar Messages

  • Understanding Lync 2013 Deployment for Single forest multiple domain Infrastructure

    Hello Everyone,
    I have an issue in understanding a deployment scenario of Lync 2013 Enterprise edition.
    We have a single forest multiple domain infra. 
    My My question here is, while AD prep, do we need to run Domainprep on every domain in the forest. 
    Thanks!
    Thank You!!! BR, Ammi.

    Hi Ammi,
    To prepare Active Directory Domain Services for your Lync Server 2013 deployment, you must perform three steps in a specific sequence.
    1.
     Preparing the Active Directory schema in Lync Server 2013
    Extends the Active Directory schema by adding new classes and attributes that are used by Lync Server.
    Run once for each forest in your deployment where Lync Server will be deployed.
    2. Preparing the forest for Lync Server 2013
    Creates global settings and universal groups that are used by Lync Server.
    Run once for each forest in your deployment where Lync Server will be deployed.
    3. Preparing domains for Lync Server 2013
    Adds permissions on objects to be used by members of universal groups.
    Run once per user domain or server domain.
    Hope it can be helpful.
    Best regards,
    Eric

  • SCCM 2012 AD Publishing in a Single Forest Multiple Domains

    Hi there,
    Let me explain the situation first so that you get the idea. We have a single forest, multiple child domains AD environment. For some reasons each domain is being managed separately by their geographic location IT.
    Forest has been extended for SCCM by the site who holds the forest root domain. Since everyone wants to manage their own domain and systems, each child domain have their own primary site server.
    In one of the domains I have installed brand new SCCM 2012 R2. I haven't done anything yet, havent turned on any discovery except Heartbeat. Now I see one device, which belongs to another domain with totally separate IP address, shows in my SCCM site. I dont
    know why.
    From here question arises for me. Correct me if I'm wrong and please advice what to do domain/forest wide.
    1. System Container is needed in each child domain, not in the forest, right?
    2. Where does/should each SCCM primary site publish information; in each domain or in the forest root domain?
    3. Under Administration > Overview > Site Configuration > Sites > Properties > Publishing I see forest root domain name and its checked. 
    Under Administration > Overview > Hierarchy Configuration > Active Directory Forests > Properties > Publishing my site is checked and its the only one in there. In that same window I went ahead and specified my own domain hoping
    to cure the possible problem.
    So, why would that one device show up in this site? I have disabled Heartbeat together with other discoveries for now till I make everything ready.
    Thanks for your help in advance.

    1. Under Administration > Overview > Site Configuration > Sites > Properties > Publishing If I uncheck forest root domain will devices on my child domain still be able to find my site server?
    2. Under Administration > Overview > Hierarchy Configuration > Active Directory Forests > Properties > Publishing my site is checked and its the only one in there. In that same window I went ahead and specified my own domain
    hoping to cure the possible problem. Is this a good practice?
    3. "When clients look for ConfigMgr info, they use GC lookups meaning they return objects from every System Management container in the forest." So, which one do clients choose and how?
    4. "For that one device, have you opened its properties and examined it?" Yes, what abou it? Its found based on Heartbeat Discovery agent (when heartbeat was enabled).
    5. "Have you reviewed the boundaries and boundary groups set up for site assignment?" Yes, as I mentioned this device belongs to different domain and totally outside of my AD site and SCCM boundaries.
    This is fresh install and not in production yet. I have disabled Heartbeat temporarily so that I fix this problem. I will enable it after. 

  • Identity firewall with Single Forest/Multi-Domain

    I have a question with regard to setting up the ID firewall on the ASA 5585 in a single forest, multiple domain windows network.
    Currently I have a semi-operational IDF at the top level but can't find users on the lower other domains, here is the setup:
    I have 3 domains.
    domain1.test.com
    domain2.domain1.test.com
    domain3.domain2.domain1.test.com
    Both domains have a two way parent-child trust and I can look for users in AD Users/Computer on both domains.  I initially setup the ASA to look at domain1.test.com using an LDAP aaa-server per the IDF instructions, and then proceeded to configure the ad-agent.  I installed the adagent on the domain1.test.com domain controller configured the settings on that system and had no problem adding users to the firewall and getting functionality within domain1.  I looked to see if I could see domain 2 and domain 3 users and found none.  I went ahead and added the domain2 system to the adagent on the DC and the system says that it is up, but when I search for users is not pulling them from domain2.  Instead, it shows domain1 users as domain2\user1.  I also configured another adserver in the ASA to search ldap on domain 2 to no avail.
    The cisco documentation states the following:
    •Before you configure even a single domain controller machine using the adacfg dc create command, ensure that the AD Agent machine is first joined to a domain (for example, domain J) that has a trust relationship with each and every domain (for example, domain D[i]) that it will monitor for user authentications (through the domain controller machines that you will be configuring on the AD Agent machine).
    Single Forest, Multiple Domains—All the domains in a single forest already have an inherent two-way trust relationship with each other. Thus, the AD Agent must first be joined to one of the domains, J, in this forest, with this domain J not necessarily being identical to any of the domains D[i] corresponding to the domain controller machines. Because of the inherent trust relationship between domain J and each of the domains D[i], there is no need to explicitly configure any trust relationships.
    Reading that it sounds like it should just work.  I had everything properly configured before I installed the adagent, but I'm guessing that there is a chance that you can't have the adagent on the top level DC and get to communicate with the lower level domains.  I wanted to ask though before I blow everything up and start over.  The instructions are not overwhelming clear on what needs to done in this scenario.  Suggestions?

    Hi Matthew,
    If I understand your post correctly, the problem is that the ASA is unable to search users in domain2, correct? This portion of the communication is unrelated to the AD Agent, but it sounds like the Agent can talk to the DC just fine. The ASA searches for users directly on the DC via LDAP queries. The communication between the ASA and the Agent is all done via RADIUS.
    If the above is correct, I would focus on why the LDAP queries are failing between the ASA and the domain2 DC. Feel free to open a TAC case on this as well for additional assistance from the AAA experts.
    -Mike

  • Can't move Exchange 2003 mailbox to Exchange 2010 Resource forest (Linked Mailbox)

    Problem Description:
    Can’t move Exchange 2003 mailbox to Exchange 2010 resource forest
    Error message:
    Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials.
    Source Environment Configuration:
    Active Directory
    FQDN: umfolozi.local
    Domain name (pre-Windows 2000): UMFOLOZI
    Domain Function Level: Windows Server 2003
    Domain Controllers:
    Hostname
    OS
    Operation Master
    SRVUMVMDC01.umfolozi.local
    Windows Server 2008 R2 Standard SP1
    Schema Master, Domain Naming, RID, PDC
    SRVUMVMDC01.umfolozi.local
    Windows Server 2008 R2 Standard SP1
    Infrastructure
    Exchange
    Version: Microsoft Exchange 2003 Standard SP2 Build 7638.2
    Server Information:
    Hostname
    OS
    TUSKUMFMAIL.umfolozi.local
    Windows Server 2003 R2 SP2
    DNS Zones
    Zone Name
    Zone Type
    Domain Controllers
    umfolozi.local
    Active Directory-Integrated (Primary)
    SRVUMVMDC01.umfolozi.local
    SRVUMVMDC01.umfolozi.local
    peermont.com
    Secondary
    SRVPGVMDC01.peermont.com
    SRVPGVMDC02.peermont.com
    Trusts
    Domain Name
    Trust Type
    Transitive
    Validated
    peermont.com
    Forest
    Yes
    Yes
    Target Environment Configuration:
    Active Directory
    FQDN: peermont.com
    Domain name (pre-Windows 2000): PG
    Domain Functional Level: Windows Server 2008 R2
    Domain Controllers:
    Hostname
    OS
    Operation Master
    SRVPGVMDC01.peermont.com
    Windows Server 2008 R2 Std SP1
    SRVPGVMDC02.peermont.com
    Windows Server 2008 R2 Std SP1
    Domain naming, RID, PDC, Infrastructure, Schema Master
    Exchange
    Resource Exchange Forest
    Server Information:
    Hostname
    OS
    Role
    Version
    Client Access Array
    SRVPGVMEXCH01.peermont.com
    Windows Server 2012 Std
    HUB, CAS
    Version 14.3 (Build 123.4)
    exchange.peermont.com
    SRVPGVMEXCH02.peermont.com
    Windows Server 2012 Std
    HUB, CAS
    Version 14.3 (Build 123.4)
    exchange.peermont.com
    Hostname
    OS
    Role
    Version
    Database Availibility Group
    SRVPGVMEXCH03.peermont.com
    Windows Server 2012 Std
    MBX
    Version 14.3 (Build 123.4)
    PeermontDAG
    SRVPGVMEXCH04.peermont.com
    Windows Server 2012 Std
    MBX
    Version 14.3 (Build 123.4)
    PeermontDAG
    DNS Zones
    Zone Name
    Zone Type
    Domain Controllers
    peermont.com
    Active Directory-Integrated (Primary)
    SRVPGVMDC01.peermont.com
    SRVPGVMDC02.peermont.com
    umfolozi.local
    Secondary
    SRVUMVMDC01.umfolozi.local
    SRVUMVMDC01.umfolozi.local
    Trusts       
    Domain Name
    Trust Type
    Transitive
    Validated
    umfolozi.local
    Forest
    Yes
    Yes
    Migration Process
    Task
    Description
    Successful/Error
    1
    SYNC AD Domain account from source forest (umfolozi.local) to target forest (peermont.com) using BinaryTree SMART Directory Sync (ADMT can be used as alternative)
    Successful
    2
    Create mailed enabled user
    Successful
    3
    Run Prepare-MoveRepuest with –OverWriteLocalObject
    Command Example:
    .\Prepare-MoveRequest.ps1 -Identity [email protected] -RemoteForestDomainController SRVUMVMDC01.umfolozi.local
    -RemoteForestCredential $RemoteCredentials -UseLocalObject -LocalForestDomainController SRVPGVMDC01.peermont.com -LocalForestCredential $LocalCredentials -OverWriteLocalObject
    Successful
    4
    Submit mailbox request
    Command Example:
    New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeliveryDomain
    "internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Credential "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True
    Error
    All the standard migration task works as expected until the mailbox migration move request is submitted. See move request verbose detail below:
    [PS] C:\Windows\system32>New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeli
    veryDomain "internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Crede
    ntial "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True -Verbose
    VERBOSE: [11:34:27.346 GMT] New-MoveRequest : Active Directory session settings for 'New-MoveRequest' are: View Entire
    Forest: 'False', Default Scope: 'peermont.com', Configuration Domain Controller: 'SRVPGVMDC02.peermont.com', Preferred
    Global Catalog: 'SRVPGVMDC02.peermont.com', Preferred Domain Controllers: '{ SRVPGVMDC02.peermont.com }'
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Runspace context: Executing user: peermont.com/Admin/Users/Admin
    Accounts/Information Technology/SoarSoft/Johann Van Schalkwyk, Executing user organization: , Current organization: ,
    RBAC-enabled: Enabled.
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Beginning processing &
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Instantiating handler with index 0 for cmdlet extension agent "Admin
    Audit Log Agent".
    WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
    will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such
    items to the destination mailbox. At move completion, these corrupted items won't be available in the destination
    mailbox.
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Searching objects "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" of type
    "MailboxDatabase" under the root "$null".
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
    VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
    Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
     {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Searching objects "0fa7d17e-3637-4708-a51b-f14eaae17968" of type "ADUser"
     under the root "$null".
    VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
    VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Processing object "$null".
    VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] No RequestJob messages found.
    VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MDB c5d6ea95-07b3-4a52-9868-e41e808a76fe found to belong to Site:
     peermont.com/Configuration/Sites/Peermont
    VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MRSClient: attempting to connect to 'SRVPGVMEXCH02.peermont.com'
    VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] MRSClient: connected to 'SRVPGVMEXCH02.peermont.com', version
    14.3.178.0 caps:07
    VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] Loading source mailbox info
    VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Failed to reconnect to Active Directory server
    SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials. --> A
    local error occurred.
    VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that
    you have used the correct credentials.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : F48FD74B,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
        + PSComputerName        : srvpgvmexch02.peermont.com
    VERBOSE: [11:34:28.859 GMT] New-MoveRequest : Ending processing &
    Troubleshooting Performed
    1. When submitting mailbox move request tried the following credential inputs:
    1.1. DOMAIN\Username
    1.2. FQDN\Username
    1.3. userPrincipalName
    2. Confirmed domain trust between source and target domain is in place and validated.
    3. Confirmed name resolution in source and target domain is functioning as expected.
    4. Confirmed network connectivity between source and target domain controllers as well as source and target exchange servers.
    5. Tried to create new Linked Mailbox to account in source forest, can’t select Global Catologue via the wizard;
    Tried to specify the credentials for the account forest and got the following error when tried to select Global Catalog from wizard:

    The error talk about the credential. Did you check the credential
    Did you tried this command?
    New-MoveRequest -Identity "Distinguished name of User in Target Forest" -RemoteLegacy -TargetDatabase "E2K10 Mailbox Database Name" -RemoteGlobalCatalog "FQDN of Source DC" -RemoteCredential $Remote -TargetDeliveryDomain "Target
    domain name"
    http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://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.

  • Migration from an exchange 2003 organisation A (Exchange 2003 sp2) to another Exchange 2010 organisation B

    Hello,
    We have two Exchange organisations:
    - A (Exchange 2003 SP2)
    - B (Exchange 2010)
    we want to migrate from A to B. the two organisations have to coexist during the migration (6 months). during this time the users have to share the same GAL and Calendar (Busy/Free informations).
    What are the steps to follow ?
    is there any docs/links treat this subject ?
    Regards

    Hi,
    You can use FIM for GALSYNC.
    REF:http://setspn.blogspot.in/2010/05/global-address-list-synchronization-gal.html
    For calendar sharing follow the below blog:
    REF:http://blogs.technet.com/b/exchange/archive/2011/03/28/iorepl-and-exchange-2010-sp1.aspx
    Regards
    Vickram

  • Migrate exchange 2003 to office 365 with single singon

    Dear All,
    We are going to migrate our mail systems from exchange server 2003 to office 365 with single sing-on.
    Please advice me the best way and guide line (information) to do it smoothly.
    Thanks in advance.

    Dear Andres parnova,
    Thanks for your information.
    I found series of articles in msexchange.org
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/performing-staged-exchange-migration-office-365-exchange-online-part1.html which has very nice and clear information.
    But, in the articles the author did not include ADFS configuration and steps.
    I would like to know how to configure ADFS and single sing-on.
    Thanks
    Min

  • Exchange 2003 migration to 2010; anyone can send as anyone

    I have been handballed an issue post an Exchange 2003 to Exchange 2010 migration. The old exchange server has been completely decommissioned as far as I can tell. 
    The remaining issue is that now any user can send as any other user despite the permissions not being in place. 
    I have checked the ADSIEdit.msc permissions as detailed here: 
    http://social.technet.microsoft.com/Forums/exchange/en-US/df365e57-80b0-4d60-890d-72c36742b072/mailbox-permissions-send-as-anyone-can-send-as-anyone?forum=exchange2010
    I have checked all other user permissions that I can find.
    There seem to be a lot of articles with people having a similar issue but none with a common resolution. 
    Is anyone able to help with this?

    It might not report anything about permission but worth running ExBPA to see any configuration problem...
    How to find who has Full Mailbox access and/or Send As permission on various mailboxes in your environment? Or How to get the list of mailboxes on which someone
    has Full Mailbox access and/or Send As permission ? - https://exchangeshare.wordpress.com/2014/06/02/exchange-powershell-tip-09/

  • Install Exchange server 2010 in Single forest Multiple AD domain Scenario

    Hello Folks,
    I am trying to install a new exchange 2010 server in an enviroment which never had exchange.
    Below is the env details
    1 Forest
    3 AD domains
    Coustmer's requirement is that he wants to install exchange in only domain and other domain will not have exchange server the domain A which has server install should host the exchange mailbox's for other 2 domains and also capable enough to handle
    the mailflow of each domain with diffrent SMTP domain. Have done research but havent got the exact scenario.
    Now i am confused on how to start with this project any feedback inputs would be of great help to me.
    BR/Deepak

    Exchange server is forest wide role, so it does not depend much on number of domains in the same forest. Usually, you install Exchange in forest root domain in your forest, and Exchange will host mailboxes from any user from entire forest. So, actually,
    your scenario is supported by default :). Just go and install Exchange in one domain. As soon as you prepare other domains for Exchange recipients, you will be able to create mailboxes from all domains in your forest.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

  • Migrating from IIFP + Exchange 2003 to FIM + EXchange 2010

    Hello Everyone,
    hope you can help me figure something out 
    i had an IIFP Galsync synchronising users and contacts between 2 exchange 2003 environment and now i would like to switch to fim 2010 and Exchange 2010,
    from what i tried just exporting and importing the IIFP configuration to FIM 2010 works, but from what i know exchange 2003 is provisioned through vb code and exchange tools and exchange 2010 through remote powershell, is there anything to change in the
    original galsync extension code to enable exchange 2010 provisioning ? 
    thanks !!
    Hitch Bardawil

    Hi there Hitch
    The old IIFP galsync solution is obviously deprecated now, so I understand why you are wanting to convert it - but there have been too many architectural changes made in each of the components you're targeting to make any kind of conversion exercise realistic. 
    It is not an overly complicated scenario to handle in FIM, and as you point out the Exchange 2010 platform integration point is totally different and is even built into the MA itself (see
    Management Agent for Active Directory Global Address List (GAL)).  I suggest you have a trawl through old posts on Carol's blog
    to read about her take on what you are trying to do.
    Bob Bradley (FIMBob @
    TheFIMTeam.com) ... now using FIM Event Broker for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

  • Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

    I wasn't prepared for this task, and it was thrown at me to do...  Eyes are bleeding from planning reading and planning, would LOVE any input from you guys.  First time posting, here and have heard great things about these forums.  The Company
    I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
    Scenario:
    Old Domain/Server: (To be decommissioned)
    Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
    Exchange 2003 SP2 (6.5.7638.1)
    Server is a domain controller and exchange server.
    Migrating to:
    Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
    VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality 
    VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
    VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
    These are probably not ideal conditions, but I have to work with what I'm given.
    Host server (2012 R2) is in work group mode.  Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2.  I had intended starting at a lower functionality level and raising
    it later, but.... ya I forgot to change it.  If needed I can spool up a new DC with a lower functional level.
    DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain.  The concern is migrating the mailboxes from Exchange 2003 on the old domain to
    Exchange 2013 on the new domain.  The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
    I had some ideas, but I'm not sure if they will work.  This is something I have never done before (Senior Engineer Quit).
    My thoughts:
    - Establish a two way trust relationship between the two domains.
    - Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
    - Create the users on the new domain
    - Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013 
    - Link Exchange accounts to the correct user accounts on the new DC.
    Can this be done cleanly? Am I going about this the correct way?  Any feedback would be GREATLY appreciated.
    Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

    Hi,
    Base on my experience, your idea is feasible.
    However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link: 
    http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
    After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
    Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
    Exchange 2010/2007 to 2013 Migration and Co-existence Guide
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Moving Exchange 2003 mailboxes to Exchange 2010

    Hello
    I have a new domain with Exchange 2010 server. I plan to join users to this domain but would like to know the best plan in moving the existing Exchange 2003 mailboxes over. Can I just import the PST files into their new Exhaneg 2010 mailboxes or is there
    a better easier solution?
    Thank you

    Hi,
    You can export mailbox using ExMerge in Exchange 2003, but ExMerge only supports ANSI PST files which have a 2GB limit.
    To migrate mailboxes across forests, Active Directory Migration Tool (ADMT) will be used.
    Here is a blog which can help you to do cross forest migration from Exchange 2003 to Exchange 2010 for your reference.
    Exchange 2010 Cross-Forest Migration Step by Step Guide – Part I
    http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Question regarding Exchange ActiveSync migration from Exchange 2003

    Hello,
    I am a bit confused about info about requirements when migrating Exchange ActiveSync (EAS) from 2003 to 2010. Now this question is related to EAS only, forget about other services, such as OWA or Outlook Anywhere, for a while.
    Basically, all migration guides state that you have to configure and setup a legacy url for legacy services for co-existence. Based on that, I have had an understanding that Exchange 2010 CAS cannot proxy EAS users that are still on Exchange 2003, but issues
    a redirect command to EAS client.
    However, this article shows information that, based on my understanding, states that Exchange 2010 CAS DOES proxy EAS clients that are still on 2003: http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx
    For migration from 2007 EAS to 2010 EAS the article shows redirecting, but not with 2003.
    So my question is: While talking about only EAS, do I need to configure legacy external url/namespace/name resolution or not?
    Thanks for answering!

    Hello,
    I agree with Rajith's suggestion.
    Additional article for your reference.
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    Cara Chen
    TechNet Community Support

  • Server 2003 SBS (with Exchange 2003) migrate to new machine Server 2012 Standard (with Exchange 2013)

    This is what I have:
    A very outdated machine running a small domain, SBS 2003 and Exchange - this is the ONLY server currently.
    This is what my boss ordered:
    A Dell R210 II machine with Server 2012 Standard (and I downloaded the trial for Exchange 2013).
    He wants the old server completely replaced and gone - with everything moved over (including Exchange) to the new machine. The main reason for the upgrade is that not all users can access email on their machines (Macs, new versions of Outlook, etc.)
    I have set up a new standalone server before but never migrated one - and I've found that going from SBS2003/Exchange2003 to Server2012/Exchange2013 is not simple in the least.
    I thought I could just set up the new server as a DC on the domain and have everything replicated to it from the source server. Then I could decommission the old server. I have been told that 1) I can't upgrade Exchange 2003 to 2013 and 2) that I shouldn't
    put Exchange on a DC. What do you do if you only have the one server?

    Hi,
    Just additional. Please also refer to following threads and article, then check if can help you.
    Migrate
    SBS 2003 to Windows Server 2012 Standard
    Migration
    SBS 2003 to Windows Server 2012 Standard
    Transition
    from Small Business Server to Standard Windows Server
    Hope this helps.
    Best regards,
    Justin Gu

  • Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

    Hi,
    We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
    We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
    Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
    1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
    that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
    2. When I try to install exchange server 2007 , I get the following error
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
    by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
    Can any one shed light on this issue.
    Regards
    Syed
    sa

    You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
    Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
    Where are you installing Exchange ? child or parent domain ?
    2. When I try to install exchange server 2007 , I get the following error "Object
    cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
    Above error indicates that Exchange setup is trying to modify
    a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
    Please give more information about your current email infrastructure
    and whether if you are installing exchange on parent or child domain?
    Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
    question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Maybe you are looking for