This is the first error I get when I try to install SP1 for Exchange 2007. Anyone know how to resolve it?"Microsoft Exchange Server 2007 setup cannot continue because this computer belongs to a domain that has a single-labeled DNS name. DNS domain name:xxx"

Ptex wrote: This is the first error I get when I try to install SP1 for Exchange 2007. Anyone know how to resolve it?"Microsoft Exchange Server 2007 setup cannot continue because this computer belongs to a domain that has a single-labeled DNS name. DNS domain name:xxx" I am having the same issue.. Anyone know of a way to fix this? Please help. Thanks

When installing on the Edge Transport role make sure the primary DNSsuffixof the computer is set to your domain. This property setting is available under System Properties, Computer Name, Change, and More.

I have the same issue.It sounds like I need to rename our domain from ourdomain to ourdomain.local or something that isn't single-labled. However per this KB artical you can't rename a domain if you have an exchange 2007 server:http://support.microsoft.com/kb/925822/en-us I can't find any referance to Exchange 2007 or SP1 Requiring a non-single-labeled domain. If that was a requirement for Exchange 2007 why was I able to install it at all, and if that is a newly added requirement for SP1 then MS needs to provide a way for Exchange 2007 users to rename their domain.

No, I have no Edge Transport role installed.

I'm having the same issue. So far, nothing but problems with Exchange Server 2007, sheesh.

Same problem with my domain. Any suggestions yet?

Same problem here, trying to upgrade from Exchange 2007 to Exchange 2007 sp1 and prereq fails due to my single label domain name. I knew this would eventually bite me. The single label domain name is a carry over from NT or before, definitely before my time here. But I never had sufficient cause to wade the scary waters of a domain name change. So far non of the consultants I have talked with have actually done a production domain name change.

Same problem here. Single label domain comes from NT4 days and needless to say changing the name scares the *** out of me as we've got over a dozen domain controllers spread across the state. Exchange 2007 has been installed for about a month and has been working quite well, but I'd like some of the added management GUI and public folder functionality in SP1. There's gotta be a way to get this done without renaming the domain.Needless to say I'm surprised to come across this issue because it allowed me to install Exchange 2007 without any problems.-Matt

After 12 hours of support from Microsoft here is what they told me. " As discussed on phone, Exchange does not support a single-labeled domain but the setup does not block it and can set up Exchange successfully. Later we may see weird behaviors. Also Exchange SP1 does not support single-labeled domains. Below are the workarounds: -Change Domain name using Domain Rename Tool -Build Domain from scratch -Create a new domain and migrate AD using ADMT " There appears to be a bug in the RTM software they does not notify you that you have a "single-labeled" domain. It installs but doesn't work properly. SP1 will not install. Good luck everyone!

This sucks. We don't have any issues at all running Exchange 2007 with a single labled DNS name. Microsoft needs to remove that requriement from SP1 or at least give us way to rename the domain on an exchange 2007 server.As far as I can tell all of thoes work arounds require a new exchange install, which means a second 64bit server and a less than fun migration process. Renaming the domain sounds like the easiest solution (as least in a simple domain) but per http://support.microsoft.com/kb/925822/en-us you can't rename a domain that includes exchange 2007.

Honestly, this is ridiculous. I did a pretty fair amount of reading before installing Exchange 2007 and nothing I came across mentioned a single labeled domain as a show stopper. I've been aware that it wouldn't be advisable to build a new domain with a single label name, but renaming an existing domain scares me. Not even the Exchange 2007 Readiness tool warned me. Now I'm excited to have everything up and working fine and I go to apply the service pack and get this? Renaming a production domain with 500 PCs and a dozen domain controllers scattered around the state doesn't seem like my idea of a fun time. Nor does creating a new domain and migrating. Help us out here MS!

All great ides for lab servers. But I'm not sure that I would like to have that kind of fun on production servers. I try to keep everything going with little disturbance to users and their work.

Still not working?

I have a client with a similar issue. A new domain with ADMT seems like the only possible option, butthats pretty extreme. I'm also unable to believe that Microsoft no longer supports domain renames with their 2007 products. I anticipate the resolution to come from advancements in rename tools before they actually change anything with E2k7.

