Re: Terminal Services locked!
From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 01/08/05
- Next message: Stuart Mackie [MCP, MSP]: "Generate/Export PKCS #12 certificate from Win2k3 CA"
- Previous message: Steven L Umbach: "Re: Changing Global Group to Domain Local Group."
- In reply to: Chris: "Re: Terminal Services locked!"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 8 Jan 2005 13:14:39 -0500
Chris wrote:
> they were clear on the "do not use on a production server".
I can't remember whether I've heard that exact phrase or not, actually. For
what it's worth, I have never had a hotfix sent to me this way blow up a
machine, but that's no guarantee, of course.
> So my choices would be if this wasn't a development server, 1.) go
> without terminal server.
> Interesting.
It's your choice to try it or not. Are you saying that this *is not* a
production server? If that's true, what do you have to lose? And if it is a
production server, do you have any spare hardware you can use to set up a
test box?
Does this server have any other roles on your network? (I'd hope not). Since
you're having major problems with your existing TS, I can't think that
applying the hotfix could really put you in a worse situation than you're in
now.Do a backup first. Maybe even a full ghost/acronis/etc image.
>
> "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.
- Next message: Stuart Mackie [MCP, MSP]: "Generate/Export PKCS #12 certificate from Win2k3 CA"
- Previous message: Steven L Umbach: "Re: Changing Global Group to Domain Local Group."
- In reply to: Chris: "Re: Terminal Services locked!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
