Ack! SBS 2008 Not Genuine!

The situation we find ourselves in right now is a little silly.

Going to download the Hyper-V manager for Windows Vista SP1, the site called for a Windows Genuine Advantage verification.

Okay, we are on a newly built SBS 2008 box with its Server Core Hyper-V partner almost built and ready for the Windows Vista VM installs.

All of the local workstations on this newly set up SBS domain are Windows XP Pro SP3 but not added to the new domain yet. We could install the Hyper-V manager on any of them anyway.

We ran through the WGA which failed of course. It then required that we download the WGA tool and run it to get a key to get through to the download.

Once the tool ran and we got the key, the WGA site choked on the key and stated that we were not running genuine software.

Yikes!

Okay, so we went into the Change Product Key routine and entered the SBS 2008 Open Value license key and ran through the validation. Well, that failed too!

This is getting a bit nerve racking since the last backup was done about an hour ago when we had finished the last batch of updates. We are working on a new server install for a client in Florida.

Since activation was stating that we had to activate today, meaning the server would go catatonic on us at anytime soon, we needed to get this situation resolved or we were recovering the server before we want to.

Nothing in our searches turned up a plausible solution.

However, since we did not enter the product key for the install (we never do until the server goes live), why not try and rearm the “trial” period and see if that corrects the problem.

1. Start –> right click Command Prompt and Run As Administrator
2. cscript %windir%\System32\slmgr.vbs –rearm [Enter]
3. shutdown –r –t 0 [Enter]
4. Once logged on: Start –> right click Computer –> Properties.
5. Click Change Product Key
6. Enter the product key and go.

Eventually, the following will show:

Lesson learned: Never run the WGA tool for any other OS on the server! 8*O

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

SBS 2008 - Eval period is up to 240 days!

The core components of SBS 2008 can hold activation off for a combined total of 240 days.

SQL Server 2008 can only run to 180 day trial period.

Microsoft KB 948472: How to extend the Windows Server 2008 evaluation period.

To check how much time is left in the grace period from the command line:

• slmgr.vbs -dli

The grace period is 60 days in duration. So, on the 60th day or thereabouts, we need to extend the grace period by doing the following:

• slmgr.vbs -rearm

The above KB article has a script that can be set to run automatically using the Task Scheduler.

While automating the trial extension may be a good idea in some ways, it is also very dangerous. Make sure to put a reminder into Outlook indicating that the trial software is coming to the end of its life if the software is somewhere close to a production environment!

Thanks to David Overton on the tip to extend the trial period: How long is the grace period on SBS 2008 (how long can you evaluate SBS 2008 without entering a product key).

One thing to keep in mind: If a client project comes up where they are confirmed to go ahead with SBS 2008, we can install. We will leave the product in trial mode until such time as the client's product key arrives and we can activate with it. We do not need to miss an opportunity, or install SBS 2003 R2 as a bridge measure.

We are so looking forward to going native with SBS 2008 and Server 2008 for our Active Directory, Exchange 2007, ForeFront and Live OneCare for Server, Remote Web Workplace and TSApps, the Group Policy Central Store (about half way down the article), and way powerful Group Policy settings!

Whoo hoo! :)

Oh ... and we are keeping our ISA :D ... we are in the process of securing SBS 2003 R2 Premium Open Value Licensing on a 3 year spread payment structure. Lots of goodies there folks!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

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

SBS 2K3 - Change that product key

In some cases, we need to use our SPLA media's product key to get our base SBS 2K3 R2 Premium install in place.

Generally, it will take about 2-3 days post license transaction with Microsoft for the media to arrive at our client's site.

Obviously, it is our preference to have the correct key in place before activating the OS.

To change the product key if we have not activated the OS we do the following:

1. Start --> Run --> %systemroot%\system32\oobe\msoobe.exe /a [Enter].
2. Click on "Yes, I want to telephone a cust6omer service representative to activate Windows" NEXT.
3. Click the "Change Product Key" button.
4. Enter the new product key in the boxes.
5. Click Update
6. Click Remind me Later or close the activation window.
7. Reboot.
8. Double click on the activation icon in the tray.
9. Activate.

If the server was activated already, then we need to do the following prior to the above:

1. Start --> Run --> Regedit [Enter]
2. Navigate to: HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current Version\WPAEvents
3. Right click on OOBETimer and Modify.
4. Change any one digit to deactivate Windows.

Once the server has been rebooted, activating the server on the client's actual key is good to go.

If the server was already activated, it should indicate that it is activated when running msoobe.exe /a after the above steps.

Link:

• MS KB328874: How to change the Volume Licensing product key on a computer that is running Windows XP SP1 and later versions of Windows XP

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

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

Server Core - Activation Error 0x8007232B

When we went to activate our Open License version of Server Core, we ended up with the following error:

Activating Windows Server(R), ServerStandardCore edition (xxx-xxx-xxx-xxx-xxxxx) ...
Run 'slui.exe 0x2a 0x8007232B' to display the error text.
Error: 0x8007232B

That error has been encountered before.

Server Core: Error 0x8007232B

The error was encountered when we went to activate our Open Licensing version of Windows Vista: Windows Vista - Activation Error: Code 0x8007232b DNS Name does not exist.

In the case of Windows Vista, it was because we installed Vista without a product key.

Well, when installing Server Core, no product key was requested and we are not using the unattend file to install yet.

