RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-12 Thread Rich Milburn
I got an answer about KMS.  I hesitated about posting here but I think
this just clears up the misconceptions expressed in the thread, it
doesn't really disclose any new information...

There are 2 issues here, and a bit of a misunderstanding.

Windows Server codenamed Longhorn is still in beta. The KMS service
for beta builds will not allow released products to activate. So, if you
want to support both Longhorn and the released version of Vista with
KMS, you will need 2 KMS hosts. However, when Longhorn is released, any
KMS intended to activate Longhorn servers will also activate Vista
volume clients.

Secondly, the KMS client will retrieve all SRV records from DNS. It
will pick one at random and attempt to connect to it. If the client does
not successfully activate or renew its activation, it will pick another
KMS from the list, and so on until they succeed or they have tried the
entire list. If a Vista KMS client contacts a beta KMS host, the client
will receive an invalid version error and will proceed to try another
KMS from the list provided by DNS.

I hope that helps clear things up.



---
Rich Milburn
MCSE, Microsoft MVP - Directory Services
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.
4551 W. 107th St
Overland Park, KS 66207
913-967-2819
--
I love the smell of red herrings in the morning - anonymous

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rich Milburn
Sent: Thursday, December 07, 2006 11:09 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS

 

 My hope was that KMS could support more than one key. I was astonished
when I discovered it didn't. If you were Vista, KMS would supply you
with a Vista key. Longhorn, a Longhorn key. Since KMS only supports one
key, it triggers the need for two separate KMS infrastructures and the
problems in #2 below.   

 

I put this up in the beta volume licensing group, hopefully there will
be some MSFT response on this.  I agree with you - the point of making
it easy by allowing srv records is offset by the fact neither the VL
client nor the KMS server can differentiate between Vista and LHS.  Even
if the solution is to update the KMS service prior to longhorn's
release, and have separate srv records (one for Vista, one for longhorn,
another for ?? because you know they're on a roll now and will soon have
other things doing VLA)  personally I'd rather have multiple records
than multiple KMS servers, and hard-coding reg keys or using MAKS for
all servers is not really a good solution, IMHO.

 

Rich

 

---
Rich Milburn
MCSE, Microsoft MVP - Directory Services
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.
4551 W. 107th St
Overland Park, KS 66207
913-967-2819
--
I love the smell of red herrings in the morning - anonymous

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey
Kamangwitz
Sent: Tuesday, December 05, 2006 11:41 PM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

 

On 12/5/06, Laura A. Robinson [EMAIL PROTECTED] wrote:

Inline...

 



From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

If you have any kind of a complex environment, you'll
find volume activation to be very frustrating indeed:

 

1. The KMS service can't support more than one key, so
if you have Longhorn VL clients in your environment you have to put up a
second KMS infrastructure for them.  

 

Actually, when you purchase a KMS key, you get to
activate TWO KMS hosts with that key, up to ten times each. Therefore,
you don't have to put up a second KMS infrastructure.  

From a subsequent post on this thread:

Doh! Okay, now I think I get what you're referencing in item 1.

There's a reason for that- LH isn't out yet. When LH is out, that won't
be an issue. :-)

 

My hope was that KMS could support more than one key. I was astonished
when I discovered it didn't. If you were Vista, KMS would supply you
with a Vista key. Longhorn, a Longhorn key. Since KMS only supports one
key, it triggers the need for two separate KMS infrastructures and the
problems in #2 below.   I'm assuming that Microsoft will be using Volume
Activation for other products in the future; are we to put up a separate
KMS for each?


 

 

2. You

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-12 Thread Harvey Kamangwitz

If a Vista KMS client contacts a beta KMS host, the client will receive an
invalid version error and will proceed to try another KMS from the list
provided by DNS.

This is good information, Rich; I hadn't seen this before. It means that
beta and production KMS infrastructures can coexist. Thanks for posting.

- Harvey



On 12/12/06, Rich Milburn [EMAIL PROTECTED] wrote:


 I got an answer about KMS.  I hesitated about posting here but I think
this just clears up the misconceptions expressed in the thread, it doesn't
really disclose any new information…

There are 2 issues here, and a bit of a misunderstanding.

Windows Server codenamed Longhorn is still in beta. The KMS service for
beta builds will not allow released products to activate. So, if you want to
support both Longhorn and the released version of Vista with KMS, you will
need 2 KMS hosts. However, when Longhorn is released, any KMS intended to
activate Longhorn servers will also activate Vista volume clients.

Secondly, the KMS client will retrieve all SRV records from DNS. It will
pick one at random and attempt to connect to it. If the client does not
successfully activate or renew its activation, it will pick another KMS from
the list, and so on until they succeed or they have tried the entire list.
If a Vista KMS client contacts a beta KMS host, the client will receive an
invalid version error and will proceed to try another KMS from the list
provided by DNS.

I hope that helps clear things up.

*---**
**Rich Milburn**
**MCSE, Microsoft MVP - Directory Services**
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.**
**4551 W. 107th St**
**Overland Park, KS 66207**
**913-967-2819**
**--**
**I love the smell of red herrings in the morning - anonymous*

*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Rich Milburn
*Sent:* Thursday, December 07, 2006 11:09 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* RE: [ActiveDir] OT: Vista Activation and KMS



 My hope was that KMS could support more than one key. I was astonished
when I discovered it didn't. If you were Vista, KMS would supply you with a
Vista key. Longhorn, a Longhorn key. Since KMS only supports one key, it
triggers the need for two separate KMS infrastructures and the problems in
#2 below.



I put this up in the beta volume licensing group, hopefully there will be
some MSFT response on this.  I agree with you – the point of making it easy
by allowing srv records is offset by the fact neither the VL client nor the
KMS server can differentiate between Vista and LHS.  Even if the solution is
to update the KMS service prior to longhorn's release, and have separate srv
records (one for Vista, one for longhorn, another for ?? because you know
they're on a roll now and will soon have other things doing VLA)  personally
I'd rather have multiple records than multiple KMS servers, and hard-coding
reg keys or using MAKS for all servers is not really a good solution, IMHO.



Rich



*---
**Rich Milburn
**MCSE, Microsoft MVP - Directory Services
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.**
**4551 W. 107th St**
**Overland Park, KS 66207**
**913-967-2819**
**--**
**I love the smell of red herrings in the morning - anonymous*



*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Harvey Kamangwitz
*Sent:* Tuesday, December 05, 2006 11:41 PM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS





On 12/5/06, *Laura A. Robinson* [EMAIL PROTECTED] wrote:

 Inline...


 --

*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Harvey Kamangwitz
*Sent:* Tuesday, December 05, 2006 11:28 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS



If you have any kind of a complex environment, you'll find volume
activation to be very frustrating indeed:



1. The KMS service can't support more than one key, so if you have
Longhorn VL clients in your environment you have to put up a second KMS
infrastructure for them.



Actually, when you purchase a KMS key, you get to activate TWO KMS hosts
with that key, up to ten times each. Therefore, you don't have to put up a
second KMS infrastructure.

 From a subsequent post on this thread:

Doh! Okay, now I think I get what you're referencing in item 1.

There's a reason for that- LH isn't out yet. When LH is out, that won't be
an issue. :-)



My hope was that KMS could support more than one key. I was astonished
when I discovered it didn't. If you were Vista, KMS would supply you with a
Vista key. Longhorn, a Longhorn key. Since KMS only supports one key, it
triggers the need

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-12 Thread Harvey Kamangwitz

Oops. I forgot a few words: ...can coexist *using autodiscovery.*
**
-H

On 12/12/06, Harvey Kamangwitz [EMAIL PROTECTED] wrote:


If a Vista KMS client contacts a beta KMS host, the client will receive
an invalid version error and will proceed to try another KMS from the list
provided by DNS.

This is good information, Rich; I hadn't seen this before. It means that
beta and production KMS infrastructures can coexist. Thanks for posting.

- Harvey



On 12/12/06, Rich Milburn [EMAIL PROTECTED] wrote:

  I got an answer about KMS.  I hesitated about posting here but I think
 this just clears up the misconceptions expressed in the thread, it doesn't
 really disclose any new information…

 There are 2 issues here, and a bit of a misunderstanding.

 Windows Server codenamed Longhorn is still in beta. The KMS service
 for beta builds will not allow released products to activate. So, if you
 want to support both Longhorn and the released version of Vista with KMS,
 you will need 2 KMS hosts. However, when Longhorn is released, any KMS
 intended to activate Longhorn servers will also activate Vista volume
 clients.

 Secondly, the KMS client will retrieve all SRV records from DNS. It
 will pick one at random and attempt to connect to it. If the client does not
 successfully activate or renew its activation, it will pick another KMS from
 the list, and so on until they succeed or they have tried the entire list.
 If a Vista KMS client contacts a beta KMS host, the client will receive an
 invalid version error and will proceed to try another KMS from the list
 provided by DNS.

 I hope that helps clear things up.

 *---
 **
 **Rich Milburn**
 **MCSE, Microsoft MVP - Directory Services**
 Sr Network Analyst, Field Platform Development
 Applebee's International, Inc.**
 **4551 W. 107th St**
 **Overland Park, KS 66207**
 **913-967-2819 **
 **--
 **
 **I love the smell of red herrings in the morning - anonymous*

 *From:* [EMAIL PROTECTED] [mailto:
 [EMAIL PROTECTED] *On Behalf Of *Rich Milburn
 *Sent:* Thursday, December 07, 2006 11:09 AM
 *To:* ActiveDir@mail.activedir.org
 *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS



  My hope was that KMS could support more than one key. I was astonished
 when I discovered it didn't. If you were Vista, KMS would supply you with a
 Vista key. Longhorn, a Longhorn key. Since KMS only supports one key, it
 triggers the need for two separate KMS infrastructures and the problems in
 #2 below.



 I put this up in the beta volume licensing group, hopefully there will
 be some MSFT response on this.  I agree with you – the point of making it
 easy by allowing srv records is offset by the fact neither the VL client nor
 the KMS server can differentiate between Vista and LHS.  Even if the
 solution is to update the KMS service prior to longhorn's release, and have
 separate srv records (one for Vista, one for longhorn, another for ??
 because you know they're on a roll now and will soon have other things doing
 VLA)  personally I'd rather have multiple records than multiple KMS servers,
 and hard-coding reg keys or using MAKS for all servers is not really a good
 solution, IMHO.



 Rich



 *---
 **Rich Milburn
 **MCSE, Microsoft MVP - Directory Services
 Sr Network Analyst, Field Platform Development
 Applebee's International, Inc.**
 **4551 W. 107th St**
 **Overland Park, KS 66207 **
 **913-967-2819**
 **--
 **
 **I love the smell of red herrings in the morning - anonymous *



 *From:* [EMAIL PROTECTED] [mailto:
 [EMAIL PROTECTED] *On Behalf Of *Harvey Kamangwitz
 *Sent: *Tuesday, December 05, 2006 11:41 PM
 *To:* ActiveDir@mail.activedir.org
 *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS





 On 12/5/06, *Laura A. Robinson* [EMAIL PROTECTED] wrote:

  Inline...


  --

 *From:* [EMAIL PROTECTED] [mailto:
 [EMAIL PROTECTED] *On Behalf Of *Harvey Kamangwitz
 *Sent:* Tuesday, December 05, 2006 11:28 AM
 *To:* ActiveDir@mail.activedir.org
 *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS



 If you have any kind of a complex environment, you'll find volume
 activation to be very frustrating indeed:



 1. The KMS service can't support more than one key, so if you have
 Longhorn VL clients in your environment you have to put up a second KMS
 infrastructure for them.



 Actually, when you purchase a KMS key, you get to activate TWO KMS hosts
 with that key, up to ten times each. Therefore, you don't have to put up a
 second KMS infrastructure.

  From a subsequent post on this thread:

 Doh! Okay, now I think I get what you're referencing in item 1.

 There's a reason for that- LH isn't out yet. When LH is out, that won't
 be an issue. :-)



 My hope

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-09 Thread Laura A. Robinson
You know, there's one thing I may have forgotten to mention- there's a good
whitepaper on this.
 
:-P
 
Laura


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of MikeM
Sent: Saturday, December 09, 2006 12:10 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS


So Laura, correct me if I'm wrong, but are you suggesting we read the white
paper? 

Seriously, thank you for all of the input on this matter.

-MM-


On 12/8/06, Laura A. Robinson HYPERLINK
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] wrote: 

1. The entire conversation is ~450 BYTES of traffic. If you can't swing that
over six months, you have bigger problems than activation. SSL-based VPN
changes nothing. Connectivity is connectivity. Why do you assume that
activation can't occur over an SSL-based VPN?
2. If you have no links at all, either look at a KMS host at the remote
sites, or look at MAK activation. 
3. Who said anything about you having to have two different images?
 
Folks, please read the whitepapers and try this out before you reject it.
The expression tilting at windmills comes to mind with some of these
objections.
 
Laura


   _  

From: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] [mailto:HYPERLINK
mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of HYPERLINK
mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
Sent: Friday, December 08, 2006 11:41 AM
To: HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED]
Subject: RE: [ActiveDir] OT: Vista Activation and KMS




