No, it's not a matter of not enough clients. If it was activated with a MAK key, it's because someone, somewhere, gave it one. I'd take a look at your imaging process, someone probably typed in a product key at some point where it should have been left blank.
On Mon, Jun 27, 2016 at 3:14 PM, Murray, Mike <mmur...@csuchico.edu> wrote: > Could be not enough clients, even though we have well over the amount > needed. They just probably all went with MAK activation. I’ve added a KMS > activation step in my TS that seems to do the trick. > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Jason Sandys > *Sent:* Thursday, June 23, 2016 7:09 PM > *To:* mssms@lists.myitforum.com > *Subject:* [mssms] RE: AD-based KMS client activation not working > > > > The Generic Volume License Key (GVLK) – which can also be referred to as > the KMS client key – is already embedded in the Windows media so if you > don’t specify a key, the GVLK will be used automatically. It certainly > doesn’t hurt to specify one, but it’s not required. > > > > I suspect that you haven’t met the activation quota or don’t have a KMS > server set up to handle Windows 10. Those are blond guesses though. The > normal Windows Application event log will have details about activation in > it. > > > > J > > > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Miller, Todd > *Sent:* Thursday, June 23, 2016 5:32 PM > *To:* mssms@lists.myitforum.com > *Subject:* [mssms] RE: AD-based KMS client activation not working > > > > (I am not sure about this answer) > > > > Don’t you have to put in a public KMS Client Setup key so that Windows > knows it needs to look for a KMS server? > > The Keys to use are located here… > > https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx > > > > I’ve not worked much with Windows 10 yet, but this is certainly true for > Windows 7. > > > > And you could double check in DNS to make sure your _VLMCS > serviceregistered correctly in _tcp in the forward lookup zone for your > domain. If you don’t specify a KMS server to use, then Windows is going to > look for one in DNS. > https://technet.microsoft.com/en-us/library/ff793405.aspx > > > > > > > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Murray, Mike > *Sent:* Thursday, June 23, 2016 1:53 PM > *To:* mssms@lists.myitforum.com > *Subject:* [mssms] AD-based KMS client activation not working > > > > When we image Windows 10 clients, we do not specify a product key. We have > AD configured for KMS activation, yet our clients are showing as MAK. Any > ideas? > > > > [image: cid:image001.png@01D1D068.E5EC4D60] > > > > > > Best Regards, > > > > Mike Murray > > Desktop Management Coordinator - IT Support Services > > California State University, Chico > > 530.898.4357 > mmur...@csuchico.edu > > > > Remember, Chico State will NEVER ask you for your password via email! > > For more information about recognizing phishing scam emails go to: > http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml > > > > > > > > > ------------------------------ > > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is > intended only for the use of the individual or entity to which it is > addressed, and may contain information that is privileged, confidential, > and exempt from disclosure under applicable law. If you are not the > intended recipient, any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and delete or > destroy all copies of the original message and attachments thereto. Email > sent to or from UI Health Care may be retained as required by law or > regulation. Thank you. > ------------------------------ > > > > > >
