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

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.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog