Re: Enterprise LicenseServer reg key not being read

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

Date: Tue, 11 May 2004 14:37:31 -0700

Certificates explained here.

323597 - Windows XP Clients Cannot Connect to a Windows 2000
Terminal Services Server
http://support.microsoft.com/?kbid=323597

You might need to delete them to be able to connect (especially if
you updated the server with the latest security patch).

Discovery process explained here:
Windows Server 2003 Terminal Server Licensing White paper
http://www.microsoft.com/windowsserver2003/techinfo/overview/terms
ervlic.mspx

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

"Steve Schofield" <steve@adminblogs.com> wrote in
news:O1F3705NEHA.2740@TK2MSFTNGP11.phx.gbl:

> i'm running into an issue where when i load a windows 2003
> server in *app mode*, place the
> LicenseServers\NameofEnterpriseLicenseServer registry key
> according to
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;279561
> I get client mis-match event id 1004 errors when connecting via
> RDP. The only reason I can see why RDP works at all is their is
> a registry key that has a 15 day grace period for logins. The
> only thing I can tell, i've not found documentation explaining
> the process in detail is once a server is put in app mode, has
> the registry keys set to over-ride the discovery process between
> this newly created *app mode* server and the enterprise license
> server. We have one server that has two registry keys. They
> are called X509, X509 ID under the TermService\Parameters\
> registry key. Does anyone know or seen this behavior? Or any
> documentation discussing the discovery process in detail and how
> these X509, X509 ID registry keys play into this?
>
> Steve Schofield

Relevant Pages

  • SecurityFocus Microsoft Newsletter #154
    ... MICROSOFT VULNERABILITY SUMMARY ... ISS RealSecure Server Sensor SSL Denial Of Service Vulnerabi... ... Roger Wilco Remote Server Side Buffer Overrun Vulnerability ... available for Microsoft Windows operating systems. ...
    (Focus-Microsoft)
  • SecurityFocus Microsoft Newsletter #49
    ... Subject: SecurityFocus Microsoft Newsletter #49 ... Microsoft Windows NNTP Denial of Service Vulnerability ... Microsoft IIS SSI Buffer Overrun Privelege Elevation Vulnerability ... Microsoft ISA Server H.323 Memory Leak Denial of Service... ...
    (Focus-Microsoft)
  • ~~~~~~~~~~~~~~ CANNOT FIND ~~~~~~~~~~~~~~
    ... acrobat cannot find external windows handler ... activesync cannot find exchange server ... aol internet explorer cannot find server ... brother network scanner cannot find pc ...
    (sci.geo.fluids)
  • ~~~~~~~~~~~~~~~ CANNOT FIND ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ... cannot find server or dns error ... windows cannot find null ... windows cannot find the network path ... cannot find internet explorer on computer ...
    (comp.protocols.snmp)
  • Re: Secondary DNS and PIX
    ... in SBS SP1 you can substitute Windows Server SP2 and Exchange SP2 for the earlier versions, you do not need to back out of current levels. ... Change the value of the DisableTaskOffload registry key to ...
    (microsoft.public.windows.server.sbs)