![]() ![]()
Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.Every time I've ever installed a KMS (I have done quite a few), the Office KMS will happily activate Office Std, Office ProPlus, Visio Std/Pro/Prem, Project Std/Pro. #Visio 2013 kms activator download licenseRequests with License Status Notification: 193ĭescription: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel Requests with License Status Non-genuine grace period: 0 Requests with License Status License expired or Hardware out of tolerance: 0 Requests with License Status Initial grace period: 67 Requests with License Status Unlicensed: 0 Key Management Service cumulative requests received from clients All rights reserved.ĭescription: Windows Operating System - Windows Server(R), RETAIL channel ![]() Microsoft (R) Windows Script Host Version 5.8Ĭopyright (C) Microsoft Corporation. That should NOT have broken anything like this. This was all running fine - until I added my Server 2012 key - so Windows 8 clients would activate, and added my office 2013 key. So why are my Visio 2010 clients now falling out of activation? I have nearly 90 clients.Įven so 10 meets the minimum activation requirement for KMS to activate office clients. If I read this right it says I only have 10 Office 2010 clients that requested activation? That can't be right. This helps the community, keeps the forums tidy, and recognises useful contributions. (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. I think your Visio problem, is not related to the pkey changes you've done.Ĭheck the KMS and also client event logs next. This is also fine, it shows your old KMS pkey, no longer in use. Name: Windows Server(R), ServerStandard editionĭescription: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel This is fine, is show 10, which is double the minimum of 5, and it will never grow beyond 10. Name: Microsoft Office 2010, KMSHost editionĭescription: Microsoft Office 2010 KMS, VOLUME_KMS channel This is fine, it shows your old KMS stats, but is no longer licensed, since WS2012 pkey has replaced this one. Name: Windows Server(R), ServerStandard editionĭescription: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_C channel This is fine, this is your new W2012 pkey, and it includes WindowsClient editions eg Win7/Win8. This is fine, only 1 client has requested activation of Office2013 - not enough (needs to be 5) Name: Windows Server(R), ServerStandard editionĭescription: Windows Operating System - Windows Server(R), VOLUME_KMS_2012_C channel Key Management Service is enabled on this machine So I think I'm just not at the minimum 5 count for 2013 clients yet - so I understand that.īut why is Visio suddenly a problem when it was fine before? Why are my 2010 clients all suddenly falling out of activated status?ĭescription: Office 15, VOLUME_KMS channel ![]() So the count on one isn't cumulative with the other. It also appears office 2010 and office 2013 are hitting kms as a separate activation. #Visio 2013 kms activator download proMy Visio clients were activating and I only ever installed my office pro plus 2010 key at that point. #Visio 2013 kms activator download installSo my question is what the heck happened? I install the KMS requirements and keys for 2013 and now I have 2010 clients falling out of activation?ĭoes Visio require it's own key be entered into the KMS server? This didn t appear to be the case with 2010. My Office 2013 Clients will not activate. My Visio 2010 users will now no longer activate (had been previously) - now are falling out of activated status. My Office 2010 pro plus clients clients are fine so far I have downloaded, installed, and activated the office 2013 KMS Host License Pack, installed my 2013 pro plus key. I have a mixed environment of office 2010 and office 2013. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |