B
Brian Daglish
Hi guys,
I'm currently working with a small test environment featuring a 2003
(standard) pdc and several 2003 (std/ent) & 2000 (std/adv) member servers.
I've got windows 2003 licence server installed on the pdc.
After activating the licence server (and rebooting the box), I ran a small
test wherein I rdp'd from one win2k box to another win2k box. Note at this
stage I have not installed any tscals on the license server.
What I expected to see is the 2003 ts licence server issue an existing
windows 2000 (built-in) cal for this win2k to win2k transaction.
But what it infact issued was a temporary existing windows 2000 cal!! I've
repeated this test a number of times with the same result.
So my question is have I some how managed to set up my licence server
incorrectly?? In a similar setup a number of weeks ago I saw the 2003
licence server issue existing built-in licences for win2k to win2k
connections. Any ideas what I may have wrong with my current setup??
Many thanks for ur replies.
I'm currently working with a small test environment featuring a 2003
(standard) pdc and several 2003 (std/ent) & 2000 (std/adv) member servers.
I've got windows 2003 licence server installed on the pdc.
After activating the licence server (and rebooting the box), I ran a small
test wherein I rdp'd from one win2k box to another win2k box. Note at this
stage I have not installed any tscals on the license server.
What I expected to see is the 2003 ts licence server issue an existing
windows 2000 (built-in) cal for this win2k to win2k transaction.
But what it infact issued was a temporary existing windows 2000 cal!! I've
repeated this test a number of times with the same result.
So my question is have I some how managed to set up my licence server
incorrectly?? In a similar setup a number of weeks ago I saw the 2003
licence server issue existing built-in licences for win2k to win2k
connections. Any ideas what I may have wrong with my current setup??
Many thanks for ur replies.