Re: Upgrade of W2K Server to Windows 2003 Terminal Server
From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: Tue, 16 Nov 2004 15:04:15 -0800
Wouldn't it have been nice if you had included this crucial
information in your first post? Would have saved me at least half
an hour looking for references to similar problems.
An inplace upgrade is something that I wouldn't consider even on a
perfectly stable system, but on a system that doesn't even
I don't understand you last question. How would a fresh install of
one server break another one?
MCSE, CCEA, Microsoft MVP - Terminal Server
--- please respond in newsgroup, NOT by private email ---
"Joshua Graham" <email@example.com> wrote on 16 nov 2004 in
> I ran Winnt32.exe /checkupgradeonly before I upgraded the
> server and the
> only thing it told me was that I would have to re-intall
> Diskeeper. This server was having problems before, I could not
> boot it up without a boot up floppy. The server did work with
> Terminal Server though. I really wanted to reload the server
> from scratch, however, I was afraid of losing all my terminal
> settings. I have another Terminal server that is Windows 2000
> and if I wipe out the server and reload it with Windows Server
> 2003 and install the CALs for Server 2003, will this break my
> Windows 2000 terminal server. Thanks for the help and input.
> "Vera Noest [MVP]" <firstname.lastname@example.org> wrote
> in message
>> OK, you seem to have some serious problems :-(
>> Maybe something went wrong during the upgrade?
>> Have you tried to uninstall TS completely (in Add/Remove
>> Windows Components) and then install it again?
>> Note that this is *not* a pretty solution, if it works at all,
>> since it will force you to re-install all of the applications
>> that demand multi-user capabilities.
>> Regarding the WMI error:
>> check the info on eventid.net and Microsoft for this problem:
>> = 1033&ProdVer=5.2
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> --- please respond in newsgroup, NOT by private email ---
>> "Joshua Graham" <email@example.com> wrote on 15 nov 2004 in
>>> I am running both on the same box and Terminal Service is
>>> not starting.
>>> It says it cannot find termsrv.exe in C:\winnt\system32 and I
>>> have searched for it and it is not there. I am running TS in
>>> Application mode, well it has 4 processors and 4 gigs of ram,
>>> plus only about 2 to 5 users will use it at one time anyway.
>>> Also, I am getting this in the event log.
>>> Event Type: Error
>>> Event Source: Userenv
>>> Event Category: None
>>> Event ID: 1090
>>> Date: 11/15/2004
>>> Time: 3:12:10 PM
>>> User: NT AUTHORITY\SYSTEM
>>> Computer: Server name
>>> Windows couldn't log the RSoP (Resultant Set of Policies)
>>> session status. An attempt to connect to WMI failed. No more
>>> RSoP logging will be done for this application of policy.
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp. (I have done this
>>> and I can connect)
>>> "Vera Noest [MVP]" <firstname.lastname@example.org>
>>> wrote in message
>>>>I sounds as if this server ran both Terminal Services and
>>>> Server Licensing Service, is that correct?
>>>> Which of those services doesn't start?
>>>> Is there anything in the EventLog on the server?
>>>> Note that running TS in Application mode (which I assume that
>>>> you mean?) is not recommended on a DC, for security and
>>>> performance reasons.
>>>> Vera Noest
>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>> --- please respond in newsgroup, NOT by private email ---
>>>> "Joshua Graham" <email@example.com> wrote on 15 nov 2004
>>>> in microsoft.public.windows.terminal_services:
>>>>> I just upgraded my last DC to Windows Server 2003 and this
>>>>> server was also my Terminal Server. I got my CALs from MS
>>>>> and I re-activated the server and installed the new CALs,
>>>>> however, I connect connect to this server. What did I do
>>>>> wrong. The terminal service will not start, was I suppose to
>>>>> do anything to the server prior to me upgrading it to Server
>>>>> 2003, I mean for Terminal Services. It had all the Service
>>>>> Packs and hotfixes on it.