What happens?

OK I give up, I have Schema's today on all three of the Schema's I loaded on Friday.
I checked them after each completion. Do the get cached or stored while they are uploaded possibly.
I know where they physically get stored under the TOEMs_Local_Storage/Images.
I checked and yes they did exist on friday. But in the Web Application on the TOEM server these Schema's Did not exits they where blank.
Today they are all available.
I swear I reset the Browser and restarted the server. But nothing
When I tried to deploy I got something like no data found or something shutting down in one minute.
Is in not good to use the Server and Localhost.
Never had a problem before.
I will try the deployment tomorrow morning to make sure that the image is good.
I was also concerned about the noAnser error and this is the only device so far that has ever had that issue.
I will update the ticket if I get any further errors tomorrow
Thanks

Thanks for the quick support! Will be tested as soon as possible!

I haven't seen this where raid was off and it still didn't work. Did you change it to ahci? How old is this model?

Hi @theopenem_admin
With version 1.3.1, I have the process feedback in ToemsUI.
Thanks a lot

@theopenem_admin never mind, I got to work! Thanks

I haven't been able to replicate this issue. Ensure you are setting the global imaging token and saving the changes. Then recreate your pxe boot menu / iso.

@theopenem_admin OMG: Typo! Sorry and THX!

@theopenem_admin
did it again even on a new machine.
I just don't get it to work

I also cannot launch toec client or make the clientboot bootable usb under rufus, not sure where I screwed up, hoping someone can help out

Thanks

You can ignore them. Sounds like a network or driver issue. I would make sure you are using the newest kernel and the drivers on your server are up to date.

@theopenem_admin OK - it was a Qwertz and Qwerty bug! Thx

Working fine for me, perhaps your download is corrupt.

Your issue is the same as this post.
https://forum.theopenem.com/topic/87/deploy-image-error

Your schema isn't missing, it's just invalid. Dell must be doing something different with these new machines causing multiple efi bootloaders to be listed. There is a proposed fix in that thread.

Thanks, not sure why I did that. It's downloading the source instead of just the binaries.

Hello @theopenem_admin,
Works beautifully. I really have very little else to say on it...

I install the agent, and once windows updates are done processing (all msiexec is blocked while it is updating), my provisioning script renames the computers and joins them to my domain. Immediately after restarting, the software pushes in.

Very well done, I am currently auto-adding after provisioning directly to a Toec Group - haven't tried an AD OU yet...

Thank you so much!

This was fixed in 1.3.2, no need to rename file. I would double check that you completed each section in https://docs.theopenem.com/getting-started/configure/

Thanks for the update

That's basically it. Install Toec and it's registered. Have you watched the videos?