Remote Desktop to Terminal Services

Archived from groups: microsoft.public.windows.terminal_services,microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.setup (More info?)

I just made what appears to be a big mistake.
I have a remotely located Win 2003 server I had been administering with
Remote Desktop.
I just added Terminal Services functionality to the server and when it
re-booted, I couldn't get in any longer with Remote Desktop,
as attempting to connect with Remote Desktop fails with 'Session
disconnected because there are no terminal server license servers available
to provide a license', which is in fact true.
However, the MS's documentation states that Remote Desktop will still work,
and that there is a 120 day grace period for terminal connections until the
client licenses are required.
So, is there a way to access the server without removing Terminal Services
from the server functionality?


Thanks,
Phil

--
Phillip N Rounds
The Cassandra Group, Inc
68 Sand Hill Rd
Flemington NJ 08822
prounds@cassandragroup.com

Archived from groups: microsoft.public.windows.terminal_services,microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.setup (More info?)

Sorry; I mis-spoke. Please see the following extract (particularly the
second paragraph) from the document I referenced in my earlier post.

Terminal Server Grace Period
A terminal server allows clients to connect without license tokens for 120
days before it requires communicating with a license server. This period is
known as the license server grace period, and begins the first time a
terminal server client connection is made to the terminal server. This grace
period is designed to allow ample time for the administrator to deploy a
license server. It is not designed to provide for a period of “free” access
to a terminal server. Per the Windows Server 2003 EULA, licenses are
required to be purchased in order to access a terminal server. There is no
provision in the EULA for accessing a terminal server without the
appropriate licenses.

The license server grace period ends after 120 days, or when a license
server issues a permanent license token through the terminal server,
whichever occurs first. Therefore, if the license server and terminal server
are deployed at the same time, the terminal server grace period will
immediately expire after the first permanent license token has been issued.


--
Bruce Sanderson MVP

It's perfectly useless to know the right answer to the wrong question.


"Bruce Sanderson" <Bruce.Sanderson@junk.junk> wrote in message
newsQrPXmMpEHA.1712@tk2msftngp13.phx.gbl...
> Even though there is a "Grace Period", Terminal Services needs to be able
> to communicate with a TS License Server, even if there are no CAL tokens
> on it.
>
> Install the Windows 2003 Terminal Services License Server on the same or
> different Windows 2003 server, then Activate the License Server.
>
> Unlike Windows 2000, Windows 2003 Terminal Services License Server does
> not have to be on a Domain Controller.
>
> See
> http://www.microsoft.com/windowsse [...] rvlic.mspx
> for more information, including how to tell your Terminal Server(s) which
> server the TS License Server is on.
>
> --
> Bruce Sanderson MVP
>
> It's perfectly useless to know the right answer to the wrong question.
>
>
> "Phillip N Rounds" <prounds@cassandragroup.com> wrote in message
> news:uD679WMpEHA.3392@TK2MSFTNGP15.phx.gbl...
>>I just made what appears to be a big mistake.
>> I have a remotely located Win 2003 server I had been administering with
>> Remote Desktop.
>> I just added Terminal Services functionality to the server and when it
>> re-booted, I couldn't get in any longer with Remote Desktop,
>> as attempting to connect with Remote Desktop fails with 'Session
>> disconnected because there are no terminal server license servers
>> available
>> to provide a license', which is in fact true.
>> However, the MS's documentation states that Remote Desktop will still
>> work,
>> and that there is a 120 day grace period for terminal connections until
>> the
>> client licenses are required.
>> So, is there a way to access the server without removing Terminal
>> Services
>> from the server functionality?
>>
>>
>> Thanks,
>> Phil
>>
>> --
>> Phillip N Rounds
>> The Cassandra Group, Inc
>> 68 Sand Hill Rd
>> Flemington NJ 08822
>> prounds@cassandragroup.com
>>
>>
>
>

Archived from groups: microsoft.public.windows.terminal_services,microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.setup (More info?)

