[THIN] Re: Terminal Server Licensing error 1009
- From: "Medeiros, Jim" <jdmedeiros@xxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 09:30:37 -0500
Wow. I don't even have the PolicyAcOn Setting in my registry. I'm using
win2k3 sp1.
Jim Medeiros
Network Manager
RC2 Brands Inc.
_____
From: Toby [mailto:toby.percival@xxxxxxxxx]
Sent: Thursday, January 04, 2007 9:21 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Terminal Server Licensing error 1009
Hmm, it's actually neither. The current setting is 0.
On 1/4/07, Matthew Shrewsbury <MShrewsbury@xxxxxxxxxxxxxxx
<mailto:MShrewsbury@xxxxxxxxxxxxxxx> > wrote:
Is the PolicyAcOn populated with a value of 2 or 4?
Matthew Shrewsbury
Network Manager
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx>
[mailto:thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On
Behalf Of Toby
Sent: Thursday, January 04, 2007 9:10 AM
To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: Terminal Server Licensing error 1009
Windows Server 2003 SP1
On 1/4/07, Matthew Shrewsbury <MShrewsbury@xxxxxxxxxxxxxxx
<mailto:MShrewsbury@xxxxxxxxxxxxxxx> > wrote:
That is helpful, what OS and service pack are you running?
Matthew Shrewsbury
Network Manager
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:
<mailto:thin-bounce@xxxxxxxxxxxxx> thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Toby
Sent: Thursday, January 04, 2007 9:02 AM
To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: Terminal Server Licensing error 1009
HI Matthew,
This key DOES exist on my TSLicensing server.
Hope this helps
Toby
On 1/4/07, Matthew Shrewsbury < <mailto:MShrewsbury@xxxxxxxxxxxxxxx>
MShrewsbury@xxxxxxxxxxxxxxx> wrote:
Yes that really does help. I did contact them and thought it was working
however I don't see my licenses showing and it is showing the wrong license
mode Per Device. I have Per User licensing.
I found article http://support.microsoft.com/?kbid=834651
<http://support.microsoft.com/?kbid=834651> that talks about TS License
server switching to a invalid mode. I checked the registry path it talks
about to confirm the mode and I found that the key "PolicyAcOn" doesn't
exist. Could someone be so kind as to let me know if it exists on their TS
license server?
Thank you,
Matthew Shrewsbury
Network Manager
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:
<mailto:thin-bounce@xxxxxxxxxxxxx> thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Medeiros, Jim
Sent: Thursday, January 04, 2007 8:39 AM
To: 'thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx> '
Subject: [THIN] Re: Terminal Server Licensing error 1009
No problem. We just went through this very similar thing when we moved our
TS Lic server from Win2k to Win2k3. We were using temp licenses until we
fixed it.
The key is to check your license certificate (if printed or you may have to
go to eopen website to find it or them). Once you have a good understanding
of what you own (per device or per user or both) THEN you should contact MS
again (sometimes this is done via Telephone and sometimes it can be done
online - your lic server should be configured one way or the other - when
you go to license it, it will show you which mode you are using). When you
contact MS they will ask for per user or per device and how many you own.
Then they will give you a code that will lic you for that particular type
and number of licenses.
Hope this helps,
Jim Medeiros
Network Manager
RC2 Brands Inc.
_____
From: Matthew Shrewsbury [mailto:MShrewsbury@xxxxxxxxxxxxxxx
<mailto:MShrewsbury@xxxxxxxxxxxxxxx> ]
Sent: Thursday, January 04, 2007 8:30 AM
To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: Terminal Server Licensing error 1009
I did call Microsoft clearing house and thought I did what you're
describing. However my Licensing looks odd to me (see screen shot).
First of all the licensing is showing Per Device CAL but I'm supposed to be
in Per User CAL. My hope is that the 20 Per Device CAL are migrated Windows
2000 licenses. However shouldn't I show the 55 Per User CALs that I own?
Sorry for the lack of understanding but I'm lost with this TS Licensing on
2003.
Matthew Shrewsbury
Network Manager
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:
<mailto:thin-bounce@xxxxxxxxxxxxx> thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Medeiros, Jim
Sent: Thursday, January 04, 2007 8:22 AM
To: 'thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx> '
Subject: [THIN] Re: Terminal Server Licensing error 1009
Did you upgrade your TS licenses for TS 2003? When you move from win2k or
winnt TS Lic server you have to upgrade the licenses with Microsoft. This
may not cost you anything, usually just a phone call or online form with
microsoft. they will give you a code to key into your lic server which will
activate 2003 licenses for TS. Then your PS4 servers should be licensed.
Jim
_____
From: Matthew Shrewsbury [mailto:MShrewsbury@xxxxxxxxxxxxxxx
<mailto:MShrewsbury@xxxxxxxxxxxxxxx> ]
Sent: Thursday, January 04, 2007 8:17 AM
To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Terminal Server Licensing error 1009
I recently installed two new PS4 servers on Windows 2003. I moved and
upgraded the Terminal Server licensing server to Windows 2003. Everything so
far is working ok except I noticed that we have been receiving an error on
each Windows 2003 PS4 server but not the TS license server. Older Windows
2000 servers are not showing an error in there event logs.
Event ID 1009
The terminal server licensing grace period is about to expire on 12/29/2006
and the service has not registered with a license server with installed
licenses. A terminal server license server is required for continuous
operation. A terminal server can operate without a license server for 120
days after initial start up.
I've done some searching on google.com <http://google.com> and found
KB885013 but this does not apply as it specifically says the error should be
on the TS License server.
Has anyone had this before? How can I confirm that my licensing will work
and not expire after 120 days?
Thank you,
Matthew Shrewsbury
Network Manager
Other related posts:
