@eruthon Checked multicast functionality after disabling SMB, and set a queue size of 2. However, imaging started without waiting for the second PC and failed, as indicated in the screenshot below.

11-21-23 12:24 Starting Multicast Session With The Following Command: cmd.exe /c ""C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part2.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log & "C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part3.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log & "C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part4.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log"

@curling0221 I am being faced with this problem again. Did you ever find a resolution to it?

@theopenem_admin I apologize for the delay. I was able to get the autodiscover and everything to work now seemingly. It registers the computers and gets up to the point where I can just about deploy an image... I can see the task in the webgui... I can see the computer listed with the custom name I gave it under imageonly under computers... yet I cannot see any of our images to be able to deploy them to this offsite computer. Any idea why? It just says no images instead of the 5 or 6 we have present.

@theopenem_admin

Thank you very much for your help,

Deployment now works fine with SMB. The manual is also very clear and easy to follow.

Thanks again for the support we can continue deploying our computers.

Sincerely,

Melvin

need to be: Windows/System32/config/SYSTEM
There is: Windows/System32/config/system
renaming system to SYSTEM

Standard is the most reliable, you just need to select the correct windows partition below when standard is selected.

@theopenem_admin 1.4.8/1.4.5 client

@ggalindo Just an update,
I got it working
Installed CD_Proxyd as a service and rebooted and everything started working
Very nice.
Thanks for the help
I will watch the video anyway just to make sure I got everything correct.

@theopenem_admin Will do Thanks very much!

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.

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.

You need a dhcp server that supports pxe boot. An at home router will not do that. You need an extra piece called a proxy dhcp server. Have you looked at this video? https://www.youtube.com/watch?v=041BeOI6_cc

You can ignore the dhcp settings in the video and just focus on the proxy config.

@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
Apologise for the delay here is the logs:

2021-12-16 09:48:22,576 [40] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=a1133a15-c991-40e0-b5c8-6e783c432dea, O=MSLS PARTNERS LLC 2021-12-16 09:49:29,234 [5] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:49:59,453 [15] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:50:29,689 [8] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:50:59,924 [43] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:51:18,862 [40] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=b7ef8896-0ed4-4586-9d1f-b4caf6feb44b, O=MSLS PARTNERS LLC 2021-12-16 09:51:30,128 [40] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:52:00,348 [63] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:52:30,567 [37] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:53:00,756 [8] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:53:30,960 [40] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=afe4c669-7138-41ee-80bb-c448e87c51d7, O=MSLS PARTNERS LLC 2021-12-16 09:55:33,589 [40] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:56:03,778 [13] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:56:33,964 [15] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:57:04,197 [43] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:57:09,431 [37] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=f7646c25-5865-40ce-98ed-f3599805c645, O=MSLS PARTNERS LLC 2021-12-16 09:57:34,351 [43] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:58:04,569 [5] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:58:34,771 [13] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:59:04,957 [37] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 09:59:35,176 [13] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=5e349698-3d2b-4ad3-a565-b7e76cc6de8c, O=MSLS PARTNERS LLC 2021-12-16 10:01:07,980 [60] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=2b57c5c0-d1c1-4ee3-9468-465bf912ff54, O=MSLS PARTNERS LLC 2021-12-16 10:01:38,211 [13] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=2b57c5c0-d1c1-4ee3-9468-465bf912ff54, O=MSLS PARTNERS

We are thinking it might be something in the bios of the computer. It is using a usb-c ethernet adapter, but we tested the adapter with another computer with usb-c and the adapter works fine on that computer. We have ordered the special network adapter for the laptop and are going to test that out, if it still doesn't work, we might go in and start looking at bios settings to see what we might try changing. Any recommendations?

no. there are diffrent models with the same issue.

I'm now pretty sure it has something to do with the network configuration. pxe server is in another subnet/vlan than clients. I did a test with a client in the same server vlan and it worked all the time.

I tried setting an ip-helper but that didn't solve it. I'm digging deeper since the issue has to be in the network imo.

if you have any experience or tips that would be much appreciated.

One way to find out, then Tally-ho

@theopenem_admin Ugh. I feel so dumb. I just ran out of space on the drive where we store our images. Thanks so much for your help!

@d_rock said in Could Not Save Image Schema - 800+ GB Image:

Do I need to have SMB enabled before capturing the image

No, you just need to replicate the storage so the image syncs to the smb share, or manually copy it over.

A year later and I finally got this set up and with your video it was really easy!
So how do you run the report for Application Usage Tracking? Maybe a video on reports would help other too? When I run the Process Report I get no Processes found. I have the client to checkin interval set to 5 minutes so it should have caught some usage. I'm probably doing something wrong.