Monday 26 November 2007

Windows Vista - Activation Error: Code 0x8007232b DNS Name does not exist

We are working with Windows Vista Enterprise x64 for our training lab systems.

Right now, we are creating, modifying, and deploying Windows Vista WIM images via network share to get comfortable with the process.

One of the lab systems is in its final resting place, so we went to activate the OS.

This is what we received when we tried:

Windows Activation Error

A problem occurred when Windows tried to activate. Error Code 0x8007232B ... DNS name does not exist.
The error itself is quite cryptic.

Given the mention of DNS, the next step was to watch in ISA to see if indeed there was some sort of blockage happening there. But, we saw absolutely nothing hit ISA when we tried to activate Windows.

So, the next step was to confirm that the ISA Client Firewall was installed and configured correctly which it was. IE showed the correct settings and could browse the Internet with no issues.

After exploring all of the possible physical connection properties we could, we tried a Live Search: Vista 0x8007232b dns name does not exist.

The answer was in the very first hit, a Microsoft Knowledge Base article: KB938107: Error message when you try to activate Windows Vista: "Activation Error: Code 0x8007232b DNS Name does not exist"

As soon as we saw the contents of the KB article, it hit us ... we had setup the WIM image without activating the OS and we were working with Vista Enterprise. There was no MAK entered during the initial setup of the OS we took the image from!

Heh ... one of those silly "Duh" moments. ;)

We clicked the "Change Product Key" link, entered our MAK, clicked on the Activate link, and voila:

Activation was successful

A very valuable lesson ...

Philip Elder
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.


Philip Elder Cluster MVP said...

Not sure about the previous comment. It has been removed.

Anonymous said...

It seems to be a fairly common error that springs up on a number of different Vista installs, and will potentially happen on Server 2008 installs too.

I did a write-up about the nature of the problem at if you want to check it out

Eric said...
This comment has been removed by the author.
Anonymous said...

I had the same problem... and after searching via Google found your blog, I realized I made the same mistake :P
Thanks for the tip!

Anonymous said...