Inline...
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harvey Kamangwitz Sent: Tuesday, December 05, 2006 11:28 AM To: [email protected] 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:[email protected]"; [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 > > G&P 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/[email protected]/"; \nhttp://www.mail-archive.com/[email protected]/ > > -- > 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://www.activedir.org/ListFAQ.aspx List archive: HYPERLINK "http://www.mail-archive.com/[email protected]/"; \nhttp://www.mail-archive.com/[email protected]/ -- S. -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.15.9/571 - Release Date: 12/5/2006 11:50 AM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.15.9/571 - Release Date: 12/5/2006 11:50 AM
