Event ID - 1022

Event Id1022
SourceMicrosoft-Windows-TerminalServices-SessionBroker
DescriptionTerminal Server %1 is not configured properly for redirection from legacy servers and should report only a single IP address to Session Broker.
Event InformationAccording to Microsoft :
Cause :
This event is logged when the Terminal Server is not configured properly for redirection from legacy servers and should report only a single IP address to Session Broker.
Resolution :
Use a single IP address for redirection
To resolve this issue, reconsider the use of multiple IP addresses for redirection on Windows Server 2008-based terminal servers in terminal server farms that are comprised of Windows Server 2003 and Windows Server 2008 terminal servers.
A Windows Server 2003-based terminal server cannot redirect users to a Windows Server 2008-based terminal server that has more than one IP address configured for redirection, because Windows Server 2003-based terminal servers do not support multiple IP address redirections.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To configure the IP address to use for redirection:
  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under TS Session Broker, double-click Member of farm in TS Session Broker.
  4. On the TS Session Broker tab, under Select IP addresses to be used for reconnection, select the check box next to the single IP address that you want to use.
  5. Click OK to close the Properties dialog box.
Verify :
To verify that the TS Session Broker server can successfully communicate with the terminal server:
  1. On the terminal server, start a new Terminal Services session.
  2. After the session is established, disconnect the session.
  3. On a different terminal server, but one that is also a member of the same farm in TS Session Broker, try to reconnect to your existing session. If you are able to reconnect to the existing session, the TS Session Broker server is successfully communicating with the terminal server.
Reference LinksEvent ID 1022 from Source Microsoft-Windows-TerminalServices-SessionBroker

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh