Hi Darrell, thanks for the reply. I found my problem. I had used the VL
media but my coworker had syspreped the machine using the KMS VL in the xml
file. We changed that to the Product Key that came prepackaged in the VL and
now things are back to the way i would expect them to be. Now i just have to
figure out a way to maintain the damn 25 Client count on my KMS server....
what a pain.
thanks for your input.
""Darrell Gorter[MSFT]"" wrote:
> What was the output for -DLI?
> You can see those errors when the media is not Volume Media
> Darrell Gorter[MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights
> |>Thread-Topic: slmgr.vbs -ckms gives Unrecognized Option Error
> |>thread-index: AcdwxttxpXkg8LEXT++2N2jDpLedIw==
> |>X-WBNR-Posting-Host: 220.127.116.11
> |>From: =?Utf-8?B?c2M=?= <email@example.com>
> |>Subject: slmgr.vbs -ckms gives Unrecognized Option Error
> |>Date: Tue, 27 Mar 2007 16:22:59 -0700
> |>Lines: 15
> |>Message-ID: <1D384FB6-5418-448D-A29F-587B68891923@microsoft.com>
> |>MIME-Version: 1.0
> |>Content-Type: text/plain;
> |> charset="Utf-8"
> |>Content-Transfer-Encoding: 7bit
> |>X-Newsreader: Microsoft CDO for Windows 2000
> |>Content-Class: urn:content-classes:message
> |>Importance: normal
> |>Priority: normal
> |>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
> |>Newsgroups: microsoft.public.windows.vista.installation_setup
> |>Path: TK2MSFTNGHUB02.phx.gbl
> |>Xref: TK2MSFTNGHUB02.phx.gbl
> |>NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> |>X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
> |>OK, so i'm trying to get our Vista VL machines and KMS server up and
> |> I have not reached the 25min KMS req so last week i activated a couple
> |>our Vista VL machines against a KMS server in another domain, that worked
> |>fine. Since then the machine has been sysprepped and now i want to point
> |>our local KMS and this is what i get:
> |>slmgr.vbs -dlv gives all info EXCEPT it DOES NOT list the current KMS
> |>slmgr.vbs -ckms gives unrecognized error message
> |>slmgr.vbs -skms <our server> gives "The RPC server is unavailable"
> |>Any thoughts or suggestions on what the heck is going on here? Why can't
> |>clear the old KMS with the CKMS command? What doesn't the -dlv command
> |>the current KMS server anymore in the license detail info? What's the
> |>with the RPC errror?