@theopenem_admin Awesome, thank you.

Hi,

We're seeing all of our Windows 10 endpoints being reported by Theopenem as being 2009. We know by our WSUS server that they are all actually 21H2 though - is this a bug in the software or are we doing something wrong.

I've just updated Toec from 1.4.4 to 1.4.8 also, forced a checking and there's no update unfortunately.

Leigh

Actually, we're all good now - it was because of the firewall blocking ports (we've opened UDP 9000-10000, but can you tell us what the full range it will use?)

Cheers,
Leigh

Further to this, i've got:

2022-02-02 16:25:11,987 [20] ERROR Toems_Service.FilesystemServices Could Not Read Schema File.
2022-02-02 16:25:11,988 [20] ERROR Toems_Service.FilesystemServices Could not find a part of the path 'C:\toems_local_storage\images\baseImage\schema'.
2022-02-02 16:25:20,572 [25] ERROR Toems_Service.FilesystemServices Could Not Read Schema File.
2022-02-02 16:25:20,573 [25] ERROR Toems_Service.FilesystemServices Could not find a part of the path 'C:\toems_local_storage\images\baseImage\schema'.
2022-02-02 16:25:22,825 [25] ERROR Toems_Service.FilesystemServices Could Not Read Schema File.
2022-02-02 16:25:22,825 [25] ERROR Toems_Service.FilesystemServices Could not find a part of the path 'C:\toems_local_storage\images\baseImage\schema'.

I've looked on the server (using 1 server for everything), and there's nothing in there.

Leigh

Hi,

I'm trying to upload an image, but i'm having difficulty. I'm following the 'universal image' video. I've sysprep'd the machine, booted off the USB and tried to start an upload.

However, I'm getting stuck on 'Creating Image Schema'.

The application log is saying:

2022-02-02 16:16:49,374 [32] ERROR Toems_Service.FilesystemServices Could not find a part of the path 'C:\toems_local_storage\images\baseImage'.

I've checked the com server ip settings, and i've also managed to upload the drivers to the c:\toems_local_storage so i know the file upload is working. I've even tried creating the 'images' folder through windows explorer, and given 'everyone' full access to the folder - nothing seems to work.

Any ideas?

Thanks,
Leigh

@theopenem_admin That was it, much appreciated. Com server was set to https - changed this to http, rebuilt the clients and re-installed.

Seems to be working now - I guess I'm so used to typing https!

Many thanks,
Leigh

@theopenem_admin Any other ideas? (Short of a re-install?)

@theopenem_admin Yes, I did that - followed the instructions word for word (got the '60').

@theopenem_admin

Just did that to check - same error.

Hi,

We're trying to evaluate Theoepenem for use in our network, so we've done a fresh install. After following the install tutorial, we're getting the following on the first client we're trying (pre-provisioned via LDAP/AD sync)...

2022-01-24 21:56:35,013 ERROR [4] ApiRequest - Error Retrieving API Response: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at RestSharp.Http.GetRawResponse(HttpWebRequest request)
   at RestSharp.Http.GetResponse(HttpWebRequest request)

Any thoughts? We do have a firewall between the client and the server, but that's not blocking anything on port 8888.

Thanks,
Leigh