Diferrence between guidance and monitor in Tivoli remote control

Usage and Config
1

(imported topic written by SystemAdmin)

Hi All,

What is the difference between guidance and monitor in tivoli remote control session?

Also during session, we use hdsupport to login to start a remote session and it detected different user which is the local user of the controller PC, Any idea on this?

Thanks in advance,

Braian

2

(imported comment written by SystemAdmin)

Hi,

The guidance mode is just an “enhanced” monitor view that allows you to draw instructions on the remote machines, for instance, you can highlight an area of the screen, draw a circle around an icon in the desktop, etc. It lets you guide the remote user through the different actions that may be required but you are still unable to actually control the remote machine.

I am afraid I am not familiar with hdsupport, but if you can provide more details on this, I can investigate further.

Thanks

Regards,

Pati

3

(imported comment written by SystemAdmin)

Hi PatiN

Thanks for the info, hdsupport is an ad account for helpdesk support, for example i login to PC as braian then i started a remote session and use the hdsupport as authentication, the target PC detected braian instead of hdsupport.

Thanks,

Braian.

4

(imported comment written by SystemAdmin)

Hi Braian,

This works as designed. The user acceptance dialog displayed to the end user will always show the controller user (as opposed to the userid used for authentication), however, you can see the authentication details in the audited data in the application event log:

Audit the peer to peer controller user (MR0428114043)

An additional audit improvement has been implemented for this

enhancement request, which was implemented in IF0009 for

improved user acceptance auditing.

This enhancement improves auditing for P2P sessions that

require user id and password authentication against the target

system, that is those where CheckUserLogin is enabled.

In line with the previous enhancements in MR0428114043

Improved auditing for user acceptance, the session rejected

audit event was also improved to allow authentication to be

audited in sufficient detail.

To improve auditing, the following audit event was deprecated

and replaced with 9 new audit events.

Deprecated audit event

Event ID

Event Description

ibm.trc.audit.0002

Session Rejected by {0}

New audit events

Event ID

Event Description

ibm.trc.audit.005A

Authenticating user ID {0} using system logon.

Allowed groups: {1}

ibm.trc.audit.005B

Session rejected because the user ID or password is

incorrect

ibm.trc.audit.005C

Session rejected because the user is not a member

of an allowed group.

ibm.trc.audit.005D

Session rejected by {0}

ibm.trc.audit.005E

Session rejected automatically after {0} seconds

ibm.trc.audit.005F

Session rejected because the session token is invalid

ibm.trc.audit.0060

Session rejected because the session token has

expired

ibm.trc.audit.0061

Session rejected because the session token is for a

different target

ibm.trc.audit.0062

Session rejected by the server for unknown reason {0}

ibm.trc.audit.0063

Session rejected because {0} mode is not allowed

ibm.trc.audit.0064

Session rejected due to a connection error

Note : This enhancement does not modify the id that is displayed to the end

user in the user acceptance window:

  • if the session is initiated from the TRC server, it will display the id

that the controller uses to authenticate against the TRC server

  • if the session is initiated by launching the standalone controller console,

the window will display the ID the controller user uses to log on to their

local system.

Hope this helps.

Regards,

Pati