So, the challenge now becomes, how do we get that key in there and activate the product?

The command we ran to attempt the activation was:

slmgr.vbs -ato

A little searching was required in order to find the right command line commands.

We found them on Sander Berkouwer's blog "The things that are better left unspoken" Activating Server Core.

The commands are as follows:

1. start /w slmgr.vbs -ipk ABCDE-FGHIJ-KLMNO-PQRST-UVWXY
• Format of the product key should be exact
2. start /w slmgr.vbs -ato

If the activation process is successful, one will see:

Product activated successfully.

This process will also switch the Activation process from KMS to MAK which is the preferential activation method for us.

We were now able to go on and discover how to install and setup Hyper-V, configure the built-in firewall for remote management and Hyper-V management, and all sorts of fun stuff that we need to discover at the command line! ;)

The Server Core command line sure is both refreshing and challenging at the same time.

It brings back memories of the challenges of doing things like setting up the AutoExec.bat file for memory management to squeeze the most conventional memory we could (my personal record was 614KB) to get those games up and running.

Other very exciting and fun stuff in the DOS command line were things like getting the TCP/IP networking configuration to actually work and prepping a system for a Windows 3.xx install! :D

Resources for Server Core are out there, but are still rather spotty due to the newness of the OS.

We have one book on the subject so far, which is in the process of being read and evaluated.

Here are some resources on Server Core:

• Server Core Team Blog
• Server Core on TechNet
• Server Core on MSDN
• Server Core video by Keith Combs
• Sander Berkouwer blog: The things that are better left unspoken

Server Core is definitely a neat OS option in Server 2008!

And, it is looking like the same VMs that ran on W2K3 R2 hosting Virtual Server 2005 R2 SP1 are a lot faster on similar equipment in Hyper-V installed on Server Core. Having the option to specify the number of cores per VM is a pretty neat feature and can be very handy for things like hosting server OSs.

More to come and thanks for reading! :)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

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

The most terrifying moment in 2007 ...

Our data mule system has a lot of software tools loaded on it for the various tasks we require of it.

Recently we swapped out the Intel DG945 based board for an Intel DQ965GF running an E6600 Core 2 Duo.

The Pentium D 945 just wasn't cutting it anymore for the multiple tasks that can be running on the system at the same time.

The hardware swap caused Windows XP Pro to hiccup an activation request which was expected.

However, Symantec's Norton Ghost also coughed up an activation request. When we entered the key on the back of the CD sleeve it refused the key. Nothing we did could fix it and we just did not have the time to mess with it.

So, we called Symantec Support. The last time we did that, the script jockey (front line support) had us repeatedly delete registry keys all the while warning us that any modifications we were making may kill our system! Needless to say, we did not follow their directions while managing to decipher which keys we really needed to kill from their instructions.

Well, this time around the support call took us to a Symantec micro support site:

Connect to Support

After punching in the given code, the support person was able to take control of the system.

While the data mule may not be the prettiest thing to look at - the MB, PSU, HDD and extra USB ports are all mounted to an old Compaq desktop case cover - the system is business critical.

MPECS' Data Mule System

We do all of our imaging, virus cleansing, data transfers, and DoD style hard drive wipes (up to 11 SATA drives simultaneously), and more on this system.

So, surrendering the wheel to an unknown was not an option. The support person was completely grilled before allowing them to go anywhere on the system. There was no way someone reading from a script was going to proceed.

Fortunately, the person on the other end of the keyboard and mouse had a pretty good grasp of the product and the methodology needed to fix the problem. After monitoring their progress for while, we were able to work on other bench related tasks so as to could keep an eye on the Data Mule screen.

They ended up using the Norton Removal Tool, rebooting, cleaning out the registry and the software's folders, rebooting and reinstalling Ghost. The activation process was able to work after that. They were on the system for about 60-90 minutes.

Their remote support tool automatically reconnected to the support session after we logged in.

Doesn't that experience, and the gut reaction, say a lot about how we perceive manufacturer's penchant to save pennies by off shoring?

It is truly sad that, from where we sit, some companies just do not seem to care about anything beyond the initial sale.

And for us smaller I.T. support folks, it better be a lesson: Never ever leave a client high and dry after the sale - no matter what happens ... Be there for them!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

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

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
MPECS Inc.
Microsoft Small Business Specialists

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

Windows Vista - Activation issue after 30 day period expires

We ran into an Activation problem on Windows Vista, or at least we thought it was a problem. ;)

The issue turned out to be a situation where a machine that is being used to test various hardware and software components on Vista hadn't been used in a while.

It was installed with no product key as it wasn't expected to be used beyond a couple of weeks.

When the machine was turned on, we received the following message:

This copy of Microsoft Windows is not genuine.

The online resolution installed the Genuine Advantage tool which also had an error:

The validation service is unable to determine whether this copy of Windows Vista is Genuine.

Of course it isn't, we hadn't inputted a product key when the OS was installed. At least, that was what we figured out as this machine has been sitting for quite a while. It wasn't supposed to be in service anymore as it is one of our Vista test mules.

So, if you get the above errors, then more than likely a product key was not used on the initial installation of the OS and the Activate over the Internet option was unchecked.

You will need to wait for Windows to prompt you for Activation:


As things like the Control Panel will be disabled or very hard to get to. At least in this case, that is what happened. It was tough to get around.

But we did it, and yes ... it was one of those days! ;*)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists