How to show logs terminal server other then console session (intouch)

Hi Roland,

This is normally done by filtering on the Session ID and this is usually the IP address if the connecting client.

(The LogViewer filter does not list all available Session ID's and you need to add this 'Show' filter manually).

But you could also add the column Session ID to review the available sessions in the log, if there is by any chance that the session you are looking for is not listed, then it requires additional troubleshooting.

I hope this helps.

Richard

Richard,

When we open de logger view we only see sessionID 0 , we don't see the other sessions. Do we need to do something on the terminal server it zelf.

Richard, 

Here is a screenshot : 

We only see sessionID 0 even if we added the filter to the thin clients 

With regards,

Roland

This could happen if your server is not running in Terminal Server mode, (With the Terminal Server Feature enabled).

If you connect to a server using Remote Desktop it will be in "Remote Administration" mode and your clients will not create Sessions in the same way as in a real Terminal Server environment.

(This is not Terminal Server)

Even though I have two users active, sessions will not be created by windows.

But this mode will limit you to two connections and that you do not log in using the same user, so perhaps this is not the case since you mention that you have multiple thin clients up and running?

And if I understand you correctly, you do not see the logs from the client session at all?

Just want to clarify before we move on to other things.

I would start with unchecking All of the the Terminal Sessions filter and review the log without any filter to ensure that you see ALL logs and use this as a baseline, as soon as you verified that you have the logs you are looking for in the list, you can start going in to filtering to review them session by session.

The server is setup as terminal server,It's a windows 2022 server (TS). We have several clients connected by a different usernames. When i remove all the filters i still see only sessionID : 0 . When i go to the server manager i see the connections, i can take over a client with shadowing. 

What do we miss here.

Ok, then we at least ruled out the simple things

And I guess that the log activity you are looking for on the session is non-existent, or does it log, but it tags it with session 0? 

Thanks for he support. Possible its a setting on the terminal server. 

Could be, I was somewhat intrigued by your issue since I did not see this problem in one of the systems I have running, but that was older OS and System Platform Version (2019 Server & SP 2017), so I went ahead and set up a new system using Windows Server 2022 and System Platform 2023 R2, 

In this system I could reproduce the issue that all sessions were logging on session 0 in SMC.
I could still see the logs from all sessions, but all where logged with Session 0 (in SMC).

Still don't know if this was the case for you? so please confirm if your entries are logged at all, or not.

The problem is that all the clients has the same code, so we can't see witch client (SessionID) it should be if the log all under sessionID : We should see a push button event when we click on a client (not the console session). this is not shown in the log.

I understand, but if you review based on the ProcessID this should be unique based on each view.exe process running.

You find the matching process ID (PID) in TaskManager

This PID is then listed in the Process ID column

This would allow you to identify from what session the entry is coming from.