If it's so well baked then how do you support multiple remote offices with
slow VPN links, or none at all? How do you support field users without a VPN
client, or using an SSL based VPN? Making us use two different images (one
for each key type) isn't a solution since it doubles our support work and
clients may move from one model to the other. There are plenty of situations
where it just doesn't work well for IT in the real world. 

Thanks, 
Andrew Fidel 



Laura A. Robinson HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 
Sent by: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 


12/05/2006 04:43 PM 


Please respond to
HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED]



To
HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED]  

cc



Subject
RE: [ActiveDir] OT: Vista Activation and KMS








The Windows Server 2003 KMS host will be out soon. In the meantime, Vista is
perfectly acceptable to use and it's incredibly simple to decommission it as
a KMS host when you implement a Win2K3 host. No TAM support needed.

Again, I'd really encourage people to thorougly read the documents I
referenced before, because I'm seeing a lot of confusion on this list that
indicates that people aren't really understanding how this works (not you in
particular, Susan, just a general comment as I've been watching the VLA
comments for a little while). 

Or if you're Neil, you can schedule a LiveMeeting and I'll explain it,
because Neil's company is one of my district's customers. ;-)

Laura 

 -Original Message-
 From: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 
 [mailto:HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of 
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Tuesday, December 05, 2006 3:21 PM
 To: HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED]
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS
 
 I personally am not ready to stick a Vista box as a 
 Licensing server.
 
 ISA still doesn't have a firewall client that works for 
 one... and I've yet to find a a/v that doesn't BSOD my tablet 
 pc or act strangely on another box I built.
 
 In fact I'm still using my Technet 'for testing purposes' 
 ones as I'm not ready to play with my VL ones.  Activation on 
 the VL ones means I'm serious to roll...and quite frankly.. I'm not.
 
 I still want to see a more formal support story on 
 Activations in general for folks that aren't TAM supported...
 
 YMMV and all that.
 
 Laura A. Robinson wrote:
  I am not at all talking about solutions that don't exist 
 today. Go to 
  a Vista machine and take a look at slmgr.vbs.
   
  Laura
 
  
 --
 --
  *From:* HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]
  [mailto:HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] *On Behalf Of *Tim
  Vander Kooi
  *Sent:* Tuesday, December 05, 2006 12:39 PM
  *To:* HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED]
  *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS
 
  While Laura and yourself make valid points, you are both talking
  about solutions that do not exist today. I'm just trying to help
  the OP with the problem he is having right now. Getting into the
  full licensing overhead of Vista, not to mention LH, could, and
  undoubtedly will, take weeks

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-09 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Yes but does it have good screenshots.  ..it's not a SBSized whitepaper 
unless it's got screenshots you know ;-)
Honestly I don't see that many SBSers will be setting up a KMS 
infrastructure anyway... Microsoft may love it if we roll out 25 or more 
VLs.. but I doubt that and we'd be buying OEM Vista's anyway.  (not to 
mention... we'd annoyingly ask to have a wizard to install this sucker 
anyway ;-)


I'm assuming you mean this link?
http://www.microsoft.com/downloads/details.aspx?FamilyID=9893f83e-c8a5-4475-b025-66c6b38b46e3DisplayLang=en

Laura A. Robinson wrote:
You know, there's one thing I may have forgotten to mention- there's a 
good whitepaper on this.
 
:-P
 
Laura



*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of *MikeM
*Sent:* Saturday, December 09, 2006 12:10 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS

So Laura, correct me if I'm wrong, but are you suggesting we read
the white paper?

Seriously, thank you for all of the input on this matter.

-MM-

On 12/8/06, *Laura A. Robinson* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:

1. The entire conversation is ~450 BYTES of traffic. If you
can't swing that over six months, you have bigger problems
than activation. SSL-based VPN changes nothing. Connectivity
is connectivity. Why do you assume that activation can't occur
over an SSL-based VPN?
2. If you have no links at all, either look at a KMS host at
the remote sites, or look at MAK activation.
3. Who said anything about you having to have two different
images?
 
Folks, please read the whitepapers and try this out before you

reject it. The expression tilting at windmills comes to mind
with some of these objections.
 
Laura




*From:* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]] *On Behalf Of
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
*Sent:* Friday, December 08, 2006 11:41 AM
*To:* ActiveDir@mail.activedir.org
mailto:ActiveDir@mail.activedir.org
*Subject:* RE: [ActiveDir] OT: Vista Activation and KMS


If it's so well baked then how do you support multiple
remote offices with slow VPN links, or none at all? How do
you support field users without a VPN client, or using an
SSL based VPN? Making us use two different images (one for
each key type) isn't a solution since it doubles our
support work and clients may move from one model to the
other. There are plenty of situations where it just
doesn't work well for IT in the real world.

Thanks,
Andrew Fidel


*Laura A. Robinson [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]

12/05/2006 04:43 PM
Please respond to
ActiveDir@mail.activedir.org
mailto:ActiveDir@mail.activedir.org



To
ActiveDir@mail.activedir.org
mailto:ActiveDir@mail.activedir.org 
cc

Subject
RE: [ActiveDir] OT: Vista Activation and KMS









The Windows Server 2003 KMS host will be out soon. In the
meantime, Vista is
perfectly acceptable to use and it's incredibly simple to
decommission it as
a KMS host when you implement a Win2K3 host. No TAM
support needed.

Again, I'd really encourage people to thorougly read the
documents I
referenced before, because I'm seeing a lot of confusion
on this list that
indicates that people aren't really understanding how this
works (not you in
particular, Susan, just a general comment as I've been
watching the VLA
comments for a little while).

Or if you're Neil, you can schedule a LiveMeeting and I'll
explain it,
because Neil's company is one of my district's customers. ;-)

Laura

 -Original Message-
 From: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Tuesday, December 05, 2006 3:21 PM
 To: ActiveDir@mail.activedir.org
mailto:ActiveDir@mail.activedir.org

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-09 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
, since there is no supported upgrade path.



-

From the I did not know that...

The Windows Anytime Upgrade (WAU) program allows a Windows Vista 
Business user to purchase an upgrade directly from Microsoft by clicking 
the Windows Anytime Upgrade link in *All Programs* and/ /*Extras and 
Upgrades*. This link and the program are only provided in Windows Vista 
Business editions because both volume-licensed and retail versions of 
this product are available (unlike Windows Vista Enterprise, which is 
only sold as a Volume License version).


-

You need more screen shots :-)  That has build me a wizard written all 
over it for us lazy SBSers :-)  Big server land... I'd be setting up a 
Vista lab and testing this stuff out.


I know someone said there was a Vista beta activation newsgroup but is 
it rolling over to RTM public newsgroup?  Given that some of my key 
business critical 'parts' for Vista are still not in place (ISA client 
and my Cingular connection manager software is flakey) businesses that 
do VLs need to look at this and set up labs for this.  While it's a good 
whitepaper (it would have been better with more screen shots ;-) ) there 
is still an administrative cost to Vista VLs that I would argue XP sp2 
never had that does need to be considered.  WGA/OGA/VGA  -- while I 
totally and utterly understand the need, it's still a bit of a change 
that needs to be communicated well  (and us SBSers have had product 
activation on our Servers for eons.. .so it's not new down here to have 
product activation... in fact I had gotten so used to SBS's setup that 
when I was setting up some big server land stuff and they asked so 
how many cals you got? I think I fell out of my chair,  and said Oh 
yeah, that's right, they trust you guys to be honest?  Wow!  Amazing!)  
If you poke around the WGA forum...there's a lot of VL keys that end up 
on the streets and shouldn't be out there.


 oh and have I said it needs more screen shots?  :-)


http://www.microsoft.com/downloads/details.aspx?FamilyID=9893f83e-c8a5-4475-b025-66c6b38b46e3DisplayLang=en


Laura A. Robinson wrote:
You know, there's one thing I may have forgotten to mention- there's a 
good whitepaper on this.
 
:-P
 
Laura



*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of *MikeM
*Sent:* Saturday, December 09, 2006 12:10 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS

So Laura, correct me if I'm wrong, but are you suggesting we read
the white paper?

Seriously, thank you for all of the input on this matter.

-MM-

 12/8/2006 12:53 PM


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-09 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 the setup to install Windows Vista. Bootable 
media is also available on request through your Volume License portal.





[1] #_ftnref1 64-bit Volume License media are not restricted in this 
way, since there is no supported upgrade path.



-

From the I did not know that...

The Windows Anytime Upgrade (WAU) program allows a Windows Vista 
Business user to purchase an upgrade directly from Microsoft by 
clicking the Windows Anytime Upgrade link in *All Programs* and/ 
/*Extras and Upgrades*. This link and the program are only provided in 
Windows Vista Business editions because both volume-licensed and 
retail versions of this product are available (unlike Windows Vista 
Enterprise, which is only sold as a Volume License version).


-

You need more screen shots :-)  That has build me a wizard written 
all over it for us lazy SBSers :-)  Big server land... I'd be setting 
up a Vista lab and testing this stuff out.


I know someone said there was a Vista beta activation newsgroup but is 
it rolling over to RTM public newsgroup?  Given that some of my key 
business critical 'parts' for Vista are still not in place (ISA client 
and my Cingular connection manager software is flakey) businesses that 
do VLs need to look at this and set up labs for this.  While it's a 
good whitepaper (it would have been better with more screen shots ;-) 
) there is still an administrative cost to Vista VLs that I would 
argue XP sp2 never had that does need to be considered.  WGA/OGA/VGA  
-- while I totally and utterly understand the need, it's still a bit 
of a change that needs to be communicated well  (and us SBSers have 
had product activation on our Servers for eons.. .so it's not new down 
here to have product activation... in fact I had gotten so used to 
SBS's setup that when I was setting up some big server land stuff 
and they asked so how many cals you got? I think I fell out of my 
chair,  and said Oh yeah, that's right, they trust you guys to be 
honest?  Wow!  Amazing!)  If you poke around the WGA forum...there's 
a lot of VL keys that end up on the streets and shouldn't be out there.


 oh and have I said it needs more screen shots?  :-)


http://www.microsoft.com/downloads/details.aspx?FamilyID=9893f83e-c8a5-4475-b025-66c6b38b46e3DisplayLang=en 




Laura A. Robinson wrote:
You know, there's one thing I may have forgotten to mention- there's 
a good whitepaper on this.
 
:-P
 
Laura





*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of *MikeM
*Sent:* Saturday, December 09, 2006 12:10 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS

So Laura, correct me if I'm wrong, but are you suggesting we read
the white paper?

Seriously, thank you for all of the input on this matter.

-MM-

 12/8/2006 12:53 PM


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-08 Thread Rich Milburn
Well done Laura.  Though I hadn't heard the bit about the KMS server not
talking to Microsoft (admittedly I have not read the document yet, I've
just read a lot about it in the beta NG discussions.  Do you suppose
that is the same level of not reporting to Microsoft that WGA did?
http://www.microsoft-watch.com/content/security/whats_genuine_about_wind
ows_genuine_advantage.html   One thing that is talked about a fair bit
that you didn't mention is that the KMS server doesn't activate clients
until it reaches a threshold of 25 client requests.   This was stated a
number of times by Microsoft people in the newsgroups.

 

---
Rich Milburn
MCSE, Microsoft MVP - Directory Services
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.
4551 W. 107th St
Overland Park, KS 66207
913-967-2819
--
I love the smell of red herrings in the morning - anonymous

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laura A.
Robinson
Sent: Thursday, December 07, 2006 8:46 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS

 

Okay, let me see if I can summarize this in a gazillion words or less...

 

There are two types of activations for Vista- MAK activation and KMS
activation.

 

MAK activation works much like an MSDN subscription. You tell Microsoft
how many MAK activations you want to purchase. Microsoft sells you a MAK
key with that many activations. A machine that is activated via MAK
activation never has to renew. A MAK-activated client either directly
contacts Microsoft servers for activation or (in 2007, when the VAMT
tool is released) it activates against a proxy in your company that
feeds the activation to Microsoft activation servers. If you reinstall
the OS and specify MAK activation again, then that will use another of
your allocated activations. MAK activation is designed for machines that
are NEVER connected to your network (VPN counts as connected) in any
given six-month period. Therefore, we're talking about a machine that
goes out your door and you don't see it again for a very long time. MAK
keys should not be commonly or lightly used. In the reinstall scenario,
much as you can now, you can contact Microsoft at that time and explain
the situation and get another activation. 

 

KMS activation DOES NOT REPORT ANYTHING TO MICROSOFT. You activate the
KMS host against a Microsoft activation server, and your KMS clients get
activated by YOUR KMS host. Once a week, they try to renew. If renewal
is successful, the KMS client now has six months from that day to renew
again. The client will still renew once a week and will be extending
that six month window each time. In other words, you always have six
months from initial activation or renewal of activation before the
client MUST contact a KMS host again. If it's day 179 and your KMS host
has been down that entire time, when you bring it back up on day 179,
your clients can renew their activations for another six months. During
those 179 days while the KMS host was down, they are unaffected unless
their 180 days of validity expired during that time and they were unable
to locate and contact another KMS server.

 

If you reinstall the OS on a KMS-activated client, IT DOESN'T MATTER,
because Microsoft doesn't track KMS clients. In fact, even the KMS
server only keeps track of the last fifty activations it has performed.
Now, if you want to keep this information for your own records, you can
easily extract it from the event logs or you can use the MOM management
pack for KMS.

 

With KMS activation, you are simply saying to Microsoft, we anticipate
that we will have 10,000 [or whatever] Vista clients. Therefore, we'll
pay you for that many Vista clients. That's the end of the story as far
as Microsoft is concerned. If you exceed 10,000 active Vista clients,
then you're in violation of your agreement, but Microsoft won't know
about it via some magic mechanism. KMS-activated clients don't talk to
Microsoft. They talk to your KMS host. 

 

The step-by-step guide I referenced tends to look dry and overwhelming
to people and I suspect that many folks don't really sit down and take
the time to read it thoroughly (can't blame 'em), but it really is all
explained there.

 

Laura

 

Hopefully I didn't put any typos or other doofusness in the above; it's
been a bad week for me when it comes to typing. :-)

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Wade
Sent: Thursday, December 07, 2006 5:40 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS

I have read all this, and it seems any thing but straight
forward to me. It looks like we are going to have to invest a lot more
money in managing licenses

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-08 Thread AFidel
If it's so well baked then how do you support multiple remote offices with 
slow VPN links, or none at all? How do you support field users without a 
VPN client, or using an SSL based VPN? Making us use two different images 
(one for each key type) isn't a solution since it doubles our support work 
and clients may move from one model to the other. There are plenty of 
situations where it just doesn't work well for IT in the real world.

Thanks,
Andrew Fidel



Laura A. Robinson [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
12/05/2006 04:43 PM
Please respond to
ActiveDir@mail.activedir.org


To
ActiveDir@mail.activedir.org
cc

Subject
RE: [ActiveDir] OT: Vista Activation and KMS






The Windows Server 2003 KMS host will be out soon. In the meantime, Vista 
is
perfectly acceptable to use and it's incredibly simple to decommission it 
as
a KMS host when you implement a Win2K3 host. No TAM support needed.

Again, I'd really encourage people to thorougly read the documents I
referenced before, because I'm seeing a lot of confusion on this list that
indicates that people aren't really understanding how this works (not you 
in
particular, Susan, just a general comment as I've been watching the VLA
comments for a little while). 

Or if you're Neil, you can schedule a LiveMeeting and I'll explain it,
because Neil's company is one of my district's customers. ;-)

Laura 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Tuesday, December 05, 2006 3:21 PM
 To: ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS
 
 I personally am not ready to stick a Vista box as a 
 Licensing server.
 
 ISA still doesn't have a firewall client that works for 
 one... and I've yet to find a a/v that doesn't BSOD my tablet 
 pc or act strangely on another box I built.
 
 In fact I'm still using my Technet 'for testing purposes' 
 ones as I'm not ready to play with my VL ones.  Activation on 
 the VL ones means I'm serious to roll...and quite frankly.. I'm not.
 
 I still want to see a more formal support story on 
 Activations in general for folks that aren't TAM supported...
 
 YMMV and all that.
 
 Laura A. Robinson wrote:
  I am not at all talking about solutions that don't exist 
 today. Go to 
  a Vista machine and take a look at slmgr.vbs.
  
  Laura
 
  
 --
 --
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf Of *Tim
  Vander Kooi
  *Sent:* Tuesday, December 05, 2006 12:39 PM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS
 
  While Laura and yourself make valid points, you are both talking
  about solutions that do not exist today. I?m just trying to help
  the OP with the problem he is having right now. Getting into the
  full licensing overhead of Vista, not to mention LH, could, and
  undoubtedly will, take weeks and/or months.
 
  For right now, at this very moment, using your VL key 
 (and I will
  continue to refer to it as a VL key as long as the page 
 on which I
  am reading it says ? Volume License Product Keys? at the top of
  it) for Vista ? KMS will allow you to activate your installation
  via the web just fine. This is not something I would do for an
  entire enterprise, but for your first few test machines on your
  production network I would do it.
 
  Again YMMV,
 
  Tim
 
  
 
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf 
 Of *Harvey
  Kamangwitz
  *Sent:* Tuesday, December 05, 2006 10:28 AM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS
 
  
 
  If you have any kind of a complex environment, you'll 
 find volume
  activation to be very frustrating indeed:
 
  
 
  1. The KMS service can't support more than one key, so 
 if you have
  Longhorn VL clients in your environment you have to put up a
  second KMS infrastructure for them.
 
  
 
  2. You can't (rather, shouldn't) use autodiscovery If 
 you do have
  both LH and Vista.  The KMS client can't distinguish 
 between a KMS
  with LH and a KMS with Vista, and there's nothing in the client
  that says oh, I hit a KMS but it has the wrong key so try again
  immediately so ~50% of a client's activation attempts 
 will fail.
 
  
 
  3.  Autodiscovery isn't practical if you have more than a few
  forests that don't trust the forest your KMS is in. All 
 admins of
  the untrusted forests must manually register the _vlmcs 
 record in
  their forest to find the KMS.
 
  
 
  ...the list goes on. (I haven't even mentioned the practical
  aspects of volume activation in a lab or firewalled 
 environment.)
  It's not a fully-baked solution.
 
  
 
  Depending

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-08 Thread Laura A. Robinson
1. The entire conversation is ~450 BYTES of traffic. If you can't swing that
over six months, you have bigger problems than activation. SSL-based VPN
changes nothing. Connectivity is connectivity. Why do you assume that
activation can't occur over an SSL-based VPN?
2. If you have no links at all, either look at a KMS host at the remote
sites, or look at MAK activation. 
3. Who said anything about you having to have two different images?
 
Folks, please read the whitepapers and try this out before you reject it.
The expression tilting at windmills comes to mind with some of these
objections.
 
Laura


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, December 08, 2006 11:41 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS



If it's so well baked then how do you support multiple remote offices with
slow VPN links, or none at all? How do you support field users without a VPN
client, or using an SSL based VPN? Making us use two different images (one
for each key type) isn't a solution since it doubles our support work and
clients may move from one model to the other. There are plenty of situations
where it just doesn't work well for IT in the real world. 

Thanks, 
Andrew Fidel 



Laura A. Robinson [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED] 


12/05/2006 04:43 PM 


Please respond to
ActiveDir@mail.activedir.org



To
ActiveDir@mail.activedir.org 

cc

Subject
RE: [ActiveDir] OT: Vista Activation and KMS






The Windows Server 2003 KMS host will be out soon. In the meantime, Vista is
perfectly acceptable to use and it's incredibly simple to decommission it as
a KMS host when you implement a Win2K3 host. No TAM support needed.

Again, I'd really encourage people to thorougly read the documents I
referenced before, because I'm seeing a lot of confusion on this list that
indicates that people aren't really understanding how this works (not you in
particular, Susan, just a general comment as I've been watching the VLA
comments for a little while). 

Or if you're Neil, you can schedule a LiveMeeting and I'll explain it,
because Neil's company is one of my district's customers. ;-)

Laura 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Tuesday, December 05, 2006 3:21 PM
 To: ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS
 
 I personally am not ready to stick a Vista box as a 
 Licensing server.
 
 ISA still doesn't have a firewall client that works for 
 one... and I've yet to find a a/v that doesn't BSOD my tablet 
 pc or act strangely on another box I built.
 
 In fact I'm still using my Technet 'for testing purposes' 
 ones as I'm not ready to play with my VL ones.  Activation on 
 the VL ones means I'm serious to roll...and quite frankly.. I'm not.
 
 I still want to see a more formal support story on 
 Activations in general for folks that aren't TAM supported...
 
 YMMV and all that.
 
 Laura A. Robinson wrote:
  I am not at all talking about solutions that don't exist 
 today. Go to 
  a Vista machine and take a look at slmgr.vbs.
   
  Laura
 
  
 --
 --
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf Of *Tim
  Vander Kooi
  *Sent:* Tuesday, December 05, 2006 12:39 PM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS
 
  While Laura and yourself make valid points, you are both talking
  about solutions that do not exist today. I’m just trying to help
  the OP with the problem he is having right now. Getting into the
  full licensing overhead of Vista, not to mention LH, could, and
  undoubtedly will, take weeks and/or months.
 
  For right now, at this very moment, using your VL key 
 (and I will
  continue to refer to it as a VL key as long as the page 
 on which I
  am reading it says “ Volume License Product Keys” at the top of
  it) for Vista – KMS will allow you to activate your installation
  via the web just fine. This is not something I would do for an
  entire enterprise, but for your first few test machines on your
  production network I would do it.
 
  Again YMMV,
 
  Tim
 
   
 
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf 
 Of *Harvey
  Kamangwitz
  *Sent:* Tuesday, December 05, 2006 10:28 AM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS
 
   
 
  If you have any kind of a complex environment, you'll 
 find volume
  activation to be very frustrating indeed:
 
   
 
  1. The KMS service can't support more than one key, so 
 if you have
  Longhorn VL clients in your environment you have to put up a
  second

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-08 Thread MikeM

So Laura, correct me if I'm wrong, but are you suggesting we read the white
paper?

Seriously, thank you for all of the input on this matter.

-MM-

On 12/8/06, Laura A. Robinson [EMAIL PROTECTED] wrote:


 1. The entire conversation is ~450 BYTES of traffic. If you can't swing
that over six months, you have bigger problems than activation. SSL-based
VPN changes nothing. Connectivity is connectivity. Why do you assume that
activation can't occur over an SSL-based VPN?
2. If you have no links at all, either look at a KMS host at the remote
sites, or look at MAK activation.
3. Who said anything about you having to have two different images?

Folks, please read the whitepapers and try this out before you reject it.
The expression tilting at windmills comes to mind with some of these
objections.

Laura

 --
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of [EMAIL PROTECTED]
*Sent:* Friday, December 08, 2006 11:41 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* RE: [ActiveDir] OT: Vista Activation and KMS


If it's so well baked then how do you support multiple remote offices with
slow VPN links, or none at all? How do you support field users without a VPN
client, or using an SSL based VPN? Making us use two different images (one
for each key type) isn't a solution since it doubles our support work and
clients may move from one model to the other. There are plenty of situations
where it just doesn't work well for IT in the real world.

Thanks,
Andrew Fidel


  *Laura A. Robinson [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]

12/05/2006 04:43 PM   Please respond to
ActiveDir@mail.activedir.org

   To
ActiveDir@mail.activedir.org  cc

 Subject
RE: [ActiveDir] OT: Vista Activation and KMS






The Windows Server 2003 KMS host will be out soon. In the meantime, Vista
is
perfectly acceptable to use and it's incredibly simple to decommission it
as
a KMS host when you implement a Win2K3 host. No TAM support needed.

Again, I'd really encourage people to thorougly read the documents I
referenced before, because I'm seeing a lot of confusion on this list that
indicates that people aren't really understanding how this works (not you
in
particular, Susan, just a general comment as I've been watching the VLA
comments for a little while).

Or if you're Neil, you can schedule a LiveMeeting and I'll explain it,
because Neil's company is one of my district's customers. ;-)

Laura

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Tuesday, December 05, 2006 3:21 PM
 To: ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 I personally am not ready to stick a Vista box as a
 Licensing server.

 ISA still doesn't have a firewall client that works for
 one... and I've yet to find a a/v that doesn't BSOD my tablet
 pc or act strangely on another box I built.

 In fact I'm still using my Technet 'for testing purposes'
 ones as I'm not ready to play with my VL ones.  Activation on
 the VL ones means I'm serious to roll...and quite frankly.. I'm not.

 I still want to see a more formal support story on
 Activations in general for folks that aren't TAM supported...

 YMMV and all that.

 Laura A. Robinson wrote:
  I am not at all talking about solutions that don't exist
 today. Go to
  a Vista machine and take a look at slmgr.vbs.
 
  Laura
 
 
 --
 --
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf Of *Tim
  Vander Kooi
  *Sent:* Tuesday, December 05, 2006 12:39 PM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS
 
  While Laura and yourself make valid points, you are both talking
  about solutions that do not exist today. I'm just trying to help
  the OP with the problem he is having right now. Getting into the
  full licensing overhead of Vista, not to mention LH, could, and
  undoubtedly will, take weeks and/or months.
 
  For right now, at this very moment, using your VL key
 (and I will
  continue to refer to it as a VL key as long as the page
 on which I
  am reading it says  Volume License Product Keys at the top of
  it) for Vista – KMS will allow you to activate your installation
  via the web just fine. This is not something I would do for an
  entire enterprise, but for your first few test machines on your
  production network I would do it.
 
  Again YMMV,
 
  Tim
 
 
 
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf
 Of *Harvey
  Kamangwitz
  *Sent:* Tuesday, December 05, 2006 10:28 AM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS
 
 
 
  If you have any kind of a complex environment, you'll
 find volume
  activation to be very

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-07 Thread Dave Wade
I have read all this, and it seems any thing but straight forward to me.
It looks like we are going to have to invest a lot more money in
managing licenses.
 
I could also find nothing about what happens if we need to re-install
Windows. It appears we need to re-activate, and it appears as its a new
sid it will use a second license... Any one any pointers on this?
 




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laura A.
Robinson
Sent: 05 December 2006 00:57
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS


Actually, it is clearly documented, along with a lot more
information on KMS, MAK and Vista Volume Activation (btw, Volume
Licensing doesn't exist in Vista; VL and VA are not the same things).
You probably don't want to get me started on a big long explanation of
how volume activation works, so I'll just point you to this site:
http://www.microsoft.com/technet/windowsvista/plan/volact.mspx
:-)
 
I highly recommend both the FAQ and the step-by-step guide. The
latter provides information on how to change from KMS to MAK and vice
versa (there are several ways), as well as documentation of defaults,
configuration options, etc.
 
Laura
 
 




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim Vander Kooi
Sent: Monday, December 04, 2006 2:44 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS



You need to go to Control Panel  System then at the
bottom select Change Product Key. This will allow you to enter your VL
key which will result in Vista activating via the web. Definitely not
well documented unfortunately.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Cline
Sent: Monday, December 04, 2006 11:45 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Vista Activation and KMS

 

I was testing out the RTM of Vista Enterprise last night
and noticed I didn't have to enter a key at any point during the
install. When Windows tried to activate, it told me there was a DNS
error, so I suspected it looks for a local activation server by default.
Sure enough, in the DNS cache was a lookup for a nonexistent
_vlmcs._tcp.domain.com. Upon further research, it appears Microsoft has
not released KMS yet, and I couldn't find any option to activate
directly with Microsoft. For the moment, is telephone activation the
only option?

Brian Cline, Applications Developer 
Department of Information Technology 
GP Trucking Company, Inc. 
803.936.8595 Direct Line 
800.922.1147 Toll-Free (x8595) 
803.739.1176 Fax 


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 -
Release Date: 12/4/2006 7:18 AM



--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date:
12/4/2006 7:18 AM




**
This email, and any files transmitted with it, is confidential and
intended solely for the use of the individual or entity to whom they
are addressed. As a public body, the Council may be required to disclose this 
email,  or any response to it,  under the Freedom of Information Act 2000, 
unless the information in it is covered by one of the exemptions in the Act. 

If you receive this email in error please notify Stockport e-Services via 
[EMAIL PROTECTED] and then permanently remove it from your system. 

Thank you.

http://www.stockport.gov.uk
**



RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-07 Thread Khurshid_Anwar
Return Receipt
   
   Your   RE: [ActiveDir] OT: Vista Activation and KMS 
   document:   
   
   was[EMAIL PROTECTED]
   received
   by: 
   
   at:12/07/2006 09:42:44 AM EST   
   




List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-07 Thread Rich Milburn
 ISA still doesn't have a firewall client that works for one...
You noticed that one, did you?  

Though I have had pretty good experience in general with Vista on good
hardware.  If I built a Vista box for KMS only, I would turn off aero
and probably disable the sound card and maybe some other stuff
(indexing, we could keep going) but then I would have pretty good
confidence in the Vista box. At present I think that's the way I'd
recommend us doing it, until it'll run on a server of some sort.

Fortunately  (as has probably been discussed here at length seeing Laura
R's affinity for slmgr.vbs :)  you can of course test on a VL copy for
90 (or is it 120?) days - 
slmgr.vbs -rearm
extends for 30 days, and you can run it either 2 or 3 times (I don't
recall which)...

Rich

---
Rich Milburn
MCSE, Microsoft MVP - Directory Services
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.
4551 W. 107th St
Overland Park, KS 66207
913-967-2819
--
I love the smell of red herrings in the morning - anonymous

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Bradley,
CPA aka Ebitz - SBS Rocks [MVP]
Sent: Tuesday, December 05, 2006 2:21 PM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

I personally am not ready to stick a Vista box as a Licensing server.

ISA still doesn't have a firewall client that works for one... and I've 
yet to find a a/v that doesn't BSOD my tablet pc or act strangely on 
another box I built.

In fact I'm still using my Technet 'for testing purposes' ones as I'm 
not ready to play with my VL ones.  Activation on the VL ones means I'm

serious to roll...and quite frankly.. I'm not.

I still want to see a more formal support story on Activations in 
general for folks that aren't TAM supported...

YMMV and all that.

Laura A. Robinson wrote:
 I am not at all talking about solutions that don't exist today. Go to 
 a Vista machine and take a look at slmgr.vbs.
  
 Laura



 *From:* [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] *On Behalf Of *Tim
 Vander Kooi
 *Sent:* Tuesday, December 05, 2006 12:39 PM
 *To:* ActiveDir@mail.activedir.org
 *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS

 While Laura and yourself make valid points, you are both talking
 about solutions that do not exist today. I'm just trying to help
 the OP with the problem he is having right now. Getting into the
 full licensing overhead of Vista, not to mention LH, could, and
 undoubtedly will, take weeks and/or months.

 For right now, at this very moment, using your VL key (and I will
 continue to refer to it as a VL key as long as the page on which I
 am reading it says  Volume License Product Keys at the top of
 it) for Vista - KMS will allow you to activate your installation
 via the web just fine. This is not something I would do for an
 entire enterprise, but for your first few test machines on your
 production network I would do it.

 Again YMMV,

 Tim

  

 *From:* [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] *On Behalf Of *Harvey
 Kamangwitz
 *Sent:* Tuesday, December 05, 2006 10:28 AM
 *To:* ActiveDir@mail.activedir.org
 *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS

  

 If you have any kind of a complex environment, you'll find volume
 activation to be very frustrating indeed:

  

 1. The KMS service can't support more than one key, so if you have
 Longhorn VL clients in your environment you have to put up a
 second KMS infrastructure for them.

  

 2. You can't (rather, shouldn't) use autodiscovery If you do have
 both LH and Vista.  The KMS client can't distinguish between a KMS
 with LH and a KMS with Vista, and there's nothing in the client
 that says oh, I hit a KMS but it has the wrong key so try again
 immediately so ~50% of a client's activation attempts will fail.

  

 3.  Autodiscovery isn't practical if you have more than a few
 forests that don't trust the forest your KMS is in. All admins of
 the untrusted forests must manually register the _vlmcs record in
 their forest to find the KMS.

  

 ...the list goes on. (I haven't even mentioned the practical
 aspects of volume activation in a lab or firewalled environment.)
 It's not a fully-baked solution.

  

 Depending on your environment, it might be easier to scrap the
 whole autodiscovery, create a DNS CNAME with a couple of KMS
 behind it, stuff the FQDN in the KMS client's registry if you have
 a standard build, and fugeddaboutit :-).

  



  

 On 12/4/06, *Laura A. Robinson* [EMAIL PROTECTED

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-07 Thread Rich Milburn
 My hope was that KMS could support more than one key. I was astonished
when I discovered it didn't. If you were Vista, KMS would supply you
with a Vista key. Longhorn, a Longhorn key. Since KMS only supports one
key, it triggers the need for two separate KMS infrastructures and the
problems in #2 below.   

 

I put this up in the beta volume licensing group, hopefully there will
be some MSFT response on this.  I agree with you - the point of making
it easy by allowing srv records is offset by the fact neither the VL
client nor the KMS server can differentiate between Vista and LHS.  Even
if the solution is to update the KMS service prior to longhorn's
release, and have separate srv records (one for Vista, one for longhorn,
another for ?? because you know they're on a roll now and will soon have
other things doing VLA)  personally I'd rather have multiple records
than multiple KMS servers, and hard-coding reg keys or using MAKS for
all servers is not really a good solution, IMHO.

 

Rich

 

---
Rich Milburn
MCSE, Microsoft MVP - Directory Services
Sr Network Analyst, Field Platform Development
Applebee's International, Inc.
4551 W. 107th St
Overland Park, KS 66207
913-967-2819
--
I love the smell of red herrings in the morning - anonymous

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey
Kamangwitz
Sent: Tuesday, December 05, 2006 11:41 PM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

 

On 12/5/06, Laura A. Robinson [EMAIL PROTECTED] wrote:

Inline...

 



From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

If you have any kind of a complex environment, you'll
find volume activation to be very frustrating indeed:

 

1. The KMS service can't support more than one key, so
if you have Longhorn VL clients in your environment you have to put up a
second KMS infrastructure for them.  

 

Actually, when you purchase a KMS key, you get to
activate TWO KMS hosts with that key, up to ten times each. Therefore,
you don't have to put up a second KMS infrastructure.  

From a subsequent post on this thread:

Doh! Okay, now I think I get what you're referencing in item 1.

There's a reason for that- LH isn't out yet. When LH is out, that won't
be an issue. :-)

 

My hope was that KMS could support more than one key. I was astonished
when I discovered it didn't. If you were Vista, KMS would supply you
with a Vista key. Longhorn, a Longhorn key. Since KMS only supports one
key, it triggers the need for two separate KMS infrastructures and the
problems in #2 below.   I'm assuming that Microsoft will be using Volume
Activation for other products in the future; are we to put up a separate
KMS for each?


 

 

2. You can't (rather, shouldn't) use autodiscovery If
you do have both LH and Vista.  The KMS client can't distinguish between
a KMS with LH and a KMS with Vista, and there's nothing in the client
that says oh, I hit a KMS but it has the wrong key so try again
immediately so ~50% of a client's activation attempts will fail.   

 

So remove the DNS records for the LH KMS, or am I
misunderstanding your point? 

To be more specific: In a Vista / Longhorn environment, you should only
use autodiscovery for one KMS infrastructure because of 50% failure rate
above. The other systems (Longhorn, if you choose autodiscovery for
Vista) must be explictly pointed to a KMS with slmgr. How much of an
adminstrative headache this is depends on how great a penetration of a
standard build is in your company; you can code it into the build. 

 


 

 

3.  Autodiscovery isn't practical if you have more than
a few forests that don't trust the forest your KMS is in. All admins of
the untrusted forests must manually register the _vlmcs record in their
forest to find the KMS.   

 

slmgr.vbs. We're not talking about a ton of records here
or a difficult population mechanism.  

It's the logistics and overhead that's a pain. No, the act of
registering a _vlmcs record in a domain is not in itself a difficult
task; it's the help desk scripts and calls from panicky system
administrators when all the clients in their forest start complaining
about failure to activate and reduced functionality mode that have
to be handled. In a large enterprise we could see a lot of these
(everyone that brings up a sandbox forest

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-07 Thread Laura A. Robinson
Okay, let me see if I can summarize this in a gazillion words or less...
 
There are two types of activations for Vista- MAK activation and KMS
activation.
 
MAK activation works much like an MSDN subscription. You tell Microsoft how
many MAK activations you want to purchase. Microsoft sells you a MAK key
with that many activations. A machine that is activated via MAK activation
never has to renew. A MAK-activated client either directly contacts
Microsoft servers for activation or (in 2007, when the VAMT tool is
released) it activates against a proxy in your company that feeds the
activation to Microsoft activation servers. If you reinstall the OS and
specify MAK activation again, then that will use another of your allocated
activations. MAK activation is designed for machines that are NEVER
connected to your network (VPN counts as connected) in any given six-month
period. Therefore, we're talking about a machine that goes out your door and
you don't see it again for a very long time. MAK keys should not be commonly
or lightly used. In the reinstall scenario, much as you can now, you can
contact Microsoft at that time and explain the situation and get another
activation. 
 
KMS activation DOES NOT REPORT ANYTHING TO MICROSOFT. You activate the KMS
host against a Microsoft activation server, and your KMS clients get
activated by YOUR KMS host. Once a week, they try to renew. If renewal is
successful, the KMS client now has six months from that day to renew again.
The client will still renew once a week and will be extending that six month
window each time. In other words, you always have six months from initial
activation or renewal of activation before the client MUST contact a KMS
host again. If it's day 179 and your KMS host has been down that entire
time, when you bring it back up on day 179, your clients can renew their
activations for another six months. During those 179 days while the KMS host
was down, they are unaffected unless their 180 days of validity expired
during that time and they were unable to locate and contact another KMS
server.
 
If you reinstall the OS on a KMS-activated client, IT DOESN'T MATTER,
because Microsoft doesn't track KMS clients. In fact, even the KMS server
only keeps track of the last fifty activations it has performed. Now, if you
want to keep this information for your own records, you can easily extract
it from the event logs or you can use the MOM management pack for KMS.
 
With KMS activation, you are simply saying to Microsoft, we anticipate that
we will have 10,000 [or whatever] Vista clients. Therefore, we'll pay you
for that many Vista clients. That's the end of the story as far as
Microsoft is concerned. If you exceed 10,000 active Vista clients, then
you're in violation of your agreement, but Microsoft won't know about it via
some magic mechanism. KMS-activated clients don't talk to Microsoft. They
talk to your KMS host. 
 
The step-by-step guide I referenced tends to look dry and overwhelming to
people and I suspect that many folks don't really sit down and take the time
to read it thoroughly (can't blame 'em), but it really is all explained
there.
 
Laura
 
Hopefully I didn't put any typos or other doofusness in the above; it's been
a bad week for me when it comes to typing. :-)


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Wade
Sent: Thursday, December 07, 2006 5:40 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS


I have read all this, and it seems any thing but straight forward to me. It
looks like we are going to have to invest a lot more money in managing
licenses.
 
I could also find nothing about what happens if we need to re-install
Windows. It appears we need to re-activate, and it appears as its a new sid
it will use a second license... Any one any pointers on this?
 


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laura A. Robinson
Sent: 05 December 2006 00:57
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS


Actually, it is clearly documented, along with a lot more information on
KMS, MAK and Vista Volume Activation (btw, Volume Licensing doesn't exist in
Vista; VL and VA are not the same things). You probably don't want to get me
started on a big long explanation of how volume activation works, so I'll
just point you to this site:
HYPERLINK
http://www.microsoft.com/technet/windowsvista/plan/volact.mspxhttp://www.m
icrosoft.com/technet/windowsvista/plan/volact.mspx
:-)
 
I highly recommend both the FAQ and the step-by-step guide. The latter
provides information on how to change from KMS to MAK and vice versa (there
are several ways), as well as documentation of defaults, configuration
options, etc.
 
Laura
 
 


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim Vander Kooi
Sent: Monday, December 04, 2006 2:44 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-06 Thread Brian Cline
Wow, 18 replies. I really appreciate all the information, folks. I've already 
read some of the resources out there on KMS and MAK, but it seems I managed to 
overlook the more important technical ones. I'll have a gander - thanks again.

--
Brian Cline



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Wednesday 06 December 2006 00:41
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS




On 12/5/06, Laura A. Robinson [EMAIL PROTECTED] wrote:

Inline...




From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of 
Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

If you have any kind of a complex environment, you'll find 
volume activation to be very frustrating indeed:
 
1. The KMS service can't support more than one key, so if you 
have Longhorn VL clients in your environment you have to put up a second KMS 
infrastructure for them.  
 
Actually, when you purchase a KMS key, you get to activate TWO 
KMS hosts with that key, up to ten times each. Therefore, you don't have to put 
up a second KMS infrastructure.  

From a subsequent post on this thread:
Doh! Okay, now I think I get what you're referencing in item 1.
There's a reason for that- LH isn't out yet. When LH is out, that won't be an 
issue. :-)
 
My hope was that KMS could support more than one key. I was astonished when I 
discovered it didn't. If you were Vista, KMS would supply you with a Vista key. 
Longhorn, a Longhorn key. Since KMS only supports one key, it triggers the need 
for two separate KMS infrastructures and the problems in #2 below.   I'm 
assuming that Microsoft will be using Volume Activation for other products in 
the future; are we to put up a separate KMS for each?

 


 
2. You can't (rather, shouldn't) use autodiscovery If you do 
have both LH and Vista.  The KMS client can't distinguish between a KMS with LH 
and a KMS with Vista, and there's nothing in the client that says oh, I hit a 
KMS but it has the wrong key so try again immediately so ~50% of a client's 
activation attempts will fail.   
 
So remove the DNS records for the LH KMS, or am I 
misunderstanding your point? 

To be more specific: In a Vista / Longhorn environment, you should only use 
autodiscovery for one KMS infrastructure because of 50% failure rate above. The 
other systems (Longhorn, if you choose autodiscovery for Vista) must be 
explictly pointed to a KMS with slmgr. How much of an adminstrative headache 
this is depends on how great a penetration of a standard build is in your 
company; you can code it into the build. 
 

 


 
3.  Autodiscovery isn't practical if you have more than a few 
forests that don't trust the forest your KMS is in. All admins of the untrusted 
forests must manually register the _vlmcs record in their forest to find the 
KMS.   
 
slmgr.vbs. We're not talking about a ton of records here or a 
difficult population mechanism.  

It's the logistics and overhead that's a pain. No, the act of registering a 
_vlmcs record in a domain is not in itself a difficult task; it's the help desk 
scripts and calls from panicky system administrators when all the clients in 
their forest start complaining about failure to activate and reduced 
functionality mode that have to be handled. In a large enterprise we could see 
a lot of these (everyone that brings up a sandbox forest for application 
testing, for example). I'm attempting to design a solution that minimizes the 
impact for everybody - corporate forest administrators, Vista users, help desk, 
untrusted test forest administrators, etc. 
 

 


 
...the list goes on. (I haven't even mentioned the practical 
aspects of volume activation in a lab or firewalled environment.)  
 
I'd be happy to discuss your options around them if you should 
decide to elaborate further.

 
If the firewalled labs don't want to open port 1688 to find a KMS, they either 
have to bring up their own KMS or use MAKs. I for one don't want to hand out 
KMS / volume keys to anyone outside the corporate KMS infrastructure. And MAKs, 
though I haven't studied them as closely, are a pain for labs that rebuild 
their clients because they're a single-use item (by which I mean that if you 
use up one activation count on a MAK then rebuild, it increments the MAK count 
- you can't reuse the previous one). And they still require some kind

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Harvey Kamangwitz

If you have any kind of a complex environment, you'll find volume activation
to be very frustrating indeed:

1. The KMS service can't support more than one key, so if you have Longhorn
VL clients in your environment you have to put up a second KMS
infrastructure for them.

2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail.

3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS.

...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.) It's not a
fully-baked solution.

Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-).




On 12/4/06, Laura A. Robinson [EMAIL PROTECTED] wrote:


KMS runs on Vista (now), will run on Longhorn when Longhorn is released,
and
will also run on Win2K3 as soon as we finish making the Win2K3 install.
:-)

Laura

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto: [EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Monday, December 04, 2006 1:12 PM
 To: ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically.

 Have your MVLS folks request the other type of key is my
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year.

 Brian Cline wrote:
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595)
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 http://www.threatcode.com

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 http://blogs.technet.com/sbs

 List info   : http://www.activedir.org/List.aspx
 List FAQ: http://www.activedir.org/ListFAQ.aspx
 List archive:
 http://www.mail-archive.com/activedir@mail.activedir.org/

 --
 No virus found in this incoming message.
 Checked by AVG Free Edition.
 Version: 7.5.430 / Virus Database: 268.15.6/567 - Release
 Date: 12/4/2006 7:18 AM



--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/





--
S.


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Tim Vander Kooi
While Laura and yourself make valid points, you are both talking about
solutions that do not exist today. I'm just trying to help the OP with
the problem he is having right now. Getting into the full licensing
overhead of Vista, not to mention LH, could, and undoubtedly will, take
weeks and/or months.

For right now, at this very moment, using your VL key (and I will
continue to refer to it as a VL key as long as the page on which I am
reading it says  Volume License Product Keys at the top of it) for
Vista - KMS will allow you to activate your installation via the web
just fine. This is not something I would do for an entire enterprise,
but for your first few test machines on your production network I would
do it.

Again YMMV,

Tim

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey
Kamangwitz
Sent: Tuesday, December 05, 2006 10:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

If you have any kind of a complex environment, you'll find volume
activation to be very frustrating indeed:

 

1. The KMS service can't support more than one key, so if you have
Longhorn VL clients in your environment you have to put up a second KMS
infrastructure for them.

 

2. You can't (rather, shouldn't) use autodiscovery If you do have both
LH and Vista.  The KMS client can't distinguish between a KMS with LH
and a KMS with Vista, and there's nothing in the client that says oh, I
hit a KMS but it has the wrong key so try again immediately so ~50% of
a client's activation attempts will fail. 

 

3.  Autodiscovery isn't practical if you have more than a few forests
that don't trust the forest your KMS is in. All admins of the untrusted
forests must manually register the _vlmcs record in their forest to find
the KMS. 

 

...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.) It's not a
fully-baked solution.

 

Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff
the FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-). 

 



 

On 12/4/06, Laura A. Robinson [EMAIL PROTECTED]  wrote: 

KMS runs on Vista (now), will run on Longhorn when Longhorn is released,
and
will also run on Win2K3 as soon as we finish making the Win2K3 install.
:-) 

Laura

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] 
 Sent: Monday, December 04, 2006 1:12 PM
 To: ActiveDir@mail.activedir.org 
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS 

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically. 

 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year. 

 Brian Cline wrote: 
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone 
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595) 
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 http://www.threatcode.com http://www.threatcode.com/ 

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 http://blogs.technet.com/sbs 

 List info   : http://www.activedir.org/List.aspx
 List FAQ: http://www.activedir.org/ListFAQ.aspx 
 List archive:
 http://www.mail-archive.com/activedir@mail.activedir.org/

 --
 No virus found in this incoming message. 
 Checked by AVG Free Edition.
 Version: 7.5.430 / Virus Database: 268.15.6/567 - Release 
 Date: 12/4/2006 7:18 AM



--
No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date:
12/4/2006
7:18 AM 


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/ 




-- 
S. 



RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Laura A. Robinson
Inline...


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS


If you have any kind of a complex environment, you'll find volume activation
to be very frustrating indeed:
 
1. The KMS service can't support more than one key, so if you have Longhorn
VL clients in your environment you have to put up a second KMS
infrastructure for them. 
 
Actually, when you purchase a KMS key, you get to activate TWO KMS hosts
with that key, up to ten times each. Therefore, you don't have to put up a
second KMS infrastructure. 
 
2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail.  
 
So remove the DNS records for the LH KMS, or am I misunderstanding your
point? 
 
3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS.  
 
slmgr.vbs. We're not talking about a ton of records here or a difficult
population mechanism.  
 
...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.)  
 
I'd be happy to discuss your options around them if you should decide to
elaborate further.
 
 It's not a fully-baked solution. 
 
I would tend to disagree. From a technical standpoint, I think it's pretty
well-baked. From a business process standpoint, it's still coming up to
speed. 
 
Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-).  
 
I'm not really understanding your concerns about autodiscovery. Could you be
more specific about your environment? 
 
Laura
 


 
On 12/4/06, Laura A. Robinson HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]  wrote: 

KMS runs on Vista (now), will run on Longhorn when Longhorn is released, and
will also run on Win2K3 as soon as we finish making the Win2K3 install. :-) 

Laura

 -Original Message-
 From: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 
 [mailto:HYPERLINK mailto:[EMAIL PROTECTED] \n
[EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] 
 Sent: Monday, December 04, 2006 1:12 PM
 To: HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED] 
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS 

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically. 

 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year. 

 Brian Cline wrote: 
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone 
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595) 
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 HYPERLINK http://www.threatcode.com/; \nhttp://www.threatcode.com

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 HYPERLINK http://blogs.technet.com/sbs; \nhttp://blogs.technet.com/sbs 

 List info   : HYPERLINK http://www.activedir.org/List.aspx;
\nhttp://www.activedir.org/List.aspx
 List FAQ: HYPERLINK http://www.activedir.org/ListFAQ.aspx;
\nhttp://www.activedir.org/ListFAQ.aspx 
 List archive:
 HYPERLINK http://www.mail-archive.com/activedir@mail.activedir.org/;
\nhttp://www.mail-archive.com/activedir@mail.activedir.org/

 --
 No virus found in this incoming message. 
 Checked by AVG Free Edition.
 Version: 7.5.430 / Virus Database: 268.15.6/567 - Release 
 Date: 12/4/2006 7:18 AM



--
No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Laura A. Robinson
I am not at all talking about solutions that don't exist today. Go to a
Vista machine and take a look at slmgr.vbs.
 
Laura


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim Vander Kooi
Sent: Tuesday, December 05, 2006 12:39 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS



While Laura and yourself make valid points, you are both talking about
solutions that do not exist today. I’m just trying to help the OP with the
problem he is having right now. Getting into the full licensing overhead of
Vista, not to mention LH, could, and undoubtedly will, take weeks and/or
months.

For right now, at this very moment, using your VL key (and I will continue
to refer to it as a VL key as long as the page on which I am reading it says
“ Volume License Product Keys” at the top of it) for Vista – KMS will allow
you to activate your installation via the web just fine. This is not
something I would do for an entire enterprise, but for your first few test
machines on your production network I would do it.

Again YMMV,

Tim

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 10:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 

If you have any kind of a complex environment, you'll find volume activation
to be very frustrating indeed:

 

1. The KMS service can't support more than one key, so if you have Longhorn
VL clients in your environment you have to put up a second KMS
infrastructure for them.

 

2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail. 

 

3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS. 

 

...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.) It's not a
fully-baked solution.

 

Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-). 

 



 

On 12/4/06, Laura A. Robinson HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]  wrote: 

KMS runs on Vista (now), will run on Longhorn when Longhorn is released, and
will also run on Win2K3 as soon as we finish making the Win2K3 install. :-) 

Laura

 -Original Message-
 From: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 
 [mailto:HYPERLINK mailto:[EMAIL PROTECTED] \n
[EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] 
 Sent: Monday, December 04, 2006 1:12 PM
 To: HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED] 
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS 

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically. 

 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year. 

 Brian Cline wrote: 
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone 
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595) 
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 HYPERLINK http://www.threatcode.com/; \nhttp://www.threatcode.com

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 HYPERLINK http://blogs.technet.com/sbs; \nhttp://blogs.technet.com/sbs 

 List info   : HYPERLINK http://www.activedir.org/List.aspx;
\nhttp://www.activedir.org/List.aspx
 List FAQ: HYPERLINK http://www.activedir.org/ListFAQ.aspx;
\nhttp://www.activedir.org/ListFAQ.aspx 
 List archive:
 HYPERLINK http://www.mail-archive.com/activedir@mail.activedir.org/;
\nhttp://www.mail-archive.com

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Laura A. Robinson
Doh! Okay, now I think I get what you're referencing in item 1.
 
There's a reason for that- LH isn't out yet. When LH is out, that won't be
an issue. :-)
 
Laura


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laura A. Robinson
Sent: Tuesday, December 05, 2006 12:48 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS


Inline...


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS


If you have any kind of a complex environment, you'll find volume activation
to be very frustrating indeed:
 
1. The KMS service can't support more than one key, so if you have Longhorn
VL clients in your environment you have to put up a second KMS
infrastructure for them. 
 
Actually, when you purchase a KMS key, you get to activate TWO KMS hosts
with that key, up to ten times each. Therefore, you don't have to put up a
second KMS infrastructure. 
 
2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail.  
 
So remove the DNS records for the LH KMS, or am I misunderstanding your
point? 
 
3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS.  
 
slmgr.vbs. We're not talking about a ton of records here or a difficult
population mechanism.  
 
...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.)  
 
I'd be happy to discuss your options around them if you should decide to
elaborate further.
 
 It's not a fully-baked solution. 
 
I would tend to disagree. From a technical standpoint, I think it's pretty
well-baked. From a business process standpoint, it's still coming up to
speed. 
 
Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-).  
 
I'm not really understanding your concerns about autodiscovery. Could you be
more specific about your environment? 
 
Laura
 


 
On 12/4/06, Laura A. Robinson HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]  wrote: 

KMS runs on Vista (now), will run on Longhorn when Longhorn is released, and
will also run on Win2K3 as soon as we finish making the Win2K3 install. :-) 

Laura

 -Original Message-
 From: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 
 [mailto:HYPERLINK mailto:[EMAIL PROTECTED] \n
[EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] 
 Sent: Monday, December 04, 2006 1:12 PM
 To: HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED] 
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS 

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically. 

 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year. 

 Brian Cline wrote: 
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone 
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595) 
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 HYPERLINK http://www.threatcode.com/; \nhttp://www.threatcode.com

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 HYPERLINK http://blogs.technet.com/sbs; \nhttp://blogs.technet.com/sbs 

 List info   : HYPERLINK http://www.activedir.org/List.aspx;
\nhttp://www.activedir.org/List.aspx
 List FAQ: HYPERLINK http://www.activedir.org/ListFAQ.aspx;
\nhttp://www.activedir.org/ListFAQ.aspx 
 List archive:
 HYPERLINK http://www.mail-archive.com/activedir

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Phillip Partipilo
As much effort is going into the whole activation thing, why not just ship
it with a bloody dongle already.
 
 
Phillip Partipilo
Parametric Solutions Inc.
Jupiter, Florida
(561) 747-6107
 
 
 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS


If you have any kind of a complex environment, you'll find volume activation
to be very frustrating indeed:
 
1. The KMS service can't support more than one key, so if you have Longhorn
VL clients in your environment you have to put up a second KMS
infrastructure for them.
 
2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail. 
 
3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS. 
 
...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.) It's not a
fully-baked solution.
 
Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-). 
 


 
On 12/4/06, Laura A. Robinson [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]  wrote: 

KMS runs on Vista (now), will run on Longhorn when Longhorn is released, and
will also run on Win2K3 as soon as we finish making the Win2K3 install. :-) 

Laura

 -Original Message-
 From: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] 
 [mailto:  mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] 
 Sent: Monday, December 04, 2006 1:12 PM
 To: ActiveDir@mail.activedir.org  mailto:ActiveDir@mail.activedir.org 
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS 

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically. 

 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year. 

 Brian Cline wrote: 
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone 
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595) 
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 http://www.threatcode.com http://www.threatcode.com/ 

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 http://blogs.technet.com/sbs  http://blogs.technet.com/sbs 

 List info   : http://www.activedir.org/List.aspx
 List FAQ: http://www.activedir.org/ListFAQ.aspx
http://www.activedir.org/ListFAQ.aspx 
 List archive:
 http://www.mail-archive.com/activedir@mail.activedir.org/

 --
 No virus found in this incoming message. 
 Checked by AVG Free Edition.
 Version: 7.5.430 / Virus Database: 268.15.6/567 - Release 
 Date: 12/4/2006 7:18 AM



--
No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM 


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/
http://www.mail-archive.com/activedir@mail.activedir.org/ 





-- 
S. 


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Laura A. Robinson
I suspect that people aren't really familiarizing themselves with how
activation works. It's really not rocket science once you understand it.


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Phillip Partipilo
Sent: Tuesday, December 05, 2006 1:53 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS


As much effort is going into the whole activation thing, why not just ship
it with a bloody dongle already.
 
 
Phillip Partipilo
Parametric Solutions Inc.
Jupiter, Florida
(561) 747-6107
 
 
 

   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz
Sent: Tuesday, December 05, 2006 11:28 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] OT: Vista Activation and KMS


If you have any kind of a complex environment, you'll find volume activation
to be very frustrating indeed:
 
1. The KMS service can't support more than one key, so if you have Longhorn
VL clients in your environment you have to put up a second KMS
infrastructure for them.
 
2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail. 
 
3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS. 
 
...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.) It's not a
fully-baked solution.
 
Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-). 
 


 
On 12/4/06, Laura A. Robinson HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]  wrote: 

KMS runs on Vista (now), will run on Longhorn when Longhorn is released, and
will also run on Win2K3 as soon as we finish making the Win2K3 install. :-) 

Laura

 -Original Message-
 From: HYPERLINK mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] 
 [mailto:HYPERLINK mailto:[EMAIL PROTECTED] \n
[EMAIL PROTECTED] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] 
 Sent: Monday, December 04, 2006 1:12 PM
 To: HYPERLINK mailto:ActiveDir@mail.activedir.org;
[EMAIL PROTECTED] 
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS 

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically. 

 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a year. 

 Brian Cline wrote: 
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to
 activate
  directly with Microsoft. For the moment, is telephone 
 activation the
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595) 
  803.739.1176 Fax
 

 --
 Letting your vendors set your risk analysis these days?
 HYPERLINK http://www.threatcode.com/; \nhttp://www.threatcode.com

 If you are a SBSer and you don't subscribe to the SBS Blog...
 man ... I will hunt you down...
 HYPERLINK http://blogs.technet.com/sbs; \nhttp://blogs.technet.com/sbs 

 List info   : HYPERLINK http://www.activedir.org/List.aspx;
\nhttp://www.activedir.org/List.aspx
 List FAQ: HYPERLINK http://www.activedir.org/ListFAQ.aspx;
\nhttp://www.activedir.org/ListFAQ.aspx 
 List archive:
 HYPERLINK http://www.mail-archive.com/activedir@mail.activedir.org/;
\nhttp://www.mail-archive.com/activedir@mail.activedir.org/

 --
 No virus found in this incoming message. 
 Checked by AVG Free Edition.
 Version: 7.5.430 / Virus Database: 268.15.6/567 - Release 
 Date: 12/4/2006 7:18 AM



--
No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM 


List info   : HYPERLINK http://www.activedir.org/List.aspx;
\nhttp://www.activedir.org/List.aspx
List FAQ: HYPERLINK http://www.activedir.org/ListFAQ.aspx;
\nhttp

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]

I personally am not ready to stick a Vista box as a Licensing server.

ISA still doesn't have a firewall client that works for one... and I've 
yet to find a a/v that doesn't BSOD my tablet pc or act strangely on 
another box I built.


In fact I'm still using my Technet 'for testing purposes' ones as I'm 
not ready to play with my VL ones.  Activation on the VL ones means I'm 
serious to roll...and quite frankly.. I'm not.


I still want to see a more formal support story on Activations in 
general for folks that aren't TAM supported...


YMMV and all that.

Laura A. Robinson wrote:
I am not at all talking about solutions that don't exist today. Go to 
a Vista machine and take a look at slmgr.vbs.
 
Laura



*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of *Tim
Vander Kooi
*Sent:* Tuesday, December 05, 2006 12:39 PM
*To:* ActiveDir@mail.activedir.org
*Subject:* RE: [ActiveDir] OT: Vista Activation and KMS

While Laura and yourself make valid points, you are both talking
about solutions that do not exist today. I’m just trying to help
the OP with the problem he is having right now. Getting into the
full licensing overhead of Vista, not to mention LH, could, and
undoubtedly will, take weeks and/or months.

For right now, at this very moment, using your VL key (and I will
continue to refer to it as a VL key as long as the page on which I
am reading it says “ Volume License Product Keys” at the top of
it) for Vista – KMS will allow you to activate your installation
via the web just fine. This is not something I would do for an
entire enterprise, but for your first few test machines on your
production network I would do it.

Again YMMV,

Tim

 


*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of *Harvey
Kamangwitz
*Sent:* Tuesday, December 05, 2006 10:28 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS

 


If you have any kind of a complex environment, you'll find volume
activation to be very frustrating indeed:

 


1. The KMS service can't support more than one key, so if you have
Longhorn VL clients in your environment you have to put up a
second KMS infrastructure for them.

 


2. You can't (rather, shouldn't) use autodiscovery If you do have
both LH and Vista.  The KMS client can't distinguish between a KMS
with LH and a KMS with Vista, and there's nothing in the client
that says oh, I hit a KMS but it has the wrong key so try again
immediately so ~50% of a client's activation attempts will fail.

 


3.  Autodiscovery isn't practical if you have more than a few
forests that don't trust the forest your KMS is in. All admins of
the untrusted forests must manually register the _vlmcs record in
their forest to find the KMS.

 


...the list goes on. (I haven't even mentioned the practical
aspects of volume activation in a lab or firewalled environment.)
It's not a fully-baked solution.

 


Depending on your environment, it might be easier to scrap the
whole autodiscovery, create a DNS CNAME with a couple of KMS
behind it, stuff the FQDN in the KMS client's registry if you have
a standard build, and fugeddaboutit :-).

 




 


On 12/4/06, *Laura A. Robinson* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:

KMS runs on Vista (now), will run on Longhorn when Longhorn is
released, and
will also run on Win2K3 as soon as we finish making the Win2K3
install. :-)

Laura

 -Original Message-
 From: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
 [mailto: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]] On Behalf Of
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Monday, December 04, 2006 1:12 PM
 To: ActiveDir@mail.activedir.org
mailto:ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS

 Nope, I've done it web based.  At the present time there are
 two kinds of keycodes up on MVLS.. one that wants a KMS, the
 other that will phone home to Redmond automatically.

 Have your MVLS folks request the other type of key is my
 understanding how this will work for now.  The KMS type won't
 be out until Longhorn.

 KMS activations will have to phone home to your servers twice a
year.

 Brian Cline wrote:
 
  I was testing out the RTM of Vista Enterprise last night
 and noticed I
  didn't have to enter a key at any point during the install. When
  Windows tried to activate, it told me there was a DNS error, so I
  suspected it looks for a local activation server by default. Sure
  enough, in the DNS cache was a lookup for a nonexistent
  _vlmcs._tcp.domain.com

RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Laura A. Robinson
The Windows Server 2003 KMS host will be out soon. In the meantime, Vista is
perfectly acceptable to use and it's incredibly simple to decommission it as
a KMS host when you implement a Win2K3 host. No TAM support needed.

Again, I'd really encourage people to thorougly read the documents I
referenced before, because I'm seeing a lot of confusion on this list that
indicates that people aren't really understanding how this works (not you in
particular, Susan, just a general comment as I've been watching the VLA
comments for a little while). 

Or if you're Neil, you can schedule a LiveMeeting and I'll explain it,
because Neil's company is one of my district's customers. ;-)

Laura 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Tuesday, December 05, 2006 3:21 PM
 To: ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS
 
 I personally am not ready to stick a Vista box as a 
 Licensing server.
 
 ISA still doesn't have a firewall client that works for 
 one... and I've yet to find a a/v that doesn't BSOD my tablet 
 pc or act strangely on another box I built.
 
 In fact I'm still using my Technet 'for testing purposes' 
 ones as I'm not ready to play with my VL ones.  Activation on 
 the VL ones means I'm serious to roll...and quite frankly.. I'm not.
 
 I still want to see a more formal support story on 
 Activations in general for folks that aren't TAM supported...
 
 YMMV and all that.
 
 Laura A. Robinson wrote:
  I am not at all talking about solutions that don't exist 
 today. Go to 
  a Vista machine and take a look at slmgr.vbs.
   
  Laura
 
  
 --
 --
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf Of *Tim
  Vander Kooi
  *Sent:* Tuesday, December 05, 2006 12:39 PM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* RE: [ActiveDir] OT: Vista Activation and KMS
 
  While Laura and yourself make valid points, you are both talking
  about solutions that do not exist today. I’m just trying to help
  the OP with the problem he is having right now. Getting into the
  full licensing overhead of Vista, not to mention LH, could, and
  undoubtedly will, take weeks and/or months.
 
  For right now, at this very moment, using your VL key 
 (and I will
  continue to refer to it as a VL key as long as the page 
 on which I
  am reading it says “ Volume License Product Keys” at the top of
  it) for Vista – KMS will allow you to activate your installation
  via the web just fine. This is not something I would do for an
  entire enterprise, but for your first few test machines on your
  production network I would do it.
 
  Again YMMV,
 
  Tim
 
   
 
  *From:* [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] *On Behalf 
 Of *Harvey
  Kamangwitz
  *Sent:* Tuesday, December 05, 2006 10:28 AM
  *To:* ActiveDir@mail.activedir.org
  *Subject:* Re: [ActiveDir] OT: Vista Activation and KMS
 
   
 
  If you have any kind of a complex environment, you'll 
 find volume
  activation to be very frustrating indeed:
 
   
 
  1. The KMS service can't support more than one key, so 
 if you have
  Longhorn VL clients in your environment you have to put up a
  second KMS infrastructure for them.
 
   
 
  2. You can't (rather, shouldn't) use autodiscovery If 
 you do have
  both LH and Vista.  The KMS client can't distinguish 
 between a KMS
  with LH and a KMS with Vista, and there's nothing in the client
  that says oh, I hit a KMS but it has the wrong key so try again
  immediately so ~50% of a client's activation attempts 
 will fail.
 
   
 
  3.  Autodiscovery isn't practical if you have more than a few
  forests that don't trust the forest your KMS is in. All 
 admins of
  the untrusted forests must manually register the _vlmcs 
 record in
  their forest to find the KMS.
 
   
 
  ...the list goes on. (I haven't even mentioned the practical
  aspects of volume activation in a lab or firewalled 
 environment.)
  It's not a fully-baked solution.
 
   
 
  Depending on your environment, it might be easier to scrap the
  whole autodiscovery, create a DNS CNAME with a couple of KMS
  behind it, stuff the FQDN in the KMS client's registry 
 if you have
  a standard build, and fugeddaboutit :-).
 
   
 
 
 
   
 
  On 12/4/06, *Laura A. Robinson* [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED] wrote:
 
  KMS runs on Vista (now), will run on Longhorn when Longhorn is
  released, and
  will also run on Win2K3 as soon as we finish making the Win2K3
  install. :-)
 
  Laura
 
   -Original Message-
   From: [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-05 Thread Harvey Kamangwitz

On 12/5/06, Laura A. Robinson [EMAIL PROTECTED] wrote:


 Inline...

 --
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Harvey Kamangwitz
*Sent:* Tuesday, December 05, 2006 11:28 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* Re: [ActiveDir] OT: Vista Activation and KMS


 If you have any kind of a complex environment, you'll find volume
activation to be very frustrating indeed:

1. The KMS service can't support more than one key, so if you have
Longhorn VL clients in your environment you have to put up a second KMS
infrastructure for them.

Actually, when you purchase a KMS key, you get to activate TWO KMS hosts
with that key, up to ten times each. Therefore, you don't have to put up a
second KMS infrastructure.

From a subsequent post on this thread:

Doh! Okay, now I think I get what you're referencing in item 1.
There's a reason for that- LH isn't out yet. When LH is out, that won't be
an issue. :-)

My hope was that KMS could support more than one key. I was astonished when
I discovered it didn't. If you were Vista, KMS would supply you with a Vista
key. Longhorn, a Longhorn key. Since KMS only supports one key, it triggers
the need for two separate KMS infrastructures and the problems in #2
below.  I'm
assuming that Microsoft will be using Volume Activation for other products
in the future; are we to put up a separate KMS for each?





2. You can't (rather, shouldn't) use autodiscovery If you do have both LH
and Vista.  The KMS client can't distinguish between a KMS with LH and a KMS
with Vista, and there's nothing in the client that says oh, I hit a KMS but
it has the wrong key so try again immediately so ~50% of a client's
activation attempts will fail.

So remove the DNS records for the LH KMS, or am I misunderstanding your
point?

To be more specific: In a Vista / Longhorn environment, you should only

use autodiscovery for one KMS infrastructure because of 50% failure rate
above. The other systems (Longhorn, if you choose autodiscovery for Vista)
must be explictly pointed to a KMS with slmgr. How much of an adminstrative
headache this is depends on how great a penetration of a standard build is
in your company; you can code it into the build.






3.  Autodiscovery isn't practical if you have more than a few forests that
don't trust the forest your KMS is in. All admins of the untrusted forests
must manually register the _vlmcs record in their forest to find the KMS.


slmgr.vbs. We're not talking about a ton of records here or a difficult
population mechanism.

It's the logistics and overhead that's a pain. No, the act of registering

a _vlmcs record in a domain is not in itself a difficult task; it's the help
desk scripts and calls from panicky system administrators when all the
clients in their forest start complaining about failure to activate and
reduced functionality mode that have to be handled. In a large enterprise
we could see a lot of these (everyone that brings up a sandbox forest for
application testing, for example). I'm attempting to design a solution that
minimizes the impact for everybody - corporate forest administrators, Vista
users, help desk, untrusted test forest administrators, etc.






...the list goes on. (I haven't even mentioned the practical aspects of
volume activation in a lab or firewalled environment.)

I'd be happy to discuss your options around them if you should decide to
elaborate further.



If the firewalled labs don't want to open port 1688 to find a KMS, they
either have to bring up their own KMS or use MAKs. I for one don't want to
hand out KMS / volume keys to *anyone *outside the corporate KMS
infrastructure. And MAKs, though I haven't studied them as closely, are a
pain for labs that rebuild their clients because they're a single-use item
(by which I mean that if you use up one activation count on a MAK then
rebuild, it increments the MAK count - you can't reuse the previous one).
And they still require some kind of internet access, or by proxy, or by
phone, to activate them.





 It's not a fully-baked solution.

I would tend to disagree. From a technical standpoint, I think it's pretty
well-baked. From a business process standpoint, it's still coming up to
speed.

Depending on your environment, it might be easier to scrap the whole
autodiscovery, create a DNS CNAME with a couple of KMS behind it, stuff the
FQDN in the KMS client's registry if you have a standard build, and
fugeddaboutit :-).

I'm not really understanding your concerns about autodiscovery. Could you
be more specific about your environment?



- Autodiscovery is no problem for Vista clients in the corporate (account)
forest; that's where the KMS service is.
- Not much more problem for clients in major (top tier) trusted forests.
- Begins to be overhead for corp forest admins when you start adding 2nd and
3rd tier trusted forests into the KMS autodiscovery registry key (who can
really keep track of what's active and what's died

Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Nope, I've done it web based.  At the present time there are two kinds 
of keycodes up on MVLS.. one that wants a KMS, the other that will phone 
home to Redmond automatically.


Have your MVLS folks request the other type of key is my understanding 
how this will work for now.  The KMS type won't be out until Longhorn.


KMS activations will have to phone home to your servers twice a year.

Brian Cline wrote:


I was testing out the RTM of Vista Enterprise last night and noticed I 
didn't have to enter a key at any point during the install. When 
Windows tried to activate, it told me there was a DNS error, so I 
suspected it looks for a local activation server by default. Sure 
enough, in the DNS cache was a lookup for a nonexistent 
_vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
has not released KMS yet, and I couldn't find any option to activate 
directly with Microsoft. For the moment, is telephone activation the 
only option?


Brian Cline, Applications Developer
Department of Information Technology
GP Trucking Company, Inc.
803.936.8595 Direct Line
800.922.1147 Toll-Free (x8595)
803.739.1176 Fax



--
Letting your vendors set your risk analysis these days?  
http://www.threatcode.com


If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will 
hunt you down...
http://blogs.technet.com/sbs

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Brian Desmond
On the VL site there are different MAK and KMS keys...which did you use

 

Thanks,

Brian Desmond

[EMAIL PROTECTED]

 

c - 312.731.3132

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Cline
Sent: Monday, December 04, 2006 12:45 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Vista Activation and KMS

 

I was testing out the RTM of Vista Enterprise last night and noticed I
didn't have to enter a key at any point during the install. When Windows
tried to activate, it told me there was a DNS error, so I suspected it
looks for a local activation server by default. Sure enough, in the DNS
cache was a lookup for a nonexistent _vlmcs._tcp.domain.com. Upon
further research, it appears Microsoft has not released KMS yet, and I
couldn't find any option to activate directly with Microsoft. For the
moment, is telephone activation the only option?

Brian Cline, Applications Developer 
Department of Information Technology 
GP Trucking Company, Inc. 
803.936.8595 Direct Line 
800.922.1147 Toll-Free (x8595) 
803.739.1176 Fax 



RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Tim Vander Kooi
You need to go to Control Panel  System then at the bottom select
Change Product Key. This will allow you to enter your VL key which will
result in Vista activating via the web. Definitely not well documented
unfortunately.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Cline
Sent: Monday, December 04, 2006 11:45 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Vista Activation and KMS

 

I was testing out the RTM of Vista Enterprise last night and noticed I
didn't have to enter a key at any point during the install. When Windows
tried to activate, it told me there was a DNS error, so I suspected it
looks for a local activation server by default. Sure enough, in the DNS
cache was a lookup for a nonexistent _vlmcs._tcp.domain.com. Upon
further research, it appears Microsoft has not released KMS yet, and I
couldn't find any option to activate directly with Microsoft. For the
moment, is telephone activation the only option?

Brian Cline, Applications Developer 
Department of Information Technology 
GP Trucking Company, Inc. 
803.936.8595 Direct Line 
800.922.1147 Toll-Free (x8595) 
803.739.1176 Fax 



Re: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
But the MVLS admin has to request the MAK keys... on mine the KMS were 
default and I had to request MAK (like Brian said)


Tim Vander Kooi wrote:


You need to go to Control Panel  System then at the bottom select 
Change Product Key. This will allow you to enter your VL key which 
will result in Vista activating via the web. Definitely not well 
documented unfortunately.


 

*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Brian Cline

*Sent:* Monday, December 04, 2006 11:45 AM
*To:* ActiveDir@mail.activedir.org
*Subject:* [ActiveDir] OT: Vista Activation and KMS

 

I was testing out the RTM of Vista Enterprise last night and noticed I 
didn't have to enter a key at any point during the install. When 
Windows tried to activate, it told me there was a DNS error, so I 
suspected it looks for a local activation server by default. Sure 
enough, in the DNS cache was a lookup for a nonexistent 
_vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
has not released KMS yet, and I couldn't find any option to activate 
directly with Microsoft. For the moment, is telephone activation the 
only option?


Brian Cline, Applications Developer
Department of Information Technology
GP Trucking Company, Inc.
803.936.8595 Direct Line
800.922.1147 Toll-Free (x8595)
803.739.1176 Fax



--
Letting your vendors set your risk analysis these days?  
http://www.threatcode.com


If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will 
hunt you down...
http://blogs.technet.com/sbs

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Laura A. Robinson
Actually, it is clearly documented, along with a lot more information on
KMS, MAK and Vista Volume Activation (btw, Volume Licensing doesn't exist in
Vista; VL and VA are not the same things). You probably don't want to get me
started on a big long explanation of how volume activation works, so I'll
just point you to this site:
HYPERLINK
http://www.microsoft.com/technet/windowsvista/plan/volact.mspxhttp://www.m
icrosoft.com/technet/windowsvista/plan/volact.mspx
:-)
 
I highly recommend both the FAQ and the step-by-step guide. The latter
provides information on how to change from KMS to MAK and vice versa (there
are several ways), as well as documentation of defaults, configuration
options, etc.
 
Laura
 
 


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim Vander Kooi
Sent: Monday, December 04, 2006 2:44 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Vista Activation and KMS



You need to go to Control Panel  System then at the bottom select Change
Product Key. This will allow you to enter your VL key which will result in
Vista activating via the web. Definitely not well documented unfortunately.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Cline
Sent: Monday, December 04, 2006 11:45 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Vista Activation and KMS

 

I was testing out the RTM of Vista Enterprise last night and noticed I
didn't have to enter a key at any point during the install. When Windows
tried to activate, it told me there was a DNS error, so I suspected it looks
for a local activation server by default. Sure enough, in the DNS cache was
a lookup for a nonexistent _vlmcs._tcp.domain.com. Upon further research, it
appears Microsoft has not released KMS yet, and I couldn't find any option
to activate directly with Microsoft. For the moment, is telephone activation
the only option?

Brian Cline, Applications Developer 
Department of Information Technology 
GP Trucking Company, Inc. 
803.936.8595 Direct Line 
800.922.1147 Toll-Free (x8595) 
803.739.1176 Fax 


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM
 


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Laura A. Robinson
HYPERLINK
http://www.microsoft.com/technet/windowsvista/plan/volact1.mspx#StepsforImp
lementingConfigDeployingKMShttp://www.microsoft.com/technet/windowsvista/pl
an/volact1.mspx#StepsforImplementingConfigDeployingKMS
 
See the section entitled, To install KMS hosts for KMS activation
 
The short answer is, slmgr.vbs is about to become your new best friend. :-)
 
BTW, there's also information there on configuring the SRV records for the
KMS host so you won't get that error again.
 
Laura


   _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Cline
Sent: Monday, December 04, 2006 12:45 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Vista Activation and KMS



I was testing out the RTM of Vista Enterprise last night and noticed I
didn't have to enter a key at any point during the install. When Windows
tried to activate, it told me there was a DNS error, so I suspected it looks
for a local activation server by default. Sure enough, in the DNS cache was
a lookup for a nonexistent _vlmcs._tcp.domain.com. Upon further research, it
appears Microsoft has not released KMS yet, and I couldn't find any option
to activate directly with Microsoft. For the moment, is telephone activation
the only option?

Brian Cline, Applications Developer 
Department of Information Technology 
GP Trucking Company, Inc. 
803.936.8595 Direct Line 
800.922.1147 Toll-Free (x8595) 
803.739.1176 Fax 


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM
 


RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Michael A. Barker
Required reading for those with Volume Agreements.

 

http://www.microsoft.com/technet/windowsvista/plan/volact.mspx

 

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Cline
Sent: Monday, December 04, 2006 12:45 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Vista Activation and KMS

 

I was testing out the RTM of Vista Enterprise last night and noticed I
didn't have to enter a key at any point during the install. When Windows
tried to activate, it told me there was a DNS error, so I suspected it
looks for a local activation server by default. Sure enough, in the DNS
cache was a lookup for a nonexistent _vlmcs._tcp.domain.com. Upon
further research, it appears Microsoft has not released KMS yet, and I
couldn't find any option to activate directly with Microsoft. For the
moment, is telephone activation the only option?

Brian Cline, Applications Developer 
Department of Information Technology 
GP Trucking Company, Inc. 
803.936.8595 Direct Line 
800.922.1147 Toll-Free (x8595) 
803.739.1176 Fax 



RE: [ActiveDir] OT: Vista Activation and KMS

2006-12-04 Thread Laura A. Robinson
KMS runs on Vista (now), will run on Longhorn when Longhorn is released, and
will also run on Win2K3 as soon as we finish making the Win2K3 install. :-) 

Laura

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
 Sent: Monday, December 04, 2006 1:12 PM
 To: ActiveDir@mail.activedir.org
 Subject: Re: [ActiveDir] OT: Vista Activation and KMS
 
 Nope, I've done it web based.  At the present time there are 
 two kinds of keycodes up on MVLS.. one that wants a KMS, the 
 other that will phone home to Redmond automatically.
 
 Have your MVLS folks request the other type of key is my 
 understanding how this will work for now.  The KMS type won't 
 be out until Longhorn.
 
 KMS activations will have to phone home to your servers twice a year.
 
 Brian Cline wrote:
 
  I was testing out the RTM of Vista Enterprise last night 
 and noticed I 
  didn't have to enter a key at any point during the install. When 
  Windows tried to activate, it told me there was a DNS error, so I 
  suspected it looks for a local activation server by default. Sure 
  enough, in the DNS cache was a lookup for a nonexistent 
  _vlmcs._tcp.domain.com. Upon further research, it appears Microsoft 
  has not released KMS yet, and I couldn't find any option to 
 activate 
  directly with Microsoft. For the moment, is telephone 
 activation the 
  only option?
 
  Brian Cline, Applications Developer
  Department of Information Technology
  GP Trucking Company, Inc.
  803.936.8595 Direct Line
  800.922.1147 Toll-Free (x8595)
  803.739.1176 Fax
 
 
 --
 Letting your vendors set your risk analysis these days?  
 http://www.threatcode.com
 
 If you are a SBSer and you don't subscribe to the SBS Blog... 
 man ... I will hunt you down...
 http://blogs.technet.com/sbs
 
 List info   : http://www.activedir.org/List.aspx
 List FAQ: http://www.activedir.org/ListFAQ.aspx
 List archive: 
 http://www.mail-archive.com/activedir@mail.activedir.org/
 
 --
 No virus found in this incoming message.
 Checked by AVG Free Edition.
 Version: 7.5.430 / Virus Database: 268.15.6/567 - Release 
 Date: 12/4/2006 7:18 AM
  
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.15.6/567 - Release Date: 12/4/2006
7:18 AM
 

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/