Feeds

Windows 8.1 and Server 2012 R2: Quick start guide for sysadmins

What do you mean you forgot your key?

Choosing a cloud hosting partner with confidence

Sysadmin blog Windows 8.1 and Windows Server 2012 R2 are now officially available. New shiny toys for the kids, but how does a sysadmin license these new products?

This post assumes you're already up and running with Windows 8 and Server 2012, but I'll quickly go over the basic requirements:

You'll need to obtain your Server Key Management Service (KMS) key from Microsoft’s Volume Licensing Service Center.

Clients by default will have a Client KMS key, but if you want to check, here's the list from Microsoft.

To clarify how a KMS works - a client has a Client KMS key which is generic globally, and tells the client to check in with a KMS Server to be licensed. The KMS Server talks back to Microsoft, using its Server KMS key which is special to your Microsoft agreement to keep itself activated.

The KMS Server will manage the licensing side of things, but there's a minimum amount of clients that need to have requested activation before the server starts approving anything. Twenty-five Client Operating Systems (eg, Windows 8.1) and five separate Server Operating Systems are the minimums. KMS clients attempt to check in every seven days, but have up to 180 days before licensing becomes invalid.

Confused yet?

KMS also needs a DNS entry (which can be customised) so clients know how to get to the KMS Server; the settings required are listed here.

Instructions

If you're not using a brand new Windows Server 2012 R2 server as your KMS Server, you'll need to download the relevant update.

If you don't do this and try to activate, you'll see the following message:

slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

So trust me, you need to install the patch and reboot.

Make sure you're using the KMS Server key relevant to the OS you're putting the key on, not what clients you're planning to license (ie, KMS Server 2012 R2 key goes on any Server OS - 2008 to 2012, and will allow you to license both Windows Server 2012 R2 clients and Windows 8.1 clients).

Once you've successfully added the key with the slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx command, you can force it to activate with the command slmgr.vbs /ato. Normally it takes a few seconds for the dialog box to show the results.

You can then see the stats on how many KMS clients are activated, as well as checking that you're ready for 8.1 and R2 with the command slmgr.vbs /dlv. Near the top of that dialog box will be a description which should end with VOLUME_KMS_2012-R2 channel.

You're now good to go with the exciting world of KMS licensing on the latest operating systems from Microsoft. ®

Internet Security Threat Report 2014

More from The Register

next story
NSA SOURCE CODE LEAK: Information slurp tools to appear online
Now you can run your own intelligence agency
Azure TITSUP caused by INFINITE LOOP
Fat fingered geo-block kept Aussies in the dark
Yahoo! blames! MONSTER! email! OUTAGE! on! CUT! CABLE! bungle!
Weekend woe for BT as telco struggles to restore service
Cloud unicorns are extinct so DiData cloud mess was YOUR fault
Applications need to be built to handle TITSUP incidents
Stop the IoT revolution! We need to figure out packet sizes first
Researchers test 802.15.4 and find we know nuh-think! about large scale sensor network ops
Turnbull should spare us all airline-magazine-grade cloud hype
Box-hugger is not a dirty word, Minister. Box-huggers make the cloud WORK
SanDisk vows: We'll have a 16TB SSD WHOPPER by 2016
Flash WORM has a serious use for archived photos and videos
Astro-boffins start opening universe simulation data
Got a supercomputer? Want to simulate a universe? Here you go
Microsoft adds video offering to Office 365. Oh NOES, you'll need Adobe Flash
Lovely presentations... but not on your Flash-hating mobe
prev story

Whitepapers

Designing and building an open ITOA architecture
Learn about a new IT data taxonomy defined by the four data sources of IT visibility: wire, machine, agent, and synthetic data sets.
Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
5 critical considerations for enterprise cloud backup
Key considerations when evaluating cloud backup solutions to ensure adequate protection security and availability of enterprise data.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Managing SSL certificates with ease
The lack of operational efficiencies and compliance pitfalls associated with poor SSL certificate management, and how the right SSL certificate management tool can help.