Re: Upgrade of W2K Server to Windows 2003 Terminal Server

From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 11/16/04


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
boot....

I don't understand you last question. How would a fresh install of
one server break another one?

 --
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
 --- please respond in newsgroup, NOT by private email ---

"Joshua Graham" <grahamjo@hotmail.com> wrote on 16 nov 2004 in
microsoft.public.windows.terminal_services:

> Vera,
>
> 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.
>
> Josh
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns95A2EA36F489Dveranoesthemutforsse@207.46.248.16...
>> 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:
>>
>> http://www.eventid.net/display.asp?eventid=1090&eventno=1881
>> &source=Userenv&phase=1
>>
>> http://www.microsoft.com/technet/support/ee/result.aspx?
>> EvtSrc=Userenv&EvtID=1090
&ProdName=Windows+Operating+System&LCID
>> = 1033&ProdVer=5.2
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "Joshua Graham" <grahamjo@hotmail.com> wrote on 15 nov 2004 in
>> microsoft.public.windows.terminal_services:
>>
>>> Vera,
>>>
>>> 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
>>> Description:
>>> 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]" <vera.noest@remove-this.hem.utfors.se>
>>> wrote in message
>>> news:Xns95A2E075D3A77veranoesthemutforsse@207.46.248.16...
>>>>I sounds as if this server ran both Terminal Services and
>>>>Terminal
>>>> 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
>>>> http://hem.fyristorg.com/vera/IT
>>>> --- please respond in newsgroup, NOT by private email ---
>>>>
>>>> "Joshua Graham" <grahamjo@hotmail.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.



Relevant Pages

  • Re: W2k TS & XP Rdp
    ... "For Windows 2000 Terminal Servers, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Server (the "Existing Windows 2000 TS CALs"), ...
    (microsoft.public.windows.terminal_services)
  • RE: Terminal Server Migration Windows NT to Windows 2003
    ... Currently Windows 2003 Terminal Server is member of Windows NT domain. ... > You may join the Win2k member server running as Terminal Service Licensing ...
    (microsoft.public.windows.server.migration)
  • Re: Printers not clearing out
    ... We have a problem that when a user logs out from the terminal server the ... built in drivers or WHQL drivers provided by the manufacturer. ... Windows Built-in PCL or PS Drivers - Version "Windows 2000, ...
    (microsoft.public.windows.terminal_services)
  • RE: TS does not work after upgrading from SBS 2003 SP1 to SP2
    ... Windows Update as it was a "recommended update". ... terminal server on SBS after you install Windows server 2003 sp2. ... Based on my research, Terminal Server is available on the Standard, ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: altes Windows XP als Lizenz =?ISO-8859-1?Q?f=FCr_Windows_?= =?ISO-8859-1?Q?2000_
    ... Windows XP Professional licenses acquired through volume licensing Using the Install Licenses function of the Terminal Server Licensing administration tool, a customer needs to provide volume licensing program information depending on program type, along with the requested quantity and type of TS CAL tokens. ...
    (microsoft.public.de.german.windows.terminaldienste)