What do we need to do to get Microsoft to change this. It's simply unacceptable. They screwed up, so they need to provide a solution. They should have at least warned us before installing E2K7 to begin with. Having to create a new domain, transfer over the AD data, and then recreate an Exchange Server would take waaaay too much time!

I totally agree. There is no documentation about this limitation that I can find.Unfortunately it doesnt seem we are getting any traction. No response from MS her or on the exchange blog (http://msexchangeteam.com/archive/2007/11/29/447611.aspx). Not sure where to go from here

Will I not get support if I can't install SP1?

Hi,I believe MS will support the RTM version for a while, but they will make SP1 a must at a later stage.The problem in your case you are already running a none supported setup if you have a single-labeled domain. I am not sure how Microsoft will deal with your non supported Scenario. I have found out another forum discussing this same issue and might be helpfull: Exchange Server 2007 SP1 on single label DNS Domain NameI hope that has been helpfull.

We went ahead with the domain rename. Overall it went smooth. We had a couple issues with Live Communication Server and the CA, but they was easy to fix, just uninstall, reinstall, and for LCS re-register the users. Here is what MS Support send me for the domain rename. Good luck everyone! -Jason ----- Problem Description / Questions We would like to rename a Windows 2003 domain and install Exchange 2007 on it and would like to be aware of the known issues. Solution Since you are installing Exchange 2007 on the domain after the rename process, there should be no issues with it. However, here are a few articles that should help you with the rename process - Windows 2003 domain rename tools - http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx (Please check the downloads section on the left) Error messages encountered on renaming domain - http://support.microsoft.com/kb/891370 Webcasts on domain rename - http://support.microsoft.com/kb/819145/ What is domain rename - http://technet2.microsoft.com/windowsserver/en/library/996741d8-28e4-4d20-9949-8f17fb9d3cfd1033.mspx?mfr=true How domain rename works - http://technet2.microsoft.com/windowsserver/en/library/4d0c3b6e-e6f5-4ab3-9d81-106ae3a715491033.mspx?mfr=true Additional Reading - Use the domain rename fixup tool for Exchange - http://support.microsoft.com/kb/842116 Download the XDR-fixup tool - http://www.microsoft.com/downloads/details.aspx?FamilyId=24B47D4A-C4B9-4031-B491-29839148A28C&displaylang=en Webcasts on the domain rename process - http://support.microsoft.com/kb/838623 (With Exchange) Issues with Exchange when renaming domain - http://support.microsoft.com/kb/822590

Thanks for your contribution JCaspersen, but we are not in need advice on domain renames. Everyone here has already deployed E2k7 under a supported scenario (vmguru007 is incorrect, it was supported, just not advised), and now Microsoft has deemed it unsupported after we are all in production. We need guidance on what do do with scenarios using single-label Post E2k7 RTM deployment.

Still no love from Microsoft?

They must be working on it. Can't wait until we get a fix.

There has been a post to the Exchange Team Blog http://msexchangeteam.com/archive/2008/01/17/447869.aspx Please have a look at it, and make any comments there. Ed Beck Supportability Program Manager

This is great news lets hope something comes from it.

Yes, this is GREAT news! It's what we've been waiting for. PLEASE post your answers to the questions from their blog to help them with a fix. The more response, the more urgent it will be for them! . Thanks again Ed.

Found this artical on the web. Could be a solution. I'm going to wait until after the 15th to see what MS has to say though.http://www.outlook-web-access.com/component/content/article/35-faqs/187-how-to-install-exchange-2007-sp1-in-an-environment-with-a-single-labeled-dns-name

Good find! I wonder if this just delays the problem, though. When sp2 comes out, will we have a whole bunch of new issues?

I worked with MS for about a month on this and my biggest gripe with them was this being undocumented until the final release of SP1. I have the old docs and there is no mention of it. And you are right there will be a SP2.Now honestly I shouldn' t have a single label domain, but I inheritedit.WehavesomanymobileusersandonceIfinallygotthedomaintothepointitcouldberenamedIreallybackedoff.Myexperiencewithdomainrenamehasbeenlessthangood.I'm hopeful MS introduces a simplified domain rename process that isn't so troublesome.

I'm in the same situation. MS says "its always been unsupported" and they reference the sp1 release notes as their proof! But of course, that documentation didn't exist pre-sp1. Anyway, I understand the scalability issues of SLD's but in a small group, Im inclined to use that registry hack to proceed. Im just worried that when sp2 comes out there won't be as an easy work around, or perhaps there will be more than scalability issues, perhaps new features or whatever dependant on non-sld's. But of course I will wait until the 15th to see what the final answer is.

I am running into a similar issue as you all are. I have a domain with an _ in it. Fortunately for me the Exchange 2007 install halts on an error stating the Domain contains characters other than A-Z blah blah blah. So now I am faced with an entire Domain Name Change to remedy this problem. Obviously that isn't a light task and will eat up a weekend to do so. I wish you guys the best of luck, and would ask that Microosft better quality control their software. Even though it makes no sense why the installer is stopping my installation. At least it stopped it for me. Where as you guys are stuck in limbo. Lets get a fix for this MS, a lot of wasted time hangs in the balance!

Make sure you post on the msexchangeteam.com site, under the earlier link to the SLD article. thats where they asked for feedback.

We've posted the follow-up to the original post. Please see http://msexchangeteam.com/archive/2008/02/15/448140.aspx Ed Beck

GREAT!!!!!! "After investigating Exchange 2007 Service Pack 1 installed in an Active Directory domain with a Single-label Domain (SLD) name, Microsoft has changed the Setup prerequisite rule for SLDs from an Error to a Warning, thereby allowing Service Pack 1 installation to continue in SLD environments..." http://msexchangeteam.com/archive/2008/02/15/448140.aspx

I still error out as a SLD? Has this fix not happend yet?

per the msexchangeteam.com post the new version wont be out for a few more weeks. rtfa

i get this error [WARNING]Setup cannot detect an SMTP or Send connector with an address space of '*'. mail flow to the internet may not work properly my domain has .local on the end i try and continue the install and when it gets to the the Hub Transport Role the install fails by not being able to start the Microsoft Edge Transport Service this is on server 2008 RTM any ideas anyone ?

you should start a new thread for new issues... It's saying that you don't have a send connector to send mail to the internet for *. this means all. it implies that your send connectors only have specific domains listed. but start a new thread. everyone in here is talking about single label domain names.

I must say this is breathtakingly lame. I know that now SP1 only warns about sld's and doesn't throw an error, but this is basically: "Hey we don't support single level domains." "Wow, bummer, ok well I'll change it to be fully supported. How do I do that?" "We don't support changing either." Add my voice to the chorus of netadmins that want a tool to change the domain with exchange 2007. I too am caught with my predecessor's mistake of not changing the domain before exchange 2007 wasinstalled, now I have to completely remove exchange to change. At least I'm small enough to have that option.

While I too have clients in this situation, the best advice is to keep on truckin with your SLD and when it comes time to consider the next migration, use ADMT to migrate your users to a fresh domain. The real problem here isnt that Microsoft doesn't like SLD's its that they allowed it prior to sp1 and prevented people from upgrading. Now that you can't possibly make the same mistake with the next version of Exchange, you should just include ADMT and a new domain as part of your migration plan (in a few years, or whenever the next version of Exchange is released).

Hi Guys, Newb so be gentle! Thus far I'm only working on our developer system so I currently have breathing room to muck about so any and all ideas are welcome!! OK, I've just been working to upgrade Exchange 2007 with SP1, went through the prerequisites and got them installed OK, ran the SP1 install, went through the checks and then clicked Upgrade, about 2/3 of the way through the install a dialogue comes up informing me that the event log file is full, I clicked OK to that dialogue after copying the text intoa text file, I just had time to notice that just over half the tasks in the SP1 install windows were listed as 'Completed' whilst the restwere shown as 'Cancelled', before I could dump the screen the box vanished (due to eager-finger-trouble on my part I suspect). I've been through the event logs and have cleared them all down and boosted their sizes so hopefully the problem wont re-occur. Anyway, my gut feeling is that the SP didn't get applied correctly or fully, howeverwhen I try to reinstall SP1, Exchange behaves as though I'm trying to perform maintenance on the actual install so it seems to think it's been upgraded to SP1 correctly, SP1 does not appear in the Add/Remove programs list so I can't peel it back from there, is there anyway that I can get the SP off now so I can re-apply it and have a nice feeling that it went on correctly. Alternatively, is there a sure-fire way to determine if the SP did in fact get applied correctly? Anyadvice much appreciated. Cheers Adam

Hi All, I have got a similiar problem. I have one Windows 2003 forest with Windows 2003 domain. The domain is SLD. There is no Exchange server installed, nor ever been. I've ran an Exchange 2007 SP1's "setup /p". After running setup to install Exchange roles, I've got an "SLD issue" warning. I cancelled the setup. I want to rename the domain now. However, I've read that after running "setup /p" it is not possible and I have to migrate to new forest. I can't do this because of number of client pc's to migrate. Could anyone clarify if I can do the rename or not? If not, Why, what is the problem? The Schema update, Exchange containter created in domain partition, ... or is there any workaround? Thanks a lot for helping in advance, regards -- Martin Necas

So /p is short for /prepareAD.PrepareAD actually does two commands: /PrepareSchema & /PrepareLegacyExchangePermissions Read here for details on each of those switches: http://technet.microsoft.com/en-us/library/bb288907(EXCHG.80).aspx Additionally, when the /PrepareSchema switch is executed, these changes are made to the schema: http://technet.microsoft.com/en-us/library/aa997467(EXCHG.80).aspx& http://technet.microsoft.com/en-us/library/bb738144(EXCHG.80).aspx So, what this means is, you cannot simply remove Exchange from the Services container via adsiedit. However - your question was: does this actually prevent you from renaming your domain - what is the point of no-return with Exchange 2007 setup? THAT I don't know! I'll look around and if I find something I'll post back, but I am very curious. Do you have a virtual environment you can test with? Were you asked to name your Organization? I'm feeling optimistic about a rename, since most of these extensions are generic in nature...

Mike, Thank you. (I had to edit my reply to you, I did not read ituntil end and were quicker in replying than in reading :-)) I have run "setup /p /on:[organization name", so I have specified the Organization name. I took a look at the AD, and there is new Exchange security groups & containers created (in the config partition). The main problem is, I have to figure it out before today's evening, which is in 3-5 hours. I have got an backup of Domain controllers, however I worry about workstations after something will go wrong with rename. Maybe the virtual environment is the best to figure that out. -- Martin Necas

yeah, use vm if you can. if you have a spare server microsoft recently announced their hyper-v is a free download! once you figure it out, please post back. im interested in learning what "the point of no return" is.

Good news! It is working! I've renamed the SLD domain to full by adding .local suffix. Then renamed the domain controllers itself (added .local DNS suffix). Everything went ok. Then I deleted Exchange security groups, Configuration container from domain and configuration partition. Then ran the Exchange setup, both the domain preparation and install of role itself went OK. Some statements at the blogs or official technet pages make confusion. After realizing, found this in reply to my same question in other forum here: http://theessentialexchange.com/blogs/michael/archive/2008/04/04/exchange-2007-and-domain-rename.aspx Thank you for pointing -- Martin Necas

Looks like the next version of Exchange may continue to support SLD's even though its still not advised: http://msexchangeteam.com/archive/2009/01/27/450514.aspxMike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

Mike Crowley said: Looks like the next version of Exchange may continue to support SLD's even though its still not advised: http://msexchangeteam.com/archive/2009/01/27/450514.aspxMike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging AdministratorThats great but I would like to see a tool to just fix the issue, with out having to uninstall Exchange. I Just had a server go down and I'm getting a new server I would love if I could install it without a SLD. But if that means uninstalling Exchange I can't do that.

You dont have to uninstall Exchange... The rule checker has been updated and no longer prevents installation.Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator