I have a Vista user that is connecting to Terminal Server through RDP. We
are having licensing issues with our new 2003 Server, but are currently using
Temporary licenses. We didn't discover the problem until our 120 days were
up on many machines so I had my users delete the MSLicensing key in the
registry to reissue the license for another 120 days until I took some time
to look into the other problem.

Although my one Vista user had 60+ days left on his temp license he deleted
the key! Now it will not reissue a temporary license and will not recreate
the MSLicensing key. When he attempts to connect he gets the following
message: The remote computer disconnected the session because of an error in
the licensing protocol. Please try connecting to the remote computer
again or contact your administrator.

Can anyone help even if it is a temp solution? I am supposed to be on
maternity leave right now, but of course this user deleted the registry key
two days after I had my baby! Frustrating! :)

Thanks. ~Gretchen

Gretchen Hembree wrote:[color=blue]
> I have a Vista user that is connecting to Terminal Server through
> RDP. We are having licensing issues with our new 2003 Server, but
> are currently using Temporary licenses. We didn't discover the
> problem until our 120 days were up on many machines so I had my users
> delete the MSLicensing key in the registry to reissue the license for
> another 120 days until I took some time to look into the other
> problem.
>
> Although my one Vista user had 60+ days left on his temp license he
> deleted the key! Now it will not reissue a temporary license and
> will not recreate the MSLicensing key. When he attempts to connect
> he gets the following message: The remote computer disconnected the
> session because of an error in the licensing protocol. Please try
> connecting to the remote computer
> again or contact your administrator.
>
> Can anyone help even if it is a temp solution? I am supposed to be on
> maternity leave right now, but of course this user deleted the
> registry key two days after I had my baby! Frustrating! :)
>
> Thanks. ~Gretchen[/color]

The user could try doing a System Restore from a time before he deleted the
MSLicensing keys. That should restore the temporary licence and give him the
60 days back.

And - congratulations!

--
LSR

Thanks for the suggestion. I tried it, but the oldest system restore point
is about three days AFTER he deleted the key. Does anyone have any other
suggestions?

The computer is not that old. Should I consider rebuilding it completely?
I am cautious because I don't even know if that would fix it! His computer
is still listed in the temporary licenses on the Terminal Server. Is there
anyway to purge that?

"LSR" wrote:
[color=blue]
> Gretchen Hembree wrote:[color=green]
> > I have a Vista user that is connecting to Terminal Server through
> > RDP. We are having licensing issues with our new 2003 Server, but
> > are currently using Temporary licenses. We didn't discover the
> > problem until our 120 days were up on many machines so I had my users
> > delete the MSLicensing key in the registry to reissue the license for
> > another 120 days until I took some time to look into the other
> > problem.
> >
> > Although my one Vista user had 60+ days left on his temp license he
> > deleted the key! Now it will not reissue a temporary license and
> > will not recreate the MSLicensing key. When he attempts to connect
> > he gets the following message: The remote computer disconnected the
> > session because of an error in the licensing protocol. Please try
> > connecting to the remote computer
> > again or contact your administrator.
> >
> > Can anyone help even if it is a temp solution? I am supposed to be on
> > maternity leave right now, but of course this user deleted the
> > registry key two days after I had my baby! Frustrating! :)
> >
> > Thanks. ~Gretchen[/color]
>
> The user could try doing a System Restore from a time before he deleted the
> MSLicensing keys. That should restore the temporary licence and give him the
> 60 days back.
>
> And - congratulations!
>
> --
> LSR
>
>
>[/color]

Solution is

1. Run RDP client as Administrator on problem machines. MSlisensing key will recreate.

or (then)

2. Open regedt32.exe, navigate to [COLOR=#1f497d][B]HKLM\Software\microsoft\mslicensing\store[/B][/COLOR], then right-click on store and choose permissions. If there isn't already permissions for Users, add it. You'll need to give that group special permissions, ([COLOR=#1f497d]create-subkey , query, set value, enumerate subkeys, notify, read [/COLOR])

Problem solved! Okay this was one of the most frustrating situations. I am
currently NOT a fan of Vista and it will take me some time to get over it! :)

Everyone was telling me to just log in as the administrator and that the key
would be recreated. The only user account set up is the administrator and so
I was very frustrated because nothing seemed to work. I finally was just
messing around and right clicked on the RDP. There was an option of Run this
program as the Administrator. I clicked that and magically the key was
recereated and I was connected! Ugh! How simple but it took me three weeks
to figure out!!!!!!!

Thanks for all your help. I hope this entry helps someone else one day. :)
~Gretchen

"Tomboy99" wrote:
[color=blue]
>
> Solution is
>
> 1. Run RDP client as Administrator on problem machines. MSlisensing key
> will recreate.
>
> or (then)
>
> 2. Open regedt32.exe, navigate to
> *HKLM\Software\microsoft\mslicensing\store*, then right-click on store
> and choose permissions. If there isn't already permissions for Users,
> add it. You'll need to give that group special permissions,
> (create-subkey , query, set value, enumerate subkeys, notify, read )
>
>
> --
> Tomboy99
>[/color]

Hello every body, I've fixed the trouble doinn this:

1.- Back up all the MSLICENSING registry folder of a machine with
Windows VISTA ULTIMATE.

2.- In the machine with Windows Vista HOME delete the MSLICENSING
Folder.

3.- On the desktop Vista Home Machine Paste the Registry Entry of the
Windows Vista Ultimate that yuo've been backed-up previously.

4.-Doble Click the Registry Entry.

5.- Try to log on into the SERVER 2000. This work too for the Windows
Server 2003.

Try with my Registry Attached.


+-------------------------------------------------------------------+
|Filename: mslicense.zip |
|Download: http://forums.techarena.in/attachment.php?attachmentid=6384|
+-------------------------------------------------------------------+

--
jesuscervin
------------------------------------------------------------------------
jesuscervin's Profile: [url]http://forums.techarena.in/member.php?userid=30977[/url]
View this thread: [url]http://forums.techarena.in/showthread.php?t=756044[/url]

[url]http://forums.techarena.in[/url]

jesuscervin;3156326 Wrote:[color=blue]
> Hello every body, I've fixed the trouble doinn this:
>
> 1.- Back up all the MSLICENSING registry folder of a machine with
> Windows VISTA ULTIMATE.
>
> 2.- In the machine with Windows Vista HOME delete the MSLICENSING
> Folder.
>
> 3.- On the desktop Vista Home Machine Paste the Registry Entry of the
> Windows Vista Ultimate that yuo've been backed-up previously.
>
> 4.-Doble Click the Registry Entry.
>
> 5.- Try to log on into the SERVER 2000. This work too for the Windows
> Server 2003.
>
> Try with my Registry Attached.[/color]

It's working. TNKS


--
without_nic
------------------------------------------------------------------------
without_nic's Profile: [url]http://forums.techarena.in/members/without_nic.htm[/url]
View this thread: [url]http://forums.techarena.in/vista-help/756044.htm[/url]

[url]http://forums.techarena.in[/url]

Big tank to Gretchen Hembree I didn't found any way to solve that
problem anychere else tank again


--
GolDo
------------------------------------------------------------------------
GolDo's Profile: [url]http://forums.techarena.in/members/110845.htm[/url]
View this thread: [url]http://forums.techarena.in/vista-help/756044.htm[/url]

[url]http://forums.techarena.in[/url]