There's a template in the firewall wizard for it on older OS versions, it's presumably still thereĭon but you only need to permit TCP:1688 inbound and you're done.
Temporarily disable the windows firewall on the server, as a test, to try a KMSclient activation. Normally, when enabling the VA features, the wizard will do the firewall rule for you, or tell you that it's needed. You should be able to confirm if TCP:1688 is allowed by a rule or not. Since we seem to have determined that the counted requests KMShost are coming internally from the server itself, maybe we haven't properly ruled out a firewall constraint.Ĭheck the Windows Firewall configuration on the server. Is the correct hostname for your KMShost? From a Win7 KMSclient machine, can you ping and do you get a successful response? This is the lower-level reason for 'KMSclient could not activate/KMShost could not be contacted'.
You've found an old error which may help.ĠxC0020017 = 'The RPC server is not available'. Your KMSclients are sending requests, but it's not clear where they are going, only that they aren't received at your KMShost. Your KMShost seems to be setup ok but it isn't receiving any activation traffic from your clients (other than itself). If that is true, it would explain why your Win10 scenarios are fine, and your Win7 scenarios are failing. ADBA can occur only on modern Windows OS versions - Win7 cannot service ADBA. So, I'm thinking that your OFF2016 activations are occurring via another channel, maybe ADBA. Your KMShost, is showing that it has not activated any OFF2016 clients (not even the Win10 computers). You haven't successfully activated any OFF2016 installation upon Win7 computers. You have successfully activated several OFF2016 installations, but those are on Win10 computers. Is there a way to get MS Office 2016 on Windows 7 workstations to activate with a Windows Server 2016 server with KMS? Please note, there is no dual activation involved with any older versions of Office, so some of the usual fixes online aren't affecting I ran the command to specify the server manually, but they still will not activate. I tried doing it manually from the command prompt but get an error saying something to the effect that a volume activation server cannot be located. But, none of the Windows 7 machines' MS Office will activate. The Windows 10 machines seem to activate fine. We then installed Office on all the workstations. Following instructions online, we setup KMS Volume Activation on the server, manually configured DNS, and installed the license key. We acquired a KMS volume license for MS Office 2016 Standard from TechSoup forĪll of the computers. We replaced a handful of workstations with new Windows 10 workstations. We recently setup a new Windows Server 2016 server for our church office.
0 kommentar(er)
