For those that are just getting started with Windows Server 2012 you may have noticed that you don’t get the option to change the server’s product key on the activation page. This can be a problem if you need to switch to MAK or KMS keys and reactive the server. No worries, the solution is pretty simple. You can use one of the following 2 options:
Option #1 –
1. Open a Command promtp and run the following :
slmgr.vbs /ipk <put your Product key here>
Option #2 –
1. On Windows server 2012 -( with your mouse point to the lower-right hand corner of the screen) click Search.
2. Type Slui.exe 0x3
3. When the activation screen pops up type in your new Product Key and Activate.
There maybe times that you will need or want to re-size a Netapp volume and normally this is process is very easy to do. You can re-size a Netapp volume using the ONcommand tool, Filerview, or even SSH into the filer directly. Either of these ways is perfectly fine, no wrong way to do it except for when it fails.
A common error I have seen for failed volume re-sizing is due to the “fs_size_fixed” error.
The “fs_size_fixed” is a parameter that has been enabled on the volume either during setup or during a snapmirror relationship break. The parameter is there to prevent any type of accidental re-sizing on the volume. The only way to re-size the volume is to remove the “fs_size_fixed” parameter by connecting directly to filer through an SSH tool and running the following commands. Once the parameter is removed you will be able to re-size the volume.
1. Connect to the filer ( you can use Putty if you have it)
2. First verify that “fs_size_fixed” is enabled on the vol, type : vol status [name of vol]
you will see in the status that “fs_size_fixed” is set to ON
3. At the prompt type : vol options [name of vol] fs_size_fixed off
4. You can confirm that the parameter has been disabled by typing : vol status [name of vol]
Happy Friday everyone!
It looks like Apple has release another iOS update for iPhone 5 on this fine May Friday. The latest update appears to be for audio profile for the speakerphone. Not sure what it really fixes since I didn’t notice any difference after apply the update. Must be something important….
More information on the latest update can be found at http://support.apple.com/kb/DL1652
If you’re unsure on how to apply Apple updates visit http://support.apple.com/kb/HT4623
The CMID ( Client Machine ID) is a unique ID that is used by a KMS host to activate the license on the machine. Typically each system has it’s own ID and there are no issues but with the use of tools such as cloning the CMID can be duplicated. When the KMS host treats each CMID as 1 client, so if you have 200 systems all containing the same CMID the KMS host has only activated 1 client machine. This results inaccurate licensing activation by your KMS host.
So what causes these duplicates you ask? Normally this is caused by some sort of cloning or imaging of a system that did not sysprep with the sysprep /generalize option, see Microsoft KB929829. I have also seen this happen when you deploy a vm from a vCenter template and you do not use the customization wizard to customize your vm.
Once the CMID is set unfortunately Microsoft does not support changing the CMID, however it is possible to do so. Microsoft does not support changing the CMID and their recommended workaround is too re-image the system using the sysprep /generalize option because changing the CMID may cause the OS to become unstable. With a user’s system that is easier to re-image but let’s say you have several production servers that have duplicate ID’s?
Good luck with telling the application owners that you need to re-deploy their server to fix a duplicate CMID. I’m sure that will go over well. If you work in a company like mine,where that would not fly well, you have 2 options either you live with the duplicate CMIDs ( prevent future duplicates) or change it by resetting the CMID.
If you’re daring like me , I would look for the reset option and test it, to see what happens. Changing or resetting the CMID on a system is technically re-arming the licensing on the system. To re-arm the licenese you will need to logon to the system with the duplicate ID and run the following command:
cscript c:\windows\system32\slmgr.vbs /rearm
So there you go, you can change the CMID just keep in mind it’s not support by Microsoft if you do. The best thing to do is just avoid having duplicates by running the sysprep /generalize option when cloning systems. If you’re deploying vm’s just remember to run the customization wizard or have a precanned setting wizard all ready to go.
I recently had another one of my weird Snapdrive issues while trying to resize an iSCSI Lun on a 2003 server. The server is a VM that is using the Microsoft iSCSI initiator and Snapdrive to manage the Netapp provisioned Lun. Re-sizing a lun using Snapdrive is normally very simple but of course on this particular day it was not behaving for me.
Snapdrive appeared to be running ok and didn’t seem to have any issues at all that day. The problem came when I attempted to re size the lun, Snapdrive re-sizing process would fail halfway through. The failure to complete the re-sizing left me puzzled since all connections to the filer appeared to be fine. There was plenty of space left on the volume so it wasn’t a space issue.
Since we were dealing with Windows here we rebooted the server just in case it was pending a reboot or it just needed to “clear it’s head”. After the reboot I attempted to re-size the lun again and again it failed . The actual failure message was that it was unable to connect to the disk. Odd…It’s connected in Snapdrive , it just won’t resize.
The next thing I thought of was to force a disconnect on the iscsi lun, this way it would forces a disconnect on all connections. The downside to the disconnect was that the Lun would be lost and the SQL databases would need to be stopped. After getting approval to take the server down again, I then proceeded to force a disconnect of this lun. Once all connections were stopped and confirmed they were gone, I then reconnected the iSCSI Lun using Snapdrive.
After the re-connection was completed, I continued with trying to re-size the Lun. BAM! It worked. All it took was a force disconnect , reconnect, then I could re-size. To be honest , I wasn’t in the mood to go further digging into a root cause for the failure, especially since I got it working now. I suspect it had something to do with Snapdrive and the iscsi connection it was using since a brand new connection seemed to clear any issues that it had previously. So, if you run into something like this, it might be worth a force disconnect to solve your re-sizing problem.