SCOM 2007 cross-forest clients migration

   Hello to all. I'm preparing a cross-forest migration from source domain domain1.a.com to target domain domain2.b.com . 
   Source domain has hundreds of servers (windows 2003 and windows 2008). All source DCs are Windows 2003. Source domain already has SCOM 2007 R2 deployed on its member servers and on others located on another source domains.
   As cross-forest migration will run just for domain1.a.com I need to know:
   1- Is possible to migrate member servers from source-->target and keep source SCOM 2007 R3 monitoring the already migrated member server? 
   2-If positive, what need to be done in advance (before any member server migration) and after each member server migration?
   3-If target forest already have a SCOM 2007 R2 environment, what should need to be done so migrated member servers would be monitored on this target SCOM 2007 R2 (that has nothing to do with the source one) ?
   Thanks in advance, EEOC.

1. It is possible.
2. You will have to install certificates in the environment and either manag the agents through a gateway (minimal number of certs) or by installing certs on the agents directly.
3. Just uninstall the agents and reinstall by the target SCOM 2007 R2 console.
Juke Chou
TechNet Community Support

Similar Messages

  • SCCM 2012 & SCOM 2012 - Cross Forest

    My current environment is running Operations Manager and Configuration Manager 2007, I am planning an upgrade them to the 2012 version.
    I need to know whether my upgrade to 2012 will support cross forest support ?
    Cheers

    And, there is no 'upgrade' of Configuration Manager 2007 to Configuration Manager 2012 (if you mean Configuration Manager 2007 instead of "SCCM 2008"). You would need to do a side-by-side migration. There are docs, webcasts, webinars (in fact I just did
    one a couple of weeks ago), and TechNet virtual labs on migration to help you gain understanding on how it would work.
    However, yes, Configuration Manager (both 2007 and 2012) do support cross forest environments.
    Wally Mead

  • SCOM 2012 Cross forest deployment

    Hi all,
    Is two way trust is mandatory to deploy cross forest scom 2012 if we user certificate also ?
    Thanks,
    Sengottuvel M

    Monitoring across non- trust domain
    1) two way trust between domains OR
    2) using certificate
    Roger

  • Exch 2007 to Exch 2007 Cross forest migration

    Hi all,
    I am currently migrating all users from a root domain in one forest to a child domain in a second forest.
    Source: Forest A\DomainA is server 2003 r2 with Exchange 2007 SP3
    Target: Forest B\Domain B is server 2008 r2 with Exchange 2007 SP3
    I am using ADMT to migrate the user accounts with SID history. Data has been replicated over with permissions in tact.
    domain trusts have been put in palce and SID filtering has been disabled.
    Order of migration thus far;
    1. Migrate Sec Groups
    2. Migrate Distribution lists - with target proxt address only (source will be added on the weekend of the cut over)
    3. Migrate User Accounts. all exchange attributes are stripped out. Source/target user account's are left in current state (not disabled)
    4. I then run this powershell command to migrate the user mailbox over;
    Move-Mailbox -TargetDatabase TargetStore -Identity SourceUser -GlobalCatalog TargtDC -SourceForestGlobalCatalog SourceDC -NTAccountOU SourceOrgUnit -SourceForestCredential SourceCredential -TargetForestCredential TargetCredential -Confirm:$False
    The mailbox is migrated over and it automatically connects to the corresponding user that was migrated previously. How is this connection made. The move-mailbox does not migrate the source user. I was under the impression that the mailbox would show in the
    target as a linked mailbox and then I would have to disconnect and it reconnect it to the target account. it makes my life easier that it reconnects it but i wanted to know if im missing something. is this the correct way in which to migrate the mailboxes.
    Thanks

    Hello,
    It’s expected. In AD account properties, there are a lot of attributes about Exchange, such as HomeMDB, HomeMTA…
    When you use AMDT, these values will be changed to the target domain so that they matches.
    Thanks,
    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]
    Simon Wu
    TechNet Community Support

  • Active Directory Cross Forest Domain Migration

    Dear All,
    We are in the process to rebuild new Active Directory infrastructure. Multiple single forest domains in organization which needs to be consolidated/migrated on single Active Directory Domain. For this consolidation, have some queries to be addressed before
    going to start consolidation.
    What is the best practices and what tool should we use for domain migration/consolidation
    Active directory is on Windows 2003, forest and domain level is on Windows 2003, this will support to Windows 2012 R2 forest and domain functional level, will be migrated
    directly from windows 2003 to windows 2012?
    When move users to new domain, how will they access the other resources on the network. For e.g. Printer, File server, local web base application
    After moving some computers to new domain would be possible to access remaining computers on old domain?
    How the file server data will be moved? Best practices with NTFS folder permissions and users rights?
    Is there any policy to register network printers on new Active Directory domain?
    How users would be access web base application on new domain as their FQDN would be define with old domain name? Any option to change old domain FQDN with new domain that would be describe with any URL link?
    Kindly give your valuable input to meet the desire result.
    Thanks in Advance.

    Dear Lucky,
     Ya you can Migrate contents from multiple forest domain. Using ADMT (Active Directory Migration Tool)is the best way to migrate AD content. But you can't migrate from Windows Server 2003 to Windows Server 2012 R2, cause in Windwos Server 2012 R2 don't
    have the supportebility of Windows Sever 2003.And not only users you can also migrate all others info (i.e. Computer object info, groups info, Exchange mailbox info, security info).You can migrate users face by face, means which peoples are in old domain they
    can access old domain and new users are in new domain.For more info please follow the given link:
    http://technet.microsoft.com/en-us/library/cc974332(v=WS.10).aspx
    Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

  • SCCM 2012 - Network requirements for Client communication to primary in a Cross Forest Environment

    Hello, I have been trying to get some definitive answers on what network traffic is required between a client and a primary site versus a secondary in a cross forest scenario.
    Here is the scenario:
    Company A has an existing SCCM 2012 primary Site. Company B (Separate Forest) has now been brought in. One subnet on each side can route to each other and using that one subnet a two way forest
    trust has been setup. But the remote offices have IP address overlaps between companies. At some point in the future all assets on company B will be re-IP and brought over to Company A domain. But in the interim it would be nice to get SCCM cross forest clients
    working. Upgrading to a CAS model with two Primaries would not be preferred here as this is a temporary solution. 
    My questions are as follows.
    If a secondary site is deployed into Company B Forest/Network. I have seen people online elude to that clients will still need to communicate to the Primary located at Company A, even though they
    are assigned to a secondary on Company B’s network. Is this true? Is there any workarounds for this? Is a NAT back to the primary acceptable, or is reverse lookup required?
    Will the Primary need to communicate directly to the clients in Company B? If this is in fact a requirement, then this would be a show stopper. But if its only needed for things like client pushes,
    then we could work around it.
    Thanks

    "But the remote offices have IP address overlaps between companies"
    Technically, this is unsupported because clients, depending upon your boundaries, will not be able to find a local DP since they use IP addresses for this. The only way to work around this is to use AD Site boundaries.
    "though they are assigned to a secondary"
    Clients are *never* assigned to a secondary site -- that's not what secondary sites are for. Yes, clients require communication with an MP in the primary site where they are assigned. There is no way to change this or work-around this except to put
    an MP from the primary site closer to those clients and use the new MP affinity option in R2 CU3.
    Reverse lookups are only used to verify names by applications that wish to have this type of functionality (which are very few in number) and have nothing to do with true network traffic. NATing is an issue for the reason I gave above -- DP location.
    Remote control, client push, and WoL won't work either because there is no way for the traffic to reach the destination behind the NAT.
    All client *agent* communication in ConfigMgr is client initiated in ConfigMgr (remote control, client push, and WoL -- as just mentioned -- are sort of exceptions to this but they don't really involve the client *agent*.)
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Cross Forest Migration from Exchange 2007 to Exchange 2013

    Hi
    Could anybody advice me the steps also the  pros and cons for below mentioned environment if we are going for the cross forest migration.
    Source 
    Domain -   test.local
    Active Directory -  Windows 2003
    Exchange Server - 2007
    Target
    Domain -   test.net
    Active Directory -  Windows 2012
    Exchange Server - 2013
    Also if it is possible ,
    How could I remove the source environment including the exchange servers. after the migration ?
    Regards
    Muralee

    Hi Oliver ,
    Please suggest us.               
     In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
    Source : Exchange 2007 with sp3 ru 10 
    Target : Exchange 2013 with cu2 ( new environment yet to be created).
    Trust : Forest trust in place (two way )
    Domain and forest functional level : 2003 in both target and source  
    Migration Steps :
    Step1 :
    We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
    in the target forest.
    Step2:
    Then we are going to use ADMT to migrate users SID'S and password .
    Step3:
    Then we are going to move the mailboxes with New-moverequest  
    Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
    .Is anything needs to be changed please intimate me .
    Thanks 
    S.Nithyanandham 
    Hey there,
    Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
    Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
    More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
    Oliver
    Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

  • Cross-forest access to public folders Exchange 2013-2007

    Dear.
    We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
    User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
    What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
    Thanks for the support.
    Regards.
    Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

    Hi Stephen,<o:p></o:p>
    <o:p> </o:p>
    Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client  permission
    to see if we can access the
    public folders.<o:p></o:p>
    <o:p> </o:p>
    If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
    http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
    http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
    <o:p></o:p>
    Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
    Link:
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
    <o:p> </o:p>
    So for public folder migration,
    the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
    we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
    <o:p></o:p>
    Regards, Eric Zou

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes

    Hey all,
    So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
    AD, etc. But I'm wondering if someone can break it down for me.
    http://1drv.ms/1lWjLqG
    The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
    Original Design
    The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
    are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
    There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
    Migration/Hybrid Design
    Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
    A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
    We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
    Migration from Exchange 2007 to Exchange 2013
    I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
    The latest Service Packs and CUs are installed in both.
    What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
    SpecialBank that users are actively using.
    I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
    If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
    if I need to in order to make the migration transparent to users.
    Can anyone help?

    Hi ,
    From you description i came to know contoso is the resource forest and special bank is the account forest .
    You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
    Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
    http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • WSUS 3.0 SP2 master server cross-forest migration impacts

        Hello to all, I'm preparing a cross-forest migration and have one WSUS 3.0 SP2 master on source forest placed in root domain. This master has 16 replicas scattered among child source domains. As I plan do migrate member servers using MS
    tool named ADMT 3.2 and considering that I will firstly migrate just root domain member servers to target forest, I need to know:
       1- Will WSUS 3.0 SP2 master server work after it's migrated from source to target forest? I mean: can all its replicas still access and donwload the necessary patches from it? Will its configuration be in place (groups, schedules, etc) ?
       2- Should I need to change source domain clients WSUS GPOs to point to the just migrated master server (new FQDN name)?
       3- Is possible to change my just migrated WSUS 3.0 SP2 to be replica from a master server already present on target forest? How this move could affect its existing replicas still present on source forest?
       Suggestion and attention points will be appreciated.
       Regards, EEOC.

    1- Will WSUS 3.0 SP2 master server work after it's migrated from source to target forest? I mean: can all its replicas still access and donwload the necessary patches from it? Will its configuration be in place (groups, schedules, etc) ?
    Fundamentally yes, as long as the downstream servers are updated to use the new hostname and DNS properly resolves that hostname. NOTE: You cannot "migrate" the WSUS role using ADMT. What is your plan for "migrating" the WSUS upstream server?
    2- Should I need to change source domain clients WSUS GPOs to point to the just migrated master server (new FQDN name)?
    Probably. Presumably the hostname and IP Address of the server are going to change.
    3- Is possible to change my just migrated WSUS 3.0 SP2 to be replica from a master server already present on target forest?
    Yes, but that's kind of a cart-before-the-horse move... which brings us back to the original question: How do you plan to "migrate" the upstream server?
    How this move could affect its existing replicas still present on source forest?
    Well.. it will introduce a three-tier replication hierarchy for starters, which will slow everything down by one or two days. But, really, I wouldn't worry about that because there's no real need to do this.
    Suggestion and attention points will be appreciated.
    Install a *NEW* WSUS server in the target forest.
    Configure it as a replica of the existing master in the source forest.
    Replicate.
    When the replication is complete, reconfigure it as an Upstream Server and RESET the Product Category and Update Classifications to what they should be.
    Synchronize with Microsoft.
    When that sync is successful, enabled regular synchronizations.
    Configure clients and downstream servers to sync from the new upstream server in the target forest.
    When all clients and downstream servers are working with the new server, turn off the old one.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Exchange 2007 to Exchange 2010 cross forest simultaneous mailbox move limits

    Hi All, 
    I am testing the throughput of mailbox moves from Exchange 2007 to Exchange 2010 cross forest. Single mailbox moves seem to be quite fast and I am not concerned about network, disk IO or server resource limitations, however I have not tested multiple simultaneous
    mailbox moves to determine what the Exchange limitations are. If anyone could identify the limitations of the items below it would be much appreciated: 
    Limit of Exchange 2007 simultaneous mailbox moves per database
    Limit of Exchange 2007 simultaneous mailbox moves per Mailbox server
    Limit of Exchange 2007 simultaneous mailbox moves per CAS server
    Limit of Exchange 2010 simultaneous mailbox moves per database
    Limit of Exchange 2010 simultaneous mailbox moves per Mailbox server
    Limit of Exchange 2010 simultaneous mailbox moves per CAS server
    Any other Exchange 2007 or 2010 hard coded limits
    Thanks in advance. 
    Michael.

    My usual answer to this question is that Microsoft set these limits for a reason.  Increasing them may not offer you much in the way of benefits if you end up slamming the server.  I generally recommend that you leave them alone.
    I have had occasional opportunities to change these constraints, most notably back during a migration to Exchange 2003 and international mailbox moves (Asia to U.S.) where the limiting factor was network latency.  I was able to increase the number of
    concurrent threads to 16 from the default 2 and there was still available bandwidth because the process was limited by the latency. 
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Public Folder Migration Cross Forest

    Hello,
    We are in the middle of planning a cross forest migration from Exchange 2010 to Exchange 2013. 
    To give some context:
    We already have an Exchange 2013 environment complete with mailboxes, and public folders etc. We have a 2010 Exchange server in a different forest that we would like to migrate all existing mailboxes and public folders from to the Exchange 2013 forest. We will
    be keeping the domain/forest that currently contains 2010 so all mailboxes that will be moved will end up being linked mailboxes in the 2013 organization with the accounts held in the other forest. 
    One of the big unanswered questions remains around public folder access. During migration there will be a time when some users will be in the Exchange 2010 organization, and some will be in the Exchange 2013 organization. I have two main questions around this
    1. Is there any way possible that anyone can think of that the users moved to 2013 can access the public folders still on 2010?
    2. What is the best way to migrate the public folders over from 2010 to 2013? Do we have to create the public folders and permissions on 2013 before hand or do we use a 3rd party tool or other method to achieve this goal?

    Hi,
    To reduce needless trouble, I recommend migrate mailbox first and public folder second.
    However, public folder will works fine no matter where it located. If you experience an issue about user in Exchange 2013 mailbox cannot access Public Folder in Exchange 2010, please change the RPC authentication to NTML.
    More details about it, please refer to:
    https://social.technet.microsoft.com/Forums/exchange/en-US/3172435f-4c06-41b3-b7a7-937dc0160049/exchange-2013-users-unable-to-access-exchange-2007-public-folders?forum=exchangesvrdeploy
    Additional, step by step to migrate Public folder to Exchange 2013, for your reference:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
    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

  • DHCP Migration - Cross Forest

    I have an existing AD - oldco.com, with DHCP configured.
    I am now migrating the entire AD infrastructure to a new domain - newco.com.
    The migration of computers will be phased over a period of weeks / months.
    DHCP scopes will remain the same, however DNS servers will be different (new DNS servers in the new AD).
    Can someone please validate this approach:
    Set up conditional forwarders on oldco.com DNS servers for newco.com
    Migrate PCs from oldco.com to newco.com using ADMT (DHCP is not domain dependent so PCs should pick up DHCP lease from oldco.com DHCP server. oldco.com DNS settings will be applied but conditional forwarding will be in place. (I could also just add newco.com
    DNS servers to oldco.com DHCP scope settings?)
    After all PCs have been migrated to newco.com, migrate DHCP databases from oldco.com to newco.com DHCP servers (edit DNS settings to use newco.com DNS servers).
    De-authorise oldco.com DHCP servers, authorise newco.com DHCP servers.
    I have completed several DHCP migrations previously in the same forest so I am ok with steps 3 and 4. It is really the cross-forest element that I am concerned with.

    Hi,
    According to you description, my understanding is that you want to migrate current AD infrastructure to a new domain, and need to confirm your plan about migrating DHCP.
    Clients will obtain IP lease from the DHCP server which provides them the DHCPACK message. Is there is only one DHCP server, clients will still obtain IP lease from the old DHCP server. It is better to set conditional forwarders(to transfer DNS queries to
    new domain) instead of adding the new DNS server to scope option. Or you may create a secondary zone on old DNS server to obtain a read-only copy zone file from the new DNS server.
    Manually assigned new DNS server of TCP/IP properties on client is needed when client join to new domain.
    You may do lab tests before migration. And remember to backup related data.
    Best Regards,
    Eve Wang
    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 Support, contact [email protected]

  • Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2

    Hi,
    We are planning cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2.
    Requesting you to please help us out for below scenario.
    Source Exchange 2010 SP2:- abc.com
    2AD, 2CAS & 2 MBX servers
    Database:- 4
    Total Users :- 3500
    Accepted Domains :- 8
    Total Data:- 5TB +
    Target Exchange 2010 SP2:- xyz.com
    Resource allocated same as above.
    Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.
    With the guidelines mentioned in
    http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-14203 we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into
    OWA. It gives error “The Outlook Web App address
    https://mail.abc.com/owa is out of date.”
    Kindly let us know how to solve this issue.
    Kindly let me know if you want any more information from our end.
    Thanks in advance.
    Thanks and Regards, Shashank Kudi

    Hi Shashank,
    Do you have certificates properly installed and configured in the target Exchange?
    If not, Please configure certificate and import the certificate to the trusted root CA if you are using internal CA cert.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Maybe you are looking for