HiWe have got a rather strange situation on our hands.We was asked to do a job for one of our clients. They have a windows 2003 domain with a Exchange 2007 exchange x64 running on a DC (for some unknown reason)The problem is that their AD domain don't have an extension like .local, .com or whatever.They asked us to check how to change that, because when they installed the Exchange 2007 they got a warning about that will not be supported for laterversions of Exchange.Our answer was that this means a full move from the old domain with no extension to a new one with an extension.So my question is:Are there any tools or any ways to keep the AD, but extend it to any extension on the domain name?Regards

I am sure this will be bit risky though. I am sure logically it will be as good as renaming the domain. http://technet.microsoft.com/en-us/windowsserver/bb405948.aspxhttp://www.petri.co.il/windows_2003_domain_rename.htmRaj

This is great :=)As we usually follow Best Practice we never came across any reason to dig into domain renaming.Thanks alot for your quick answer.We will try this out as soon as possible

The problem is that their AD domain don't have an extension like .local, .com or whatever.They asked us to check how to change that, because when they installed the Exchange 2007 they got a warning about that will not be supported for laterversions of Exchange. The technical term for this is Single Label Domain (SLD). It is supported with Exchange 2007 and Exchange 2010. However, the Exchange team does recommend not using SLDs.Next version of Exchange and Single Label Domain (SLD) policy under review http://msexchangeteam.com/archive/2009/01/27/450514.aspx Exchange Server 2010 will be supported on Single Label Domains (SLD)While Exchange 2010 is supported with SLDs, the Exchange product team's view is that SLDs are not a recommended configuration, and may not be supported by future Exchange versions. Other Microsoft or third party applications that you want to run in your environment may not be supported on an SLD. This could have an adverse effect on your environment. While we will allow installation of Exchange 2010 in an SLD, we strongly recommend that you take steps to move your organization out of this configuration. http://msexchangeteam.com/archive/2009/10/27/452969.aspx MCTS: Messaging | MCSE: S+M | Small Business Specialist

On Thu, 12-Nov-09 09:20:53 GMT, Jon-Alfred Smith wrote:>The problem is that their AD domain don't have an extension like .local, .com or whatever.They asked us to check how to change that, because when they installed the Exchange 2007 they got a warning about that will not be supported for later versions of Exchange.>of Exchange and Single Label Domain (SLD) policy under review http://msexchangeteam.com/archive/2009/01/27/450514.aspx >>Exchange Server 2010 will be supported on Single Label Domains (SLD)While Exchange 2010 is supported with SLDs, the Exchange product team's view is that SLDs are not a recommended configuration, and may not be supported by future Exchange versions. Other Microsoft or third party applications that you want to run in your environment may not be supported on an SLD. This could have an adverse effect on your environment. While we will allow installation of Exchange 2010 in an SLD, we strongly recommend that you take steps to move your organization out of this configuration. http://msexchangeteam.com/archive/2009/10/27/452969.aspx It may not be a recommended practice NOW, but back in the day (1999,before Windows 2000 RTM) it sure was. There are probably still a fewforests that exist with an "empty root" and a single lable domain thator a company that wasvictimized by that practice.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP