Hello,
Suggestion- It would be great to be able to rename computers in TOEM (not imaged, just managed via TOEC) or add a "display name" field that is searchable but changeable in the TOEM UI.

Re: UI Login Timeout

Does this still work on the latest version? I've tried setting it to 240, but users still auto log out pretty quick. Not sure what I'm missing
Thanks,
-BW

@brywhi
Also seeing this on the mariadb log.

We used to have the DB server on a separate machine, but I was seeing some weird behavior so I moved the db back to the com1 server. But, I'm seeing the same weirdness even on localhost.

It seems our database crapped itself. Getting tons of errors like this in the ClientAPI.log:

Any ideas?

@eruthon Great idea too- to just rename via PS script.

We manage a lot of remote computers without physical access using TOEM/TOEC, and sometimes it gets crazy trying to figure out which computer is which

Re: UI Login Timeout

Does this still work on the latest version? I've tried setting it to 240, but users still auto log out pretty quick. Not sure what I'm missing
Thanks,
-BW

@theopenem_admin - Is there a propery in log4net that is being set for the client IP? If so I could add it into the conversion pattern.

Hi All,
The password manager we use (passbolt) doesn't like the TOEM UI's password field. Is there an option to allow the password to be auto-filled?
Thanks,
-BW

@theopenem_admin
Ah, yes. The TOEC port is open to the world.

They're coming in pretty rapidly- any way to get the IP address on the log so I can see about programmatically blocking bad actors?

@eruthon Great idea too- to just rename via PS script.

We manage a lot of remote computers without physical access using TOEM/TOEC, and sometimes it gets crazy trying to figure out which computer is which

What does this mean in the ClientApi Toec log?

[11] ERROR Toems_ClientApi.Controllers.Authorization.CertificateAuth The given header was not found.

@brywhi Nevermind... this is fixed. Bad DB config on our part that eventually led to the DB being too slow. Fixed now. Not a TOEM bug at all, definitely an error on my side

@brywhi

Also seeing this:

2023-01-18 17:39:47,446 [88] ERROR Toems_DataModel.UnitOfWork System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> MySql.Data.MySqlClient.MySqlException: Lock wait timeout exceeded; try restarting transaction
   at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
   at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32& affectedRow, Int64& insertedId)
   at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
   at MySql.Data.MySqlClient.MySqlDataReader.NextResult()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.Entity.EFMySqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
   at System.Data.Entity.Core.Mapping.Update.Internal.DynamicUpdateCommand.Execute(Dictionary`2 identifierValues, List`1 generatedValues)
   at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
   --- End of inner exception stack trace ---
   at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions options, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction)
   at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options, Boolean executeInExistingTransaction)
   at System.Data.Entity.Internal.InternalContext.SaveChanges()

@brywhi
Also seeing this on the mariadb log.

We used to have the DB server on a separate machine, but I was seeing some weird behavior so I moved the db back to the com1 server. But, I'm seeing the same weirdness even on localhost.

It seems our database crapped itself. Getting tons of errors like this in the ClientAPI.log:

Any ideas?