I am trying to do this too, I am using proxy, I have modified the default files in the 3 folders under C:\Program Files\Theopenem\tftpboot\proxy (bios, efi32, efi64) but the changes do make any difference, even if I try to rename a label. Then I seemed to remember I needed to regenerate boot files, and that made no difference other than resting the default files back to default setting of 50

@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
Thanks for the hint- you lead me in the right direction.

I fixed it. My fault- I had created some triggers on a few tables for some additional reporting I wanted to do, and they had a definer user specified in the mysqldump backup that didn't exist on the new server. After changing the definer to root in the mysqldump prior to recovering, everything is working!

Turns out I did. Here's what happened:

Oddly, it shows it having received an IP address in the second screen.

The third screen is after I've assigned a static IP to it (A random valid one or the one listed above do the same thing)

Just run that command before you sysprep and you'll be fine.

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!

@theopenem_admin when I enable efi on the virtual machine setting in virtual box. I no longer have to ability to f12 into pxe boot. And the vm will not boot. And I also don’t understand because the laptops are dual legacy and uefi. I’ve never had to click enable efi before and it imaged the drives just fine.

@theopenem_admin Thanks, that would be great.

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?

@jgitta
J
jgitta
27 Jun 2023, 10:32

@theopenem_admin
Hi, I also have the same problem, I can't log in with the initial user.
Can you help me find the correct password via the web.config file? Thank you

@theopenem_admin

Sorry misunderstood what you were saying that worked thanks for your help and great product man really nice.

Following my suspicion of IIS, I logged in as the (Built-in) Administrator and used Server Manager to remove IIS and its dependencies completely, and then ran the installer again and now it works. Looking at the Server 2019 image I have (installed via WDS), it has IIS enabled by default, so IIS was corrupted from the start.

I am now able to log into the web ui without issue.
Thanks for your help diagnosing this, if someone finds this in the future, I hope it helps!

Are you just testing this installation, or have you pushed it out to your computers. If you are just testing so far. I would regenerate your toems ca and and intermediate. Install the new certs on your server, regenerate Toec. Install Toec on a new machine. To rule all of those things out.

@theopenem_admin Thank you for helping!

WIW, I have the same situation, and the only thing that seemed to work for me was to make sure that all storage settings were set to local, on the main server, and secondary com servers, and to make sure upload/deploy direct to SMB was disabled. Works like a charm after that.

@theopenem_admin Thank you so much! After the last two days of testing and use, I'm seeing speeds saturating my gigabit connection.
And reliability is now rock-solid. Before, creating images was extremely stressful, as timeouts and errors would happen more often than not, with no obvious notice. I can now create images without worry.

Thanks again!

that's good, thought you were using winpe not linux.

Hello,
I got it to work by breaking the large folders up into several Zip file no larger that 2.3GB that seemed to work. So I used 2 File Copy Modules and then linked them with different priorities to the Image and it does work. A lot of work for what used to be one step in CD.

Thanks for the help!!!

@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?