G
Guest
Hello,
I use a french Win2kTS+SP3 server with 20 cient CALS. He also serves as the Lic Server.
An expiration date appears in front of each licence. Exactly the day of the expiration, the terminal who got the licence cannot connect ("the terminal server cannot issue a licence" is approximatively the message that appears in the event log).
But, the next day, it can !!! and his "emission" date (i mean, the date the license ahs been given to the terminal) is the current date. The new expiration date is around 60 days later.
So, will i always have to suffer this "no work" day, or should there be a solution ? (Perhaps by de-installing the Lic Server, reinstalling it, activate it, call the Clearing House, ... and hope it changes something .).
Thanks for any idea.
I use a french Win2kTS+SP3 server with 20 cient CALS. He also serves as the Lic Server.
An expiration date appears in front of each licence. Exactly the day of the expiration, the terminal who got the licence cannot connect ("the terminal server cannot issue a licence" is approximatively the message that appears in the event log).
But, the next day, it can !!! and his "emission" date (i mean, the date the license ahs been given to the terminal) is the current date. The new expiration date is around 60 days later.
So, will i always have to suffer this "no work" day, or should there be a solution ? (Perhaps by de-installing the Lic Server, reinstalling it, activate it, call the Clearing House, ... and hope it changes something .).
Thanks for any idea.