Re: Terminal Services locked!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Chris (Chris_at_discussions.microsoft.com)
Date: 01/08/05 

Date: Sat, 8 Jan 2005 09:09:03 -0800

they were clear on the "do not use on a production server".
So my choices would be if this wasn't a development server, 1.) go without
terminal server.
Interesting.

"Lanwench [MVP - Exchange]" wrote:

> Chris wrote:
> > without being too negative;
> > I did call and after 100 options I got through. Then I got the
> > disclaimer that if I try this hotfix it's by my own choice. That it
> > has not been fully tested and the results could be undesirable. To
> > back-up your server and to NOT useon a production server.
>
> I've never heard anyone at MS tell me not to use something on a production
> server outright. The "use at your own risk" is a standard disclaimer. And
> you should back up your server first.
>
> >
> > The article was written October 15, 2004 and terminal server is
> > important. Why can't MS give me more comfort? All I want to do is gt
> > back my Terminal Server use on MS's flagship Server OS.
>
> If the hotfix really does address your specific symptoms, try it. I imagine
> you can uninstall it if it causes problems - but this does vary.
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> Chris wrote:
> >>> I've been using TS on a Win2003 Standard server and now it is
> >>> locked? I get the message:
> >>> "Terminal server has ended the connection"
> >>> I looked up in the knowledge base and found an article:
> >>> http://support.microsoft.com/default.aspx?scid=kb;en-us;828662
> >>> but to my surprise, and I've not been frustrated like this one, the
> >>> article does not allow download of the patch/fix. There is a link
> >>> that that bounces you around to unuseful pages to no end!
> >>> Can someone at MS fix this article and make the patch available this
> >>> is VERY frustrating. I can not use my terminal service on this
> >>> server! I need a fix ASAP.
> >>
> >> As the article clearly states, you have to contact Microsoft to get
> >> the hotfix. This is true for most hotfixes.
> >>
> >> Call them. They should not charge you for the call if you mention
> >> the KB article number and say you just need a hotfix - they will
> >> email it to you with a password.
>
>
>

Relevant Pages

  • Re: Terminalserver shutting down
    ... vanished as soon as I applied the 907242 hotfix. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... SQL troubleshooting: http://sql.veranoest.net ... Next we will go through the "Windows Server 2003 Troubleshooting ...
    (microsoft.public.windows.terminal_services)
  • Re: terminal server that hands out licenese to other servers..
    ... I've worked in a lot of place but have never had a reason to allow 10 admins on one server at time. ... Microsoft MVP - Terminal Server ... Does that mean you have to install all terminal services in "application mode" on all servers that will need more than two connections? ... To provide licenses for the user connections, install the Terminal Server Licensing component on a domain controller and use the Terminal Server Licensing administration tool to activate your licenses. ...
    (microsoft.public.windows.terminal_services)
  • Re: cant connect to TS after install sp1 on SBS
    ... Deploying Windows Server 2003 Terminal Server to Host User Desktops ... Microsoft ISA Server 2004 Documentation ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server with SBS 2K3
    ... All of these problems only occur on the Terminal Server, there are others, ... > Microsoft CSS Online Newsgroup Support ... > |> policy and the local policy of the terminal server. ...
    (microsoft.public.windows.server.sbs)
  • RE: terminal server licensing issue.
    ... First, Cris is correct, we recommend to install the terminal server ... the SBS domain is different from the standard windows ... | did this the server started telling me I have a license issue. ...
    (microsoft.public.windows.server.sbs)