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.

Similar Messages

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.

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

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

Exchange 2010 to 2013 cross forest migration doesn't have an SMTP address that matches the target delivery domain

I’m having a problem moving a mailbox from exchange 2010 sp3 to Exchange 2013 which are in two separate forests.
Two way trust in place
Certificates imported
ADMT is set up.
SMTP namespace oldcompany.org and newcompany.org for the old email domain and new one is configured to be shared between forests.
I’m doing the following:
Step 1
Prepare-MoveRequest.ps1 -Identity [email protected] -RemoteForestDomainController DC1. oldcompany.Local -RemoteForestCredential $RemoteCredentials -LocalForestDomainController DC1. newcompany.local -LocalForestCredential $LocalCredentials -TargetMailUserOU
"OU=Office Users , DC=newcompany,DC=local" –verbose
Everything goes ok, and a disabled user is created. A disabled user account is created in the correct OU.
Email address is set to [email protected]
Proxy smtp addresses are set:
smtp:[email protected]
SMTP:[email protected]
smtp:[email protected]
Step 2
I then use ADMT and migrate sid history ect.
Step 3
New-MoveRequest –Identity [email protected] –Remote –Remotehostname exchange.oldcompany.local -RemoteCredential $RemoteCredentials –TargetDeliverydomain exchange.newcompany.local
This then fails with the error:
The target mail user newcompany.local/Office Users /mark test' doesn't have an SMTP address that matches
the target delivery domain 'exchange.newcompany.local'.
    + CategoryInfo          : InvalidArgument: ([email protected]:MailboxOrMailUserIdParameter) [New-MoveReques
   t], RecipientTaskException
    + FullyQualifiedErrorId : [Server=EXCHANGE,RequestId=ec704dc8-bfb9-47c1-a1ec-cc6d8ef00484,TimeStamp=23/12/2014 1
   0:51:33] [FailureCategory=Cmdlet-RecipientTaskException] 5ABE3B29,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
    + PSComputerName        : exchange.newcompany.local
Any ideas what I am missing.

Hi Walkersway,
As you have mentioned both the domains are "shared between forests", I would assume its added to the accepted domains as Internal Relay. Also you have 'Send Connector' Setup to relay out the email to the new forest.
"You configure the SMTP domain as an internal relay domain to make sure that email that's addressed to that domain is accepted by the Exchange organization. The connector configuration of your organization determines how messages are routed."
In your case "newcompany.local" should be present.
Try this:
New-MoveRequest –Identity [email protected] –Remote –Remotehostname exchange.oldcompany.local -RemoteCredential $RemoteCredentials –TargetDeliverydomain newcompany.local
The TargetDeliveryDomain parameter specifies the FQDN of the external email address
created in the source forest for the mail-enabled user when the move request is complete. This parameter is allowed only when performing remote moves with the
Remote or RemoteLegacy parameter.
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

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

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

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

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

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

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

Cross Domain migration

Hi,
I would like to know best practice for Cross forest Migration from Exchange 2010 to Exchange 2013... Here is the scenario:-
1. There are two forest abc.xyz.com & efg.xyz.com.
2. abc domain having Exchange 2010 is running.
3.Efg domain having user accounts and users login to laptop using this domain.
4. I have to install Exchange 2013 in Efg domain and migrate mailboxes from Exchange 2010 servers. This includes public folder, GAL Sync & Free /busy.
Please suggest me best practice to achieve goal ... Pls. send details on
Thanks in Advance !!
Amit kumar

Hello,
You current topology is “Resource/User forest“, right?
The basic requirement is: the Exchange 2013 target forest must contain a valid mail-enabled user with a specified set of Active Directory attributes.
http://technet.microsoft.com/en-us/library/ee633491(v=exchg.150).aspx
Thanks,
Simon Wu
TechNet Community Support

Gal Sync and group member sync cross forest. Not working together

