How can you have a redundant KMS server?

In Windows 7, and Vista, we have two opportunities to activate our software using volume licensing. Multiple Activation Key (MAK) and Key Management System (KMS). MAK is useful in environments of less the 25 clients, or when you do not want the clients to have a need to check in with the activation server. KMS is useful when you are activating more than 25 clients. These clients check back with the activation server every 7 days, but can go as long as 180 days before deactivating.

Since the clients need to have some contact with a KMS host, the question is how to make this redundant. You can use the same KMS activation code to bring 2 KMS hosts online. One primary, and a backup. Microsoft does not recommend more than this.
Reference: http://www.eggheadcafe.com/software/aspnet/32994952/activationkms-issues-ca.aspx (See the comments from George Yin).

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Jason Yoder, MCT

Search This Blog