Hello @Fusionized ,
Thank you for posting here.
Here are the answers for your references.
Requirements for Domain Rename
Before a domain rename operation begins, the following requirements (but are not limited to) must be met:
1.The forest functional level must be Windows Server 2003 or higher.
2.If the position of domains will change, trust relationships must be created to provide trust between any domain that will be renamed (and therefore repositioned) and the domain that is to be its parent in the new structure.
3.DNS zones must exist for the new domains.
4.Domain-based Distributed File System (DFS) folder redirection paths must be redirected to a server-based path.
5.Domain-based roaming user profiles must be relocated to a server-based share or stand-alone DFS path.
6.Computers in the to-be-renamed domains must be configured to change their host names to reflect the new domain names.
7.Certification authority (CA) requirements must be met.
8.Location of the Domain – in forest it can have different level of domains. Those can be either complete different domains or child domains. If you going to change the location of the dc in the forest you must need to create trust relationships between domains to keep the connectivity.
9.DNS Zone – DNS Zone files must be created for the new domain name prior to the rename process in relevant DNS servers.
10.Computer Name Change – Once the domain is renamed the computers host names will also renamed. So if those are configured to use by applications or systems make sure you prepare to do those changes.
11.Once your infrastructure is ready, to perform the rename process we need an administrative computer or server. It must be a member of domain and should not a DC. It must have “Remote Server Administration Tools” installed.
12.Exchange Server Incompatibility
The domain rename operation is not supported in Microsoft Exchange 2000 server,Microsoft Exchange Server 2007 or Exchange Server 2010,Microsoft Exchange Server 2013.
DNS domain rename is supported in Exchange Server 2003 with Service Pack 1 (SP1). 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.
There are also non-Exchange applications that may be impacted, but Exchange is emphasized because email is often the most utilized form of communication and would be impacted most if you were to perform a domain rename. Also, renaming the NetBIOS domain name is not supported in any version of the Exchange Server. Lastly, keep in mind that non-Microsoft applications may also not support a domain rename.
If you perform an AD rename with an unsupported version of Exchange, you will need to create a new AD forest, install Exchange into the new forest, and migrate all the objects. However, this process is very time intensive and many not be realistic to undertake.
**Q1:**We have a running internal Certificate Server-probably even AD integrated--> How is this certainly recognizable?
A1:We can refer to the part of "CA Requirements" in the following link "How Domain Rename Works" and "Prepare Certification Authorities".
How Domain Rename Works
Prepare Certification Authorities
**Q2:**What's with the AD-integrated KMS licensing?
A2:I am sorry, after a lot of my research, I cannot find the affect on AD-integrated KMS licensing after domain rename.
We can consult our question by opening a new post and selecting Windows 10 general tags.
**Q3:**DFS is used --> What is there to consider?
A3:
1.Domain-based Distributed File System (DFS) folder redirection paths must be redirected to a server-based path.
2.Domain-based roaming user profiles must be relocated to a server-based share or stand-alone DFS path.
3.We can refer to the part of "Folder Redirection and Roaming User Profile Requirement" in the following link.
How Domain Rename Works
**Q4:**Microsoft 365 is operated from the local Active Directory with the help of AD Sync --> What is there to consider?
A4:We can consult our question by opening a new post and selecting Azure or O365 tags.
**Q5:**SQL Server work with Domain user -->What is there to adjust?
A5:We can consult our question by opening a new post and selecting SQL tags.
**Q6:**What does the rename mean for the SCCM?
A6:We can consult our question by opening a new post and selecting SCCM tags.
**Q7:**Which causes does the rename have for f.e. helpingtools such as NetFX?
A7:You can use the domain rename process to change the names of your domains, and you can also use it to change the structure of the domain trees in your forest. This process involves updating the Domain Name System (DNS) and trust infrastructures as well as Group Policy and service principal names (SPNs).
The ability to rename domains provides you with the flexibility to make important name changes and forest structural changes as the needs of your organization change. Using domain rename, you cannot only change the name of a domain, but you can change the structure of the domain hierarchy and change the parent of a domain or move a domain residing in one domain tree to another domain tree. The domain rename process can accommodate scenarios involving acquisitions, mergers, or name changes in your organization, but it is not designed to accommodate forest mergers or the movement of domains between forests.
**Q8:**What does the rename mean for 802.1x authentification in the WLAN?
A8:We can consult our question by opening a new post and selecting Network or WLAN or 802.1x authentification tags.
**Q9:**What about the changes to vSphere and VEEAM?
A9:We can ask engineers of vSphere and VEEAM for help.
**Q10:**How does a print server actually react to the name change?
A10:We can consult our question by opening a new post and selecting printer tags.
It seems your AD environment is more complex, it is recommended you would probably just create a new domain, and move or migrate everything to new domain using ADMT tool if needed.
Hope the information above is helpful.
Best Regards,
Daisy Zhou