Re: Article KB834651 TS Licensing mode changes
- From: "TP" <tperson.knowspamn@xxxxxxxxxxxxxxx>
- Date: Tue, 19 Apr 2005 09:42:22 -0400
I have used the hotfix on many different servers without problems
ever since it was released. This doesn't mean you are safe to use it,
so test it first in your environment.
The "tested service pack" version is out, it is included in Win 2003
SP1. Of course you should test this before deploying it as well.
If you don't use either of the above options, you can create a
shutdown script that will reset the registry key to 4. Also you can
reset things manually by changing the licensing mode back and forth
after you make a change in add/remove programs. For example,
you change something in add/remove, go to tscc.msc, the mode
says it is "Per User", change it to "Per Device", click Ok, then change
it to "Per User", and click Ok again.
Thanks.
-TP
wincom wrote:
> I have a situation where magically my previously permanent TS
> licenses have become temporary. I came across KB Article 834651. I
> took a look at the registry of the TS machine and bingo, PolicyAcOn
> key was set to zero. I called MS and I have been sent a link to
> download the hotfix. This fix is not tested however and I do not
> want to corrupt my TS. If I simply go into the registry and change
> the value from zero to 4 ( for per user), would that solve the
> problem as long as I realize that future add/remove program stuff
> might bring it back? Then I could wait for the tested service pack.
.
- References:
- Article KB834651 TS Licensing mode changes
- From: wincom
- Article KB834651 TS Licensing mode changes
- Prev by Date: Window 2003 Terminal Services or Just Windows 2003 Server
- Next by Date: RE: Scheduled Terminal Server reboot.
- Previous by thread: Re: Article KB834651 TS Licensing mode changes
- Next by thread: I can't see the client printer.
- Index(es):
Relevant Pages
|
