“Change product key” link is not available in Windows 8 or in Windows Server 2012

When you try to change the product key in Windows 8 or in Windows Server 2012, you cannot find a “Change product key” link in the System item in Control Panel.

For example, you want to convert a default setup product key to a Multiple Activation Key (MAK) on a computer that is running Windows 8. However, you cannot find an element in the UI that lets you change the product key.

To change the product key without first activating Windows, use one of the following methods:

Method 1

  1. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
  2. In the search box type Slui.exe 0x3.
  3. Tap or click the Slui.exe 0x3 icon.
  4. Type your product key in the Windows Activation window, and then click Activate.

Method 2
Run the following command at an elevated command prompt:

Cscript.exe %windir%system32slmgr.vbs /ipk

Note You can also use the Volume Activation Management Tool (VAMT) 3.0 to change the product key remotely, or if you want to change the product key on multiple computers.

Windows Server 2012 Failover Cluster Virtual Fibre Channel Adapter Live Migration Error

I’ve got a multiple  node cluster running Windows Server 2012 with Brocade 415/815 4G/8G FC HBA’s connecting to a VX SAN. I am trying to get the virtual HBA’s working in Hyper-V Guest running Windows 2008 R2 (SQL Cluster). I first created 2 virtual SAN Switches one connected to each port on my physical HBA (each physical port connects to a separate fabric). I add two Virtual HBA’s in my Guest, one to each VSAN Switch. When I go to Zone the HBA’s I only see side A of the virtual HBA’s not both A and B. On each fabric I should see two (A and B) WWPN but I only see one, to solve this you must shut down the Guest OS and twist the address set name (copy Set Address A to  Set Address B  and Set Address B to Set address A) I can add disk and everything works, however when I go to Live migrate I get the following error due to side B not being zoned. Live migration of ‘Virtual Machine Win2012_01’ failed.

Virtual machine migration operation for ‘Win2012_01’ failed at migration destination ‘hv-cl07-c2’. (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

‘Win2012_01’ Synthetic FibreChannel Port: Failed to finish reserving resources with Error ‘Unspecified error’ (0x80004005). (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

‘Win2012_01’ Synthetic FibreChannel Port: Failed to finish reserving resources with Error ‘Unspecified error’ (0x80004005). (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

To solve this problem, I have done the following:

  • Updated my drivers to the latest version (3.0.2.21)
  • Remember that the Virtual SAN path must be the same, for example when you create 2 paths then the VSAN A should always connect to FiberSwitch 1 and VSAN B should connect 2 Fberswitch 2. This is because when you try to live migrate the guest OS and the VSAN paths are different the fiberSwitch cannot build the connection.
  • My problem was however that I only had created one host on the SAN and configured all the 8 paths under one host, to resolve my problem I created one host for the address set A and one host for the address set B. So I have always one connected and one disconnected host on my SAN and when I am doing a Live migration then the both hosts are online

I hope that this will solve your problem to.

Best Regards,

Pouyan

 

Using PowerShell as the Shell on Windows Server Core

With PowerShell becoming one of the most important tools in a Windows administrator’s tool bag as well as really becoming the best prompt to use on Windows Server Core, I thought it was about time I documented how to change the command prompt that opens when you log into Server Core with a PowerShell prompt.

To complete this requires two steps:

  1. Enable/Install PowerShell on the Windows 2008 R2 Server Core computer
  2. Update the HKLMSoftwareMicrosoftWindows NTCurrentVersionWinLogonShell registry key replacing cmd.exe with PowerShell.exe

To enable PowerShell run SCONFIG from the command prompt and then select menu options 4 then 2. This will require the computer to be rebooted

Once rebooted login and in the CMD prompt type PowerShell. At the PowerShell prompt type:

SET-ITEMPROPERTY "HKLM: SOFTWAREMICROSOFTWINDOWS NTCURRENTVERSIONWINLOGON" SHELL POWERSHELL.EXE

Having completed above log off and back on and a powershell prompt will open instead.

~Pouyan