Deploying Wink28 R2 with Product Key fails (OSD)
- By Huzaifah Ahmad
- Published 05/8/2010
Huzaifah Ahmad
I am currently working as a Senior Field Consultant. I started my professional career in 1999 in India. In the year 1999 I decided to transition from the Retail Industry to hard core Information Technology, which was always my strength and desire. I realised my strengths and keen interest when I worked on Dbase III Plus a few years back but due to various constraints I could not pursue my career at that point in time. I have worked in various capacities in the fields of Software Technology, as Systems administrator, Systems Support Engineer, Implementations Engineer and Senior Implementation Engineer. Currently, I am based as Senior Field Consultant for a Microsoft Gold Partner in Oxford, U.K.
I am certified in various disciplines
CCIE # 23368
CCNP
CCNA
CCA
MCSE NT, 2k & 2k3
MCSA 2k & 2k3
MCSE 2k & 2k3 (Messaging & Security)
MCSA 2k & 2k3 (Messaging & Security)
I devote my free time to the technology communities. I believe knowledge grows by sharing and I love to share my knowledge. I believe it is important to be passionate and really enjoy whatever you do. I am also the founder and maintain Ahmedgroup (http://www.ahmedgroup.co.uk)
Deploying Wink28 R2 with Product Key fails (OSD)
Is the Windows 7 KMS Key used at any point in OSD for the client or is the key used exclusively for the KMS Host
KMS keys are used only to create KMS systems; they are not the equivalent of the legacy volume license keys (VLK). The rough equivalent of a VLK is the multiple activation key (MAK). Never use a KMS key unless you are standing up a KMS. Clients activating against a KMS -- aka KMS clients -- do not require a key. That's part of the "beauty" of the KMS scheme, you never have to enter or give out a key.
Please click on the URL's to read the entire threads.