This may help as a temp measure to reconnect to the server. As always if you
are playing with the registry "BACK IT UP FIRST". This may not be strictly
in Line with the licensing policy but may help you get back in to reset.

"you could try the following to clear the existing license on the affected
PC:

Start Registry Editor (Regedit.exe).
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\MSLicensing

Delete the whole MSLicensing key from the registry.
Quit Registry Editor.
Connect to the Terminal Services server"



Kenny




"Bruce Sanderson" <Bruce.Sanderson@junk.junk> wrote in message
newsQrPXmMpEHA.1712@tk2msftngp13.phx.gbl...
> Even though there is a "Grace Period", Terminal Services needs to be able
to
> communicate with a TS License Server, even if there are no CAL tokens on
it.
>
> Install the Windows 2003 Terminal Services License Server on the same or
> different Windows 2003 server, then Activate the License Server.
>
> Unlike Windows 2000, Windows 2003 Terminal Services License Server does
not
> have to be on a Domain Controller.
>
> See
>
http://www.microsoft.com/windowsse [...] rvlic.mspx
> for more information, including how to tell your Terminal Server(s) which
> server the TS License Server is on.
>
> --
> Bruce Sanderson MVP
>
> It's perfectly useless to know the right answer to the wrong question.
>
>
> "Phillip N Rounds" <prounds@cassandragroup.com> wrote in message
> news:uD679WMpEHA.3392@TK2MSFTNGP15.phx.gbl...
> >I just made what appears to be a big mistake.
> > I have a remotely located Win 2003 server I had been administering with
> > Remote Desktop.
> > I just added Terminal Services functionality to the server and when it
> > re-booted, I couldn't get in any longer with Remote Desktop,
> > as attempting to connect with Remote Desktop fails with 'Session
> > disconnected because there are no terminal server license servers
> > available
> > to provide a license', which is in fact true.
> > However, the MS's documentation states that Remote Desktop will still
> > work,
> > and that there is a 120 day grace period for terminal connections until
> > the
> > client licenses are required.
> > So, is there a way to access the server without removing Terminal
Services
> > from the server functionality?
> >
> >
> > Thanks,
> > Phil
> >
> > --
> > Phillip N Rounds
> > The Cassandra Group, Inc
> > 68 Sand Hill Rd
> > Flemington NJ 08822
> > prounds@cassandragroup.com
> >
> >
>
>

Archived from groups: microsoft.public.windows.terminal_services,microsoft.public.windowsnt.terminalserver.client,microsoft.public.windowsnt.terminalserver.setup (More info?)

No, I never installed terminal server, I always just used remote desktop.
Anyway, I de-installed it, and will go through the whole process again if
needs be.

Thanks,
Phil
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9571E6B68A856veranoesthemutforsse@207.46.248.16...
> There have been a couple of reports here lately, about grace
> periods ending unexpectedly.
> In most cases, it turned out that full-blown Terminal Services was
> installed during the first OS installation, and uninstalled after
> a couple of connections, since at that time Remote Desktop was the
> only functionality needed.
>
> This triggers the start of the grace period. If full-blown TS is
> then later installed again, the grace period has already ended.
> Could this be the explanation in your case?
>
> The only solution that I can see is to either uninstall TS or
> install a TS Licensing Server.
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "Phillip N Rounds" <prounds@cassandragroup.com> wrote on 27 sep
> 2004 in microsoft.public.windows.terminal_services:
>
> > I just made what appears to be a big mistake.
> > I have a remotely located Win 2003 server I had been
> > administering with Remote Desktop.
> > I just added Terminal Services functionality to the server and
> > when it re-booted, I couldn't get in any longer with Remote
> > Desktop, as attempting to connect with Remote Desktop fails with
> > 'Session disconnected because there are no terminal server
> > license servers available to provide a license', which is in
> > fact true. However, the MS's documentation states that Remote
> > Desktop will still work, and that there is a 120 day grace
> > period for terminal connections until the client licenses are
> > required. So, is there a way to access the server without
> > removing Terminal Services from the server functionality?
> >
> >
> > Thanks,
> > Phil