<div>
Thanks.<br />
main reason is the customer has re-branded the company name and they want to remove all aspects of the old companyX.local domain, we are looking at doing it this way as we thought this would be the most logical and supported way of getting the job done.<br />
<br />
Your thoughts?
</div>


<div>
What is the advantage of changing domain name ?<br />
If your current DCs are messed or not healthy then you can think of it. &nbsp;Still if not healthy cross forest migration will be more complicated to contact between old DC and new DC.<br />
<br />
If you are keen on migration, go ahead. But it will not make difference for a user (just profile reconfiguration). &nbsp;It will give big headache to admin for certain period of time.
</div>


<div>
The domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010. DNS domain rename is supported in Exchange Server 2003. However, renaming of the NetBIOS domain name is not supported in any version of Exchange Server. Other non-Microsoft applications might also not support domain rename.<br />
<a href="http://social.technet.microsoft.com/wiki/contents/articles/1347.renaming-a-windows-server-2008-active-directory-domain-dsforum2wiki.aspx" rel="ugc nofollow">http://social.technet.microsoft.com/wiki/contents/articles/1347.renaming-a-windows-server-2008-active-directory-domain-dsforum2wiki.aspx</a>&nbsp;<br />
<br />
so solution for you concerns is below<br />
refer:<br />
<a href="http://www.msexchange.org/articles-tutorials/exchange-server-2010/migration-deployment/uncovering-impacts-domain-rename-exchange-server-2010-sp1.html" rel="ugc">http://www.msexchange.org/articles-tutorials/exchange-server-2010/migration-deployment/uncovering-impacts-domain-rename-exchange-server-2010-sp1.html</a>
</div>


<div>
Hi mfg1,<br />
<br />
To minimize downtime use CodeTwo Exchange Migration: <a href="http://codetwo.com/exchange-migration/?sts=5851" rel="ugc">http://codetwo.com/exchange-migration/?sts=5851</a><br />
<br />
The application will replicate mailboxes to the target domain without interrupting their availability.<br />
<br />
Best regards,<br />
Adam
</div>


<div>
Hi Muzafar I already understand that rendom is not supported, that is why we are looking at a cross forest migration.<br />
<br />
UPN suffixs are not really getting away from the problem either, I looked at this a while ago but it still stands the domain is still &quot;olddomain.local&quot;<br />
<br />
If I had a way of convincing the customer to keep the existing domain name I certainly would but they simple insist it must be changed.<br />
<br />
Correct me if I am wrong I found this article on getting the job done, I will draw out how I would like to run things but just need to know if this will run well until everything is migrated?<br />
<br />
Your advise is appreciated<br />
<br />
<a href="http://www.careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-35288" rel="ugc">http://www.careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-35288</a>
</div>


<div>
<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1090020/migration.png" target="_blank" class="file-inline" title="Diagram (18 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>migration.png</a>
</div>


migration.png

<div>
that perfect... you can go ahead with the POA...even the link is also helpful <br />
<br />
just to summaries<br />
<br />
1) Setup a new domain &amp;&nbsp;exchange env<br />
2) enable the trust<br />
3) migrate the users &amp;&nbsp;mailboxes to new domain<br />
4)migrate the Computers<br />
5)Migrate the member servers, file server...etc<br />
<br />
thats it.. :)<br />
<br />
ensure you have a proper backup in place before making any progress on migration sequences.
</div>


<div>
I think I will replicate my setup and do this in a lab environment first.
</div>


<div>
Thanks Kent your first link is the same one I found, I am looking next week to test this out and see how I get on, hopefully it will go ok.
</div>


<div>
thanks guys, fingers crossed my testing will be successful.
</div>


<div>
<div class="content wysiwyg-content">
Hi I have a 2008r2 domain with 3 DC's, I also run exchange 2007 at the moment, if I create a new 2012r2 domain will this guide work ok?<br />
<br />
I have around 200 users as well and the main reason for this is they want to change the domain from what it is currently as its the old company name, with a 200 user/mailbox setup roughly how long would you expect this to take and is there much downtime incurred with doing it this way?
</div>
</div>


Hi I have a 2008r2 domain with 3 DC's, I also run exchange 2007 at the moment, if I create a new 2012r2 domain will this guide work ok?

I have around 200 users as well and the main reason for this is they want to change the domain from what it is currently as its the old company name, with a 200 user/mailbox setup roughly how long would you expect this to take and is there much downtime incurred with doing it this way?

Cross Forest Migration from 2008R2 domain to 2012R2 domain

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.