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
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
@theopenem_admin said in The pipe has been ended:
direct SMB imaging with the WIE
is there a guide on how to do this?
We were thinking as a 2nd option to make our own windows pro usb stick and boot from it and run your script from there to deploy. Where can I find the script to make the connection with the image server? then we also want to try if this is still an option.
Thanks in advance for your time and help
Regards Melvin
Melvin - Dear support,
We added the drivers in the windows PE but it didn't help. he goes creating files he stops at the 96% and then we get the error "curl: (23) Failure writing output to destination" he then immediately reboots.
other systems are fine like dell computers. Do you have any idea what it could be?
Thank you in advance
After trying 10 times it will work. This is of course not the intention.
If we deploy another system, another type of PC, it will work right away, it is specifically 2 systems that do not work, called colormatric
We try to deploy a system but we get the following error in the logging of TheOpenEM:
[ERROR] Error reading 359 bytes from fd 0 (err=109): The pipe has been ended
[ERROR] Error reading data from WIM file: Broken pipe
ERROR: Exiting with error code 50:
Could not read data from a file.
** Making System Bootable **
Failure when attempting to copy boot files.
on the computer we are trying to deploy we get the error:
curl: (23) Failure writing output to destination
Maybe 1 of you know where we should look to solve this problem?
We have a windows server 2019 version running