How to track Windows 8 OEM licensing in K1000
Started getting Windows 8 systems in today (specifically Latitude 10 tablets) and noticed none come with a COA sticker/license key. Previously, we were creating license assets in our K1000 to track these and stay compliant. Now that OEMs don't include a COA there is no actual "key" to keep track of any more.
Anyone have any thoughts on this? How are we supposed to keep our licensing current if we can't track the new embedded OEM licenses for Windows 8? Contacting my Dell account team now to get their take on it as well, will post back my findings.
Community Chosen Answer
Per my Dell account rep:
"I spoke with our Microsoft OEM rep about your situation and have confirmed that the MS license keys are indeed now imbedded within the BIOS of the system. The idea behind this is to enable “easier” reinstallation of the software so that no license key will be needed to record or enter upon reinstallation of the OS as the installer will automatically populate that into the reinstallation sequence from what it reads in the BIOS reducing the risk of people losing the sticker (due to wear and/or tear) that we are accustomed to seeing attached on the systems themselves.
As far as reporting goes for audits, our MS rep says that each system will come with a Microsoft Windows sticker to identify that the system came with a legitimate Win 8 OEM license. If further proof is need, your Dell Account Team (Brian and I) can run an OEM report to list all the systems that was purchased with a valid OEM license. Please note that this initiative was done via Microsoft working with all OEMs to send out machines with (at least ones with Win 8 OEM O/S) this method so auditors should be well aware of the situation with Win 8 OEM licensing. Let me know if this makes sense or if you have any further questions. Thanks!"
So going forward, if you buy OEM you won't have to track license assets any more. On the flip side of that, if you want your K1000 not to report that you are non-compliant, you will likely have to create a "dummy" license asset and attribute it to all your OEM systems.
Still doesn't quite sit right with me and the solution feels a tad bit sloppy, but I guess the times are a changing...