Windows 10: KMS and ADBA

ScenarioAn organization is currently using a multi-Forest environment and activating W10 devices in Forest A, from a KMS infrastructure in Forest B.They now want a native ADBA in Forest A to only activate their new W2019 server, and leave the W10 clients existing and new, to carry on activating from the old KMS server in Forest B.Is this a possible scenario that can be achieved, or will new W10 clients added to Forest A be automatically activated by the new ADBA implementation?Thanks.Martin

:)

 

Microsoft Sculpt Keyboard won't connect to Windows 10 Pro through Lindy KM Switch after upgrade from Win7 Pro

Hi,

The issue might occur if the device is not compatible with Windows 10. Since you mentioned that it's not working if the keyboard is connected to Lindy KM Switch. To troubleshoot the issue, we suggest that you check if the keyboard will be detected by your
PC while it’s connected to Lindy KM Switch. Follow the steps below to check:

• Right-click on the Start menu and select Device Manager.
• Click on the arrow button beside Keyboard and look for the name of your keyboard.

If it’s not there, we recommend that you visit Lindy KM Switch’s website to verify if the device you are using is compatible with Windows 10.

Let us know how it goes.

 

Win 10 crashed and stopped booting from Dual boot.

Please list the steps that you used to remove KMS.

 

Windows 7 activation with KMS

• https://www.ghacks.net/2019/01/11/microsoft-explains-the-windows-7-kms-activation-issue/
  
• Activation failures around January 8, 2019, on volume-licensed Windows 7 Service Pack 1 KMS clients - Windows Client