Power BI

Content by Charles Sterling

Windows 7 Release Candidate Ultimate: Adding a machine to a Domain Broken?

With Visual Studio 2010 Beta1 now becoming mainstream i needed to format my work laptop to be able to install it natively –as there was no install for the previous VS 2010 CTP.  

Friday i download the Windows 7 RC ISO then realized i didn’t have a DVD burner on my laptop.  Too Lazy to get off the couch i downloaded Virtual CloneDrive(Very nice!)  watched an episode of Simpsons and it was done! 

During the commercial break i kicked off the install of Visual Studio 2010 Beta1 after the two episodes of Phineas and Ferb (Natasha my 8 year old daughter was running the remote) and it too was done with no errors.  Pretty cool considering i just installed two beta Microsoft products back to back!

Of course the first thing i do with this machine was try to add it to the domain on the Microsoft corporate network…the same i have been doing for the last !5 years.  Unfortunately my tried and true:

Right click the computer choose properties, select change settings and select the button:

“To Rename this computer or change its domain or workgroup, click change”



Typed in “Redmond”


Where i would normally would expect to get a prompt for my credentials i received an error…hmm…


So i applied updates to see if it was quarantine issue –nope .

I rebooted – which typically fixes everything else – Nope

Then just for grins i take a look at my ipconfig and noticed the DNS information has all Redmond.Microsoft.com suffix information ….hmm…

Okay so i try adding that as my Domain name and SUCCESS i am prompted for credentials!! – Yeah!

Then at the credentials dialog I tried Redmond.Microsoft.com\chass and my password…Failure- boo!

The reason was bad user account/password!  ..hmmm..


Switching back to the time proven domain_name\User_name worked like a charm –in this dialog- YEAH!!!



Now i don’t know if this is a change to Windows 7 RC (definitely didn’t behave this way at the last Beta) or a change to our internal network but even if it is just our internal network hopefully this will save some other blue badge some time!





(I am including the error dialog below for Search engines)

Note: This information is intended for a network administrator.  If you are not your network’s administrator, notify the administrator that you received this information, which has been recorded in the file D:\Windows\debug\dcdiag.txt.

The domain name "Redmond" might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "Redmond":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.Redmond

Common causes of this error include the following:

– The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:


– One or more of the following zones do not include delegation to its child zone:

. (the root zone)