Plan migration new domain.

Hi Guys,
I am planning a stage migration from Domain_one to domain.two and an upgrade (New install) to exchange 2013. You will notice the underscore in Domain_one which is the reason for the migration
as we cannot install exchange 2013 (2007) with underscore in the domain.
I am hoping someone can review my plan overview and let me know if I am missing anything.
Create new domain.two
Create Trusted relationship between domains
Add desktop to domain.two
Test communication from desktop to domain_one servers (Excluding Exchange)
Install exchange domain.two
Setup exchange in domain_one to forward any mailbox that cannot be resolved on server to exchange server in domain.two
Use migration tool to migrate desktop to domain.two
Test Exchange in domain.two and migrated desktop access to domain_one
Export / import mailbox.
Migrate desktop in controlled process
Migrate server to domain two.
Point inbound mail to exchange server domain.two
One of the question I have is how to create the access to server from domain.two to domain_one. I assume that I need to allow security in the format of domain.one\Security group.
Thanks for any advice in advance.
Craig
Craig

Hi Craig,
About domain name, I would like to clarify the following thing:
1. The domain name can contain Letters, numbers, or hyphens (-).
2. The domain name should begin and end with a letter or a number.
What's more, I would like to verify if you do a staged Exchange migration.
Staged migration is used to migrate all the organization's mailboxes to Exchange Online.
Moreover, I recommend you perform a cross forest mailbox migration to a new Exchange 2013 Server that is installed in a new domain.
For more information, here is a blog for your reference.
Exchange 2010 Cross-Forest Mailbox Moves
http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

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

AD Migration from NT 4.0 using New Domain Name & Unity UM

The customer currently has Unity 3.1(5) UM with Exchange 5.5 in NT 4.0 domain. They will be migrating to AD 2000 during phase 1 of the project, which will be followed by Unity upgrade to 4.0(4) a few weeks afterwards.
During the phase 1, Exchange 2003 will be introduced, but the mailboxes will remain in Exchange 5.5 until phase 2.
Here is the migration path proposed by the customer for the phase 1.
1. Current DNS will be isolated to a W2K server with the new domain defined in the DNS. All servers will point to this DNS server as their primary.
2. A BDC will be setup and then removed from our network.
3. Our PDC will be upgraded to Windows 2000 server. AD will be setup with a new domain of XXX.PRV
4. Service packs will be applied to the server.
5. The AD connector will be installed for Exchange 5.5
6. An additional W2K server will be brought online as a DC and additional global catalog.
I do realize that domain name change is not supported for Unity, but would this have any impact on Unity? Basically, the PDC that will be upgraded to W2K DC will retain old domain name (XXX_NT) as the NetBios name whereas the new DNS domain name will be XXX.PRV.
Since Unity does not need to talk to AD or Exchange 2003 at all until the phase 2, Im thinking this would be okay, but wanted to get some expert opinions on it. Also, the customer has tested some legacy servers in the lab, and they were able to authenticate against the XXX_NT domain name in the new XXX.PRV AD environment.
Phase 2 will consist of the following tasks.
1. Run DB Walker.
2. Back up using DiRT.
3. Extend AD schema.
4. Upgrade Unity to 4.0(4).
5. Disconnect Unity from Exchange 5.5.
6. Upgrade Exchange System Manager on Unity.
7. Re-establish Exchange partner relationship using Exchange 2003.
8. Run DB Walker.
9. Move Exchange 5.5 mailboxes to Exchange 2003.
Thank you bunch!
Han

Your project (from oh so long ago) looks very similar to what I am proposing to do now. I currently run Cisco Unity 4.0.4 SR1 with Exchange 5.5 (Unified Messaging), on an NT4 network. I have recently upgraded my network to Windows 2003 with Active Directory. I am building a new Exchange 2003 server in the new domain but not upgrading Unity 4.0.4--at least, not yet. I am looking to change the Partner Exchange server to point at the new Exchange server. I see no docs that cover such a scenario--only lateral moves (5.5 to 5.5, 2003 to 2003). As long as the ADC is in place, do you think I even have to change the Partner server when my new Exchange server comes online (initially)? How did your project turn out? Did you have to change the process you outlined above?
Thanks for any info!
John

Issue in SQL-server migration to new domain

Hello,
I have a scenario, where i need to migrate SQL 2005 servers db's ( around 30, small ones) to new server in a new domain. Destinationserver is 2012 R2, running SQL2014
Domains have trust between them, and users have already been migrated to new domain. Users are using the databases with NT authing from the new domain (new logins & users have been created to old sql-server).
I have backed up db's from old server and restored them in new server. After that, i restored logins with following article's script:
http://support.microsoft.com/kb/918992
I cleaned from the login script logins that are not in use, change the domainname to new in CREATE LOGIN phase (for the users who did not have already login from new domain) and the script ran without errors.
User Mappings are like they should be on logins, however, the user & schema names are indicating to old domain. If i try to change them, i receive error about SID mismatch. This affects also users, who have already had new logins for new domain, their
usernames on mappings are also changed to old domain's username. What is causing this?

Hi,
Could you try the following to migrate the logins and check the result?
1. You may drop all the windows login. Modify the script generated by sp_help_revlogin step and replace create login
to drop login.
2. Use the script generated by sp_help_revlogin step to create
Logins. Modify login name to accommodate new domain name.
3. Grant server level roles using the output from:
Generate Server level role related info :
SELECT 'EXEC sp_addsrvrolemember ''' +
p.name + ''' , ''' + r.name + ''';'
FROM
sys.server_principals r
INNER JOIN sys.server_role_members m ON r.principal_id = m.role_principal_id
INNER JOIN sys.server_principals p ON
p.principal_id = m.member_principal_id
WHERE
r.type ='R'
Sample Output :-
EXEC sp_addsrvrolemember 'sa' , 'sysadmin';
4. Map the SIDS using below command for all DB by using ALTER USER. For example:
ALTER USER [DomainA\UserA] with login = [DomainB\UserA]
See:
http://blogs.technet.com/b/mdegre/archive/2011/06/27/can-i-move-sql-server-to-another-domain.aspx
Here some useful articles:
http://www.databasejournal.com/features/mssql/article.php/3922256/Re-generating-SQL-Server-Logins.htm
http://support.microsoft.com/kb/918992/en-us
http://support.microsoft.com/kb/240872
Thanks.
Tracy Cai
TechNet Community Support

AD User migration to new domain

I have SharePoint site in Domain A with 1000 users. There will be new domain B setup. I need to migrate ShrePoint Site from domain A to domain B. The AD users SID will remain the same. Below are two possible solution
1. Install new SharePoint in Domain A. Restore the site from Domain A to Domain B. Migrate all 1000 users using move-Spuser or Stsadm command.
2. Change the domain for System hosting SharePoint. Then migrate the 1000 users using move-Spuser or Stsadm command
Will the permission remains same in case user is migrated or what can be other issues.
Please remember to mark the replies as answers or vote as helpful if they help.

So one thing to keep in mind is that disjoining/joining SharePoint farms from one domain to another isn't supported. Instead, the general process is to build a new farm in the target domain and recreate it, restoring backups of content/service application
databases as necessary.
Users cannot be moved from one domain to another without a SID change. Part of their SID stems from the domain they're a member of, and that changes when they're moved. There is a function called SIDHistory which stores previous SIDs from previous domains,
and this is commonly used. Despite that, you still need to issue a Move-SPUser, not only because their SID has changed, but because their domain name has changed.
One thing to note is that if you're using a Claims-enabled Web Application, you still must issue -IgnoreSID in the Move-SPUser cmdlet, regardless if SIDHistory is used or not during the migration.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

After migrating a windows 7 machine using ADMT Group policy shows the the computer is from the new domain but user is from old domain

We have migrated machines using ADMT tool but we have found some window 7 machines Group policy issues. We see that the computer GP is getting from the new domain but the users profile still has the old domain GP information. Any help on
removing the old GP objects and forcing the new domain User policy would be great. We have tried the basic troubleshooting gpupdate /force reboot etc.
Thanks

Hi,
Sorry for the delayed response.
First, please verify whether these domain users you mentioned belong to old domain or new domain.
If they belong to old domain the GP is right with no problem. If they belong to new, try following suggestions.
Please test these steps in one of the problematic computer. If it worked, then go on for others.
To avoid unexpected problems, please backup your register keys before following steps:
Open regedit.exe, and delete following keys:
HKLM\Software\Policies\Microsoft Key (looks like a folder).
HKCU\Software\Policies\Microsoft Key.
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects Key.
HKCU\Software\Microsoft\Windows\CurrentVersion\Policies key
Exit the registry and restart.
Note: HKLM = HKEY_LOCAL_MACHINE & HKCU = HKEY_CURRENT_USER
If you have any feedback on our support, please click
here
Keep post.
Kate Li
TechNet Community Support

Migrate to new domain and new SCCM

The migration scenario is this:
All Clients are in Domain1 and are managed through SCCM 2012 with System Center Endpoint Protection 2012.
Some of the clients need to join a new domain and be managed through a new SCCM 2012 R2 server with System Center Endpoint Protection 2012 R2.
There are no trusts between the forests. Do we need to uninstall the SCCM 2012 Agent and SCEP 2012 and then install the new SCCM 2012 R2 Agent and SCEP 2012 R2?
Or can we just uninstall SCCM 2012 Agent only and keep SCEP 2012 and later install.

There are multiple ways to go about it.
Assuming that the AD forest is properly extended and the new site's info is properly published, then you can simply run a script:
http://msdn.microsoft.com/en-us/library/cc146558.aspx
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327/view/Discussions
If the two assumptions above aren't correct, then the client has no way of getting the trusted root key gracefully for the new site and running ccmsetup is the best way.
The ccmsetup bootstrapper will download files as needed from the closest DP but (from memory) won't redownload files if they are already present in the ccmsetup folder.
A client push is probably the easiest method to initiate ccmsetup because it can be managed from a central location -- just make sure you select the checkbox for always reinstall. Of course, as mentioned above, if someone has previously used the "group
policy" to assign the site to your clients, you'll need to clean up that mess first otherwise the clients will always try to assign to the old site.
Jason | http://blog.configmgrftw.com

Subincacl tool with netapp cifs migration to new domain

Hello
I have DomainA (old) DomainB (new). i am migrating services from DomainA. to DomainB. i have a netapp filer running CIfS in DomainA. i have two way trust between two doamins. All the security groups have been migrated from DomainA
to DomainB with sid history via Quest tool . now i need to repermission ntfs on all the shares with DomainB. I tried usign subinacl tool with following syntax without success
subinacl /outputlog=c:\output.txt /errorlog=c:\error.txt /subdirectories Z:* /migratedomain=domainA=DomainB=MAPFILE.TXT
where mapfile has a a mapping of between groups of DomainA and DomainB, Z is mapped drive to netapp cifs volume
but it errored out with following
Last Syntax Error:WARNING : /migratedomain=DomainA=DomainB=mapfile.txt : Invalid option : Z:\*

Hi,
Do you run the command from an elevated command prompt? Verify you have proper permission for the mapped drive. Please use the following version of SubInACL.
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23510
For domain migration:
SubinAcl /noverbose /subdirectories x:\*.* /changedomain=DomainA=DomainB
For server migration:
SubinAcl /subdirectories \\Destserver\Share\*.* /migratedomain=SourceServer=DestServer
Best Regards,
Aiden
Aiden Cao
TechNet Community Support

Migrating Lync 2013 to new domain

I have a customer who wants to migrate their Lync servers to a new domain. Is this possible with the existing servers or do I need to backup the config, deploy new Lync servers in that domain and restore the config? Thanks in advance.

New SIP domain or a new Active Directory Domain? You can easily add new SIP domains to the environment. You cannot move a Lync Server from one AD domain to another. You would need to migrate users in a cross forest scenario or backup contacts
and restore.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Migrating 2 domains into child domains in a new forest

I have a unique senario in which my company merged with another.
My Company:
Windows 2003 AD
Exchange 2003 SP3
192.x.x.x
New Company
Windows 2008 AD
Exchange 2010
10.x.x.x
Each domain has its own resources, servers and workstations. For political reasons we still need some management seperation.
My Goals:
Create a new root neutral forest/domain.
Migrate both domains to 2 child domains under this new root
Bring the domain to 2012 R2
Create a single Exchange 2010/2013 cluster with all mailboxes
What is the best way to accomplish this? Where exactly does Exchange sit?
Thanks!

Hi,
>>What is the best way to accomplish this?
In Active Directory, we can use ADMT to do the migration. However, if we need Inter-forest migration from Domain Controller 2003 to Domain Controller 2012, at this time MS
has not ADMT for Windows Server 2012. We can downgrade our forest and Domain functional level to Windows Server 2008 R2, add an additional Domain Controller 2008 R2 and use ADMT 3.2 for migration. After migration is completed, we can demote Domain Controller
2008 R2 and raise again FFL & DFT to Windows Server 2012.
Regarding specific procedures for performing the migration, the following article can be referred to as reference.
Interforest Migration with ADMT 3.2 - Part 1
http://social.technet.microsoft.com/wiki/contents/articles/11996.interforest-migration-with-admt-3-2-part-1.aspx
Interforest Migration with ADMT 3.2 - Part 2
http://social.technet.microsoft.com/wiki/contents/articles/16208.interforest-migration-with-admt-3-2-part-2.aspx
Interforest Migration with ADMT 3.2 - Part 3
http://social.technet.microsoft.com/wiki/contents/articles/16621.interforest-migration-with-admt-3-2-part-3.aspx
>>Where exactly does Exchange sit?
For mailbox migration, in order to get better help, we can ask for suggestions in the following exchange forum.
Exchange Server 2013- Setup, Deployment, Updates, and Migration
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrdeploy
Best regards,
Frank Shen

Migration of SCCM 2012 SP1 to SCCM 2012 R2 in a new domain.

I am wondering if it is possible to migrate objects from a SCCM 2012 SP1 server in one domain to a new SCCM 2012 R2 server in another domain ?
I read this article, but it does not state this particular combination.
http://technet.microsoft.com/en-us/library/gg682006.aspx
Thx
Thomas

For Migrate from SCCM 2012 SP1 to SCCM 2012 R2 in same environment/Domain, it's support and applicable.
But migrate to new domain, it's not support. Also you can't migrate database for new domain or object. you will need to rebuild it.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Migrating Spiceworks to a new domain

Hi,We are currently migrating between domains, and I have been tasked with migrating Spiceworks. I've moved between servers before by exporting the database and re-importing it on the new server, but this is slightly different.The install is AD integrated, and we are moving from one domain to the other. The username structure will be the same but obviously change due to the domain change (e.g: domain1\abc becomes domain2\abc.) However, the email address is staying the same which uses a different domain name which we just use for email.We want to preserve the logged tickets, users logged against tickets, AD logon to the portal, avoid duplication in the people database (e.g: avoid one entry on each domain for each person) and keep the network scan.Is there some sort of conversion tool or script to run to help with this?Thanks,Dan
This topic first appeared in the Spiceworks Community

Hello Spiceworks,Can someone please help with the following situation?I have an email domain set up using Horde (mail.my-company-name.com) and a set of email addresses ([email protected]). I want to migrate all of these accounts to Google Apps for Work, and I also need to migrate the emails, but it is unclear from the Google Help pages ( https://support.google.com/a/answer/6250450?hl=en ) how this is accomplished.More specifically, what will happen when I create a Google Apps for Work for my-company-name.com ? When someone sends an email to [email protected] , will it be received in my new Gmail account or on Horde? Or do I need to change MX records in my hosting control panel for this?Secondly, if I want to migrate the emails from Horde for userx, how do I set it up in Google (since the same [email protected]..

Moving SP2013 and SQL2008R2 to new domain - no trusts between domain

Hello,
I'm looking to move a customized installation of SharePoint 2013 (Microsoft server 2012 std VM) and it's db (SQL 2008 r2 VM) from one domain to another domain. There will be no trust between the domains and assume that no users or service accounts will be
migrated. Has anyone performed a similar operation? If so, can you provide guidance as to the best way to tackle this situation. Currently we plan on exporting the SP2013 VM from the old domain, importing (re-creating) that VM in the new domain and importing
the DB to an existing SQL server in the new domain. My concern is being able to log in to Central Admin afterwards because the domain accounts are no longer valid. Should we change all accounts to local admins first, detach the db and change those accounts
as well? Or would a totally different approach make more sense? Any help would be appreciated..
Thanks in advance,
Alex

You need to build a new SharePoint farm, changing SharePoint server's domain membership isn't supported.
What you'll do is build a new farm, create the Web Application(s), etc. and then restore SQL database backups from the old farm into the new farm.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Use old domain controller AD user profile with new domain (profile changed)

Dear All,
I have built Win Server 2012 for Domain migration from Windows Server 2003 to Windows Server 2012. I have tested all thing on VMware including user creation and tested Domain join using power shell for Win 7 and .VBs batch file for Win XP computers all thing
are working fine.
Let 1st I introduce my current environment. I have existing Win Server 2003 domain controller (abc.com) with 130 client computers and 200 users I am going to plan migrate my current environment to Win server 2012 Domain (xyz.com) Keep in mind that Domain
name is changed but Domain Controller (Server) names are same i.e MY-PDC . I have tested domain join on multiple computers using existing clone of client computers and create all existing users using .csv file and power shell with required
credentials and OU.I am facing the user profile issue when I join domain and login with existing user which was previously the user of same computer the required profile does not login and computer creates new user profile in Document and Settings section
of Win XP.
I need your expert opinions because copy old profile data and create new outlook profile for each user is a big headache for any one. Hope you people can understand and help me in this issue.
Please provide best answer and result on priority I will be thankful to all of you.
Regards,
Arsalan

Hi Arsalan,
Please check if USMT can help you to achieve this target.
User State Migration Tool 4.0 User's
Guide
Meanwhile, please also refer to following articles and check if can help you.
How
to Migrate Windows User Profile to New Account
Keeping user old domain profile
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
If anything I misunderstand or any update, please don’t hesitate to let us know.
Hope this helps.
Best regards,
Justin Gu

Move SP to new domain

Hi all,
I am planning to move my SP server to new domain.
1. Please advise any steps for it.
2. I have some lists that have "User or Group" column which get user name form Active Directory. If we move to new domain, how could we modify those columns?
Thanks all ^_^

Hi Andy,
Here you are the complete steps
http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx
check those links also
http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=194
https://social.technet.microsoft.com/Forums/sharepoint/en-US/20ab9c73-ab38-47d0-a791-8f9004fbe1a4/move-sharepoint-farm-servers-to-another-ad-domain
Kind Regards,
John Naguib
Technical Consultant/Architect
MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
Please remember to mark your question as answered if this solves your problem

Plan migration new domain.

Similar Messages

Maybe you are looking for