[RESOLVED] Admin account created on hosts

[Benbatt]

Hello,

The context:
Access to the console is via an LDAP admin group, so each admin has an account like admin_admin1.
I've noticed that on client PCs, I find these users in c:\users\admin_admin1.
Is this normal WAPT behavior, or should we use a generic account to avoid cluttering the PCs?

WAPT 2.5.5.15640 Enterprise

[sfonteneau]

I noticed that on client PCs, I find these users in c:\users\admin_admin1.

Can you elaborate on that?

I don't understand what this is; it's a folder, what's in it? Is it on all client workstations?

[dcardon]

Hi Benoit,

if you're escalating privileges to launch the console with an admin account to enable Kerberos authentication, it's normal for there to be a local directory for that account on the admin's machine. Windows treats privilege escalation as a login (with the user directory and all that).

However, this shouldn't create accounts on every machine in the network.

Regards,

Denis

[Benbatt]

Ultimately, WAPT wasn't the problem (another deployment in the same week --')

Otherwise, I have a real question,
My users have reported that PC shutdown has been slow since the installation of the Wapt agent
I have logs

• 2024-07-11 20:42:37,082 [wapttasks SocketIOClient 12276] INFO Connecting Socketio to https://superserver.cab.local:443
  2024-07-11 20:42:37,184 [waptws SocketIOClient 12276] WARNING Exception ConnectionError('Connection error'), waiting 60s before retrying
  2024-07-11 20:43:37,194 [wapttasks SocketIOClient 12276] INFO Socketio connection params have changed. Socketio needs reconnect
  2024-07-11 20:43:37,194 [wapttasks SocketIOClient 12276] INFO Creating socketio client: https://superserver.cab.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.pem') proxies: None verify_cert: C:\Program Files (x86)\wapt\ssl\server\superserver.cab.local.crt
  2024-07-11 20:43:37,194 [wapttasks SocketIOClient 12276] INFO Connecting Socketio to https://superserver.cab.local:443
  2024-07-11 20:43:37,278 [waptws SocketIOClient 12276] WARNING Exception ConnectionError('Connection error'), waiting 60s before retrying
  2024-07-11 20:44:37,291 [wapttasks SocketIOClient 12276] INFO Socketio connection params have changed. Socketio needs reconnect
  2024-07-11 20:44:37,291 [wapttasks SocketIOClient 12276] INFO Creating socketio client: https://superserver.cab.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.pem') proxies: None verify_cert: C:\Program Files (x86)\wapt\ssl\server\superserver.cab.local.crt
  2024-07-11 20:44:37,291 [wapttasks SocketIOClient 12276] INFO Connecting Socketio to https://superserver.cab.local:443
  2024-07-11 20:44:37,401 [waptws SocketIOClient 12276] WARNING Exception ConnectionError('Connection error'), waiting 60s before retrying
  2024-07-11 20:45:37,418 [wapttasks SocketIOClient 12276] INFO Socketio connection params have changed. Socketio needs reconnect
  2024-07-11 20:45:37,418 [wapttasks SocketIOClient 12276] INFO Creating socketio client: https://superserver.cab.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.pem') proxies: None verify_cert: C:\Program Files (x86)\wapt\ssl\server\superserver.cab.local.crt
  2024-07-11 20:45:37,418 [wapttasks SocketIOClient 12276] INFO Connecting Socketio to https://superserver.cab.local:443
  2024-07-11 20:45:37,450 [waptws SocketIOClient 12276] WARNING Exception ConnectionError('Connection error'), waiting 60s before retrying
  2024-07-11 20:46:37,468 [wapttasks SocketIOClient 12276] INFO Socketio connection params have changed. Socketio needs reconnect
  2024-07-11 20:46:37,468 [wapttasks SocketIOClient 12276] INFO Creating socketio client: https://superserver.cab.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\ordi1.cab.local.pem') proxies: None verify_cert: C:\Program Files (x86)\wapt\ssl\server\superserver.cab.local.crt

[sfonteneau]

My users have reported that PC shutdowns have been slow since installing the Wapt agent

Is waptexit visible in this case?

[Benbatt]

No, that's not the case, but these errors slow down the PC shutdown; in some logs, it takes more than 3 minutes.
I'm on the latest release of the WAPT agent and server.

[dcardon]

Hello Benoit,

thank you for keeping each forum topic separate. I'm closing this one; please open a new one for this second topic.

Regards,

Denis