I am finalizing a cross forest migration. The End client needs an extended period of time with both domains up and running. I have been working with an advisory engineer and we are having a hard time.
We started by setting up GAL sync and that works as expected. Then we tried to setup group provisioning, and I have that working. I can create a groups and add members, as long as those users are in FIM and the Target forest the membership information
is preserved. During the process we removed the GAL sync agents for ease of troubleshooting. Now when I run the GAL sync agents and I search the connector space I am showing connector false on both sides. I am not sure how to correct that. The other objects
were created by the DS agents and FIM. If I sync a new object it will create a contact cross forest.
What I want it to do is run the GAL sync without group contacts. Synchronize the GAL on both sides. (Groups have been created on both sides of the domain and ADMT has moved the group membership with the user) After the GAL is synchronized I need FIM
to synchronize the group membership adding the contacts from the missing users that have moved. I am not sure how to get that logic in the system.
I am not sure I am going about this the right way. It may be easier to use the FIM and AD DS agents to provision users cross forest as contacts and the group membership would be preserved. If that is the case, I am not sure how to pull
that off.
Does anyone have recommendations?
Thank You

This is an overview of basically how it works.
The Group sync is pretty much out of the box, the real key here is the User is imported to FIM and that 'Person' is then provisioned outbound as a contact.
Membership synchronizes with the Group and FIM maintains group membership cross forest as the source user, and the target contact are the same 'Person'.
Precedence is important. The OU structure is the same on both forests and needs to be initialized. The Groups Sync is ahead of the users and then the users sync, and the group membership
syncs.
The attribute flow is a long list. It includes all of the exchange information for the contact, and it provisions the contact as mail enabled on both sides. There is no VB it’s all
done in sync rules.
Next Ill post the attribute flow and precedence diagram, I’ll get that together this week (I hope). I intend to put this up in a lab and get screen shots on the whole configuration.
I will do that as soon as I can.
Let me know if you have questions.

Cross Forset Migration from sccm 2012 to sccm 2012RS

Hi all,<o:p></o:p>
We have a plan to migrate
sccm 2012 to sccm 2012 R2 on trusted forest (cross forest migration)<o:p></o:p>
Please share possibility...<o:p></o:p>
Thanks, Mariappan Shanmugavel

Possibility for what?
Migration only works from ConfigMgr 2007 SP2 or from the same version of ConfigMgr 2012 thus will not be able to migrate from 2012 to 2012 R2. You will need to upgrade your 2012 site to 2012 R2 first and then perform the migration. The TechNet docs clearly
show this: http://technet.microsoft.com/en-us/library/gg699364.aspx
ANd, as Torsten pointed out, if you are simply planning on moving the existing site server, that isn't supported and won't work either.
Jason | http://blog.configmgrftw.com | @jasonsandys

Is that possible to do the cross domain migration for AD RMS Services?

Hi guys, recently i am doing a cross domain migration, when i listing out the server, i found the server have AD RMS services which is still active.
but after my migration is complete, it is planned to do the decommission on all the old server
After my checking, i believe the AD RMS have trust establish with a cross site domain already. What i am planning to do is try to do a migration on it.
i have do some research on it an i found "Cross forest Migration of AD RMS document"
what i found in the document, it have mention about
In the event when one cluster running AD RMS is to be discontinued, users may still want to access
previously protected content that was issued a publishing license by that computer. Servers in other clusters can then add the to-be-discontinued server as a trusted publishing domain.
So i was wondering if there is an option for Ad RMS services to select a server or host to discontinued?
The scenario in my head now,
1.Build trust between in my new domain AD RMS with the existing AD RMS. update the certificate between the trusted domain as i mention above with my new domain AD RMS.
but i was wondering if i power down or decommission the server what will happen?
2. the worst case scenario will be decommission the old AD RMS service, and publish the new AD RMS services in new domain, simply build trust with the cross site domain.
any suggestion on this? which case is more workable?
Thanks
Dave

Hi,
I think you may ask in AD RMS forums:
http://social.technet.microsoft.com/Forums/en-US/home?category=rms&filter=alltypes&sort=lastpostdesc
Regards.
Vivian Wang

Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2

Similar Messages

Maybe you are looking for