Archived from groups: microsoft.public.windowsnt.terminalserver.client (
More info?)
OK, I've re-read the
Windows Server 2003 Terminal Server Licensing White paper
http://www.microsoft.com/windowsserver2003/techinfo/overview/termse
rvlic.mspx
and there are some changes from what I previously wrote (sorry for
that!):
The licensing program for License Paks is now called "Retail" in
stead of "Other", and it needs a 25-digit license code:
<quote>
If you purchase your TS CALs by means of a Microsoft License Pak,
note that Microsoft added some additional components to the MLP for
TS CALs, starting with Windows 2000. Previously, the contents of a
MLP included EULAs. The Windows Server 2003 TS CAL MLP, like the
Windows 2000 Server TS CAL MLP, will include the EULAs as well as a
new component called a license addendum. This license addendum
contains a 25-character alphanumeric code, called a license code,
which represents the quantity of TS CALs purchased. The system
administrator uses this license code and chooses a licensing
program called Retail to install the MLP TS CAL tokens on the
license server.
</quote>
To cover all options, I would call the vendor who sold you the
licenses, but I doubt that they can help.
If so, I would call the normal Microsoft support. You wrote that
the error message states: "The licensing agreement data provided to
Microsoft is not valid", which seems to imply that the Licensing
wizard is treating your attempt to install TS CALs as if you choose
the "Open" or "Select" licensing program, and not "Retail". If
that's the case, something is wrong in the Licensing Services.
One other possibility is to completely uninstall the TS Licensing
service, rename the %windir%\System32\Lserver folder, delete the
MSLicensing subkey, reboot, and install it again.
Documented here:
839878 - You cannot install the Terminal Services CAL pack on a
Windows 2000 server-based computer
http://support.microsoft.com/?kbid=839878
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?bXBpcHBpbg==?=" <mpippin@discussions.microsoft.com>
wrote on 19 jul 2005 in
microsoft.public.windowsnt.terminalserver.client:
> Hey Vera,
>
> I have tried all the licensing options, none have accepted my
> numbers. Also I called the phone number under listed to do it
> verbally. They said they do not do the oem licensing. This was
> kinda my last straw.
>
> Some one must be doing this,
>
> Any other thoughts?
>
> "Vera Noest [MVP]" wrote:
>
>> And you're sure you have choosen the "Other" licensing program?
>> Because that should ask you for a 14-digit license pack number.
>>
>> I would follow the wizards advice and use the telephone method,
>> i.e phone the Clearinghouse.
>> I'm sure that they can guide you through the process.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting:
http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> "=?Utf-8?B?bXBpcHBpbg==?=" <mpippin@discussions.microsoft.com>
>> wrote on 19 jul 2005:
>>
>> > Hey Vera
>> > I am trying to do what you said but I keep getting this as an
>> > error, "The licensing agreement data provided to Microsoft is
>> > not valid. Check all the information you provided, make any
>> > necessary corrections, and then resubmit your request. If
>> > the problem persists, try using a different connection
>> > method."
>> >
>> > The sample box below where the numbers go shows the use of
>> > only seven digits, but the number on this license card has
>> > fourteen numbers. I have tried all of them, some of them,
>> > and with dashes in between.
>> >
>> > The internet connectivity is good, so I do noy think that is
>> > the case. But I am remotely administrating the server, would
>> > it make a diffrence if I try to activate these licenses
>> > local?
>> >
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> You have to choose the correct Licensing Program in the Add
>> >> licenses Wizard. For licenses bought under an Open Volume
>> >> licenses, you choose "Microsoft Open license program". For
>> >> OEM licenses, you choose "Other".
>> >>
>> >> Article is about W2K, but the principles are the same on
>> >> 2003:
>> >>
>> >> 237811 - How to Activate a Terminal Services License Server
>> >> and Install CALs Over the Internet
>> >>
http://support.microsoft.com/?kbid=237811
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting:
http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> "=?Utf-8?B?bXBpcHBpbg==?="
>> >> <mpippin@discussions.microsoft.com> wrote on 18 jul 2005 in
>> >> microsoft.public.windowsnt.terminalserver.client:
>> >>
>> >> > I am unable to figure out how to install OEM TS
>> >> > Cal’s I received from my distributor a
>> >> > Microsoft envelop with a card in it. The card was for 5
>> >> > TS Device Client Access License for Windows Server 2003
>> >> > OEM. The card has a Tracking ID: with 14 numbers. Can
>> >> > anyone please tell me what I need to do to add these to
>> >> > the server?
>> >> >
>> >> > I have used the open license arangement for per user with
>> >> > 5 sets of 5 alpha newmeric with no issues. But this has me
>> >> > stumped. Thanks
Facebook
Twitter
Instagram