@theopenem_admin Thank you so much. Looking forward to the release!

@theopenem_admin Im in a university setting on a sub orginzation level.

We have only 100 computers in our ORG, but our AD has over 20,000

@theopenem_admin The Linux environment works fine yes. The problem it doesn't work as smoothly for deployment because of the need to change boot settings for secure boot.

@theopenem_admin Awesome, thank you!

Thanks, it will be nice to cleanup some of those installation null refs.

Looking at the LDAP changes, it seems we are just effectively changing the base dn for syncing. It's not really a group filter. This leaves the authentication alone to use the original base dn. I wonder if we should just have 2 fields, it's basically just semantics at this point.

Authentication Base DN
Computer Sync Base DN

Which then leads into what if we want multiple DN's. Feel free to do as much or as little with this. At the very least you've motivated me to dig deeper into this for the next release.

Thanks again.

https://forum.theopenem.com/topic/223/required-ports?_=1648301332308

Currently you can't select which images are replicated to which location. You can only sync or not sync images to that com server. It's something I could add though. If you want to add this to the feature requests sections of the forums so I don't forget about it, that would be helpful

@theopenem_admin

Thank you so much for your quick response.

I will try out this out as you descirbed.

One thing is would it be possible to access the web UI from anywhere remotely kind of like how faronics delpoy is.

I would like to be able to access the web UI from home and not in the office. Probably best practice would be to vpn into my office and then access the web ui.

Have you followed this guide?

https://docs.theopenem.com/tutorials/wie/

It's on the policy. Change the trigger type.

@edwinjamess This fixed my problem instantly thanks for posting this fix !!!

@theopenem_admin I was able to get this fixed, I needed to point to each of the different ARCH to their respective bootmgfw.efi once I did this the WIM images worked just as expected ! Thanks for all of the help and assistance !

@theopenem_admin
Thanks for pointing me in the right direction. There was no https binding and I'm getting that set up now.

@theopenem_admin
Thanks! I think the inventory bug is what was causing the issue I saw - I was not seeing the deployment had happened and thought the failure was with Checkin. When I went to the Computer level and ran the commands I always ran the Checkin first, and then looked at the inventory. I assumed Checkin at group is what wasn't working, but probably had; the reality is the push had happened but the inventory hadn't updated until I ran Inventory on the Computer side.

Thank you for checking into it!

@theopenem_admin No the image name is "clientboot"

When you generate your iso in Theopenem, there is an option to disable secure boot. You need to change that option before you generate the iso.

@daodio2 said in zero touch win deployment via client:

@daodio2 said in zero touch win deployment via client:

@daodio2 said in zero touch win deployment via client:

@daodio2 in other words initiate a re-image task with the client selecting the f12 option or the windows setup task and reboot.

similare to the MDT to create a zero touch ISO and call on the task sequence. FOG does something similar if i'm not mistaken, this would be a great feature.
Can you make video on this topic ?

@theopenem_admin oh excellent I’ll try to install it right over top of the existing toec client. Fingers crossed it will refresh the connection to the new server. Thanks again.

@theopenem_admin Afternoon

Yep, clean install with only TOE installed

URL shows the correct port 8888 aswell under cluster.

Thanks

I would review the docs for adding the com server and modifying the web.config file. It seems that you missed something in that area.