

RT okieselb: New blog post: Autopilot Manager with additional automation RT ariaupdated: YES!! The #UpdatePolicy CSP page is now updated to show which policies should be used for what and which are legacy polici… 1 month ago RT DBBrook24: Automatic Driver policies and Deferrals are working a treat with the #WUfBDS Driver and Firmware servicing!!

reg file that adds values I always find it’s best to add them into the registry manually on a test machine and then export those values into a. Then all you need to do is attach the GPO to the relevant OU’s containing machine objects. reg file and deploy it either with group policy or SCCM or even manually with something like psexec if you need to.Ĭreate a new GPO for the required KMS change.Ĭomputer Configuration>Preferences>Windows Settings>RegistryĪdd 2 new registry items to delete or add (whichever suits you) and Apply once only: GPO is one if you’re in an active directory environment, another is to create a. If you need to perform a mass add or delete then you have a few options. If they do appear you can either amend them or simply delete them. If they don’t appear simply add them in as string values. These are fairly self-explanatory, the service name is the KMS server and the service port is the TCP port used for contacting the KMS server. This is how it will look in your registry:

You can add (or look for) the following string values:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform If you browse the registry with regedit and go to the following key: If you ever find yourself in the position whereby you need to enforce a machine to use a particular KMS server or port then read on.Įqually if you have a machine that doesn’t seem to read the KMS server _vlmcs srv records from DNS then check this.
