Posts made by itisljar

@surfboy sorry for late reply!

I've had even worse problems lately, so I am doing some troubleshooting; image speeds fall down to 1 GB / min, imaging lasts about 15-20 minutes. I have spare SSD 2.5" drive, SPPC, I've disconnected NVME, put SSD in and put image to that SSD drive - speeds are as expected, around 5.5 GB / min.

In desperation, I've created image with Aomei Backupper, which works through WinPE boot disk, and it works great. Speeds are around 120 MB / s, which was expected from cheap USB3 device, and it took around 5 minutes to finish.

So, linux drivers / support for NVME is the problem here, not network.

@theopenem_admin can something be done about that? WIE is currently not an option, unfortunately.

Hello!

I have Dell Optiplex 3070 machines which have slow image downloads. It takes around 12 minutes for 20 GB image, and all my other machines, some of them are 10 years old, need around 4-7 minutes, with images of similar size. It has NVME disk so it shouldn't be a problem.

I've read somewhere that slow download speeds could be connected with unsupported or half supported network drivers. Kernel used is 5.17.3.

@theopenem_admin Yes, I saved the changes, verified them by setting console as the default selection for boot menu, so it has been loaded. But no setting I've tried can change the keyboard once the login has been shown. I am guessing I will have to recreate the boot files, I think initrd will have to be reconfigured. I have access to linux OS (Rocky Linux 8 and 9) so I think I can do it, but I don't have knowhow - well, time to learn. Can it be done? Can I manually reconfigure it?

Hello!

Sometimes I have a computer which has additional HDD installed for storage; depending on SATA cable placement and controller, TOEM sometimes selects wrong /dev/sda and images the wrong hard drive. Can it be made that, when you image a machine with two (or more hdds) you can select which hdd the image will get on?

@theopenem_admin

Unfortunately, it doesn't work.
Tried:
keymap=hr
keymap=HR
keymap=hr-HR
keymap=croat
loadkeys croat (this works when I start the console from boot menu and log in, then change manually, but not for login and password)

Should I pass some kernel arguments in boot menu? (EDIT) I tried passing arguments there, didn't work. So, what's the next step?

Here I am again

Now, can the keyboard layout be changed somehow when booting from network? It defaults to US, which is unfortunate for us because we use QWERTZ layout.

How could I do that? Is it possible? I need to apply hr-HR layout.

@theopenem_admin I'm dumb

You pointed me into right direction. It's not secure boot related, it's UEFI network boot related. It doesn't work. But, when I enable legacy mode and boot like that, it works. I guess I have to set up DHCP proxy on server.

Hello!

I tried setting up TheOpenEM on our "server" network, which is on different subnet. I've set it up as standard, LIE server, not WIE. Subnets can talk to each other and are part of our bigger company network, we have quite a lot of subnets.

Our work subnet is different one, and I can't get PXE to boot. I don't get errors, just... not booting. It's Dell Optiplex 3070. I get this, when I start boot:

Start PXE over IPV4 on MAC: xx-xx-xx-xx-xx-xx
Station IP address is 10.1.36.30

Server IP address is 10.1.79.37
NBP filename is pxeboot.0
NBP filesize is 314097 bytes

Downloading NBP file...
NBP file downloaded successfully.

And then goes into BIOS for checking hardware, and doesn't boot. It boots on local server, which I have set up few years ago, with local network and DHCP, separated from everything.

I thought I'd build USB/ISO boot and try from there, and it boots into menu, I select TheOpenEM and it stops booting after few moments with message INIT NOT FOUND

I've read around the forum for a bit and if I understood correctly, the problem is that I have to have COM server on the same subnet I try to PXE boot on. Did I understand the problem (and solution) correctly?

@theopenem_admin Haha yeah, I love troubleshooting these things which are not documented anywhere. I do have a problem though, can't get HR (Croatian) keyboard to work.

I have setup CMD file for building like this:

set TimeZone=Central European Standard Time
set MyLang=hr-HR

Whatever I do, I can't get Croatian keyboard to work. It's important because it has letters in different positions. Where should I configure that, somewhere in scripts, perhaps, but I don't see where...?

I've found a way to change it manually, but I want it to build with a command. Can you help me with that? I've found what my input locale is:

InputLocale=041a:0000041a

But where do I enter that? Could you make a change in building scripts to make default system locale user's choice, if not setup, would make default en-US?

EDIT: the reasons I ask you these thinks is your announcement that you will work more on WIE since you can't get shims for linux approved for secure booting, and I think this would be excellent addition to great script you made for creating WIE.

Thank you.

@itisljar

To reply to myself, the problem was this:

set ComServerURL=http://10.1.36.30/

It NEEDS to have port set up, too. It should look like this:

set ComServerURL=http://10.1.36.30:8888/

Now just to learn how to set up HR keyboard, that would be grand anyone?
EDIT: I'm dumb. Configuration for keyboard is in CMD file for building WIE.

Here I am again!

I have another problem now: PXE booting works, system is setup to boot WIE image, and it boots, but then it reaches a stage where it stops and exclaims that the NIC doesn't have IP adress and that the driver could not be found.

When I enter "Display available NICs", I get two NICs displayed; first one is Microsoft Kernel Debug Network Adapter, and it has no address assigned. Second one is Realtek PCIe Gbe Familly Controller, I can see its mac address, IP address, it says that ipenabled is True and dhcpenabled is True. Yet it doesn't boot further from this point.

I have no experience with Windows PE whatsoever, I have general idea what it is, and I don't know what to do at this point. Images were build on my work computer and transferred to server. Same thing happens if I boot ISO off USB drive.

Also, there is line that says this:
Try Entering http://10.1.36.30/clientimaging/Test In A Web Browser
That is the IP adress which had to be entered into CMD file when starting building WIE images, right? But that link doesn't work without port 8888 after IP adress. Could that bie the problem, should I enter port with IP address?
That part in build CMD looks like this now:

set ComServerURL=http://10.1.36.30/

Should it be

set ComServerURL=http://10.1.36.30:8888/

?

Relevant pictures attached.

@theopenem_admin
Thank you. It works now.

OK, I will at monday, when on my work. Will there be any problems with creating boot images within web GUI?

Also, is there any tutorial about setting up WIE imaging environment? I've setup server up until checking that number that has to be 60, linux environment is already set up, just have to select proper boot images, but is WIE just creating winPE images, placing them into tftpboot folder and selecting them in server?

So, since we are using mostly Windows machines, I've started to set up another server with WIE only, but I have problems.
After installation of TOEMS and configuration by steps included, on fresh installation of Windows 10 22h2 64 bit, I've started Building windows environment. Followed the tutorial, enter all relevant information in cmd file, but build crashes at one point, for x86 images:

MakePE Version:  	20151014
===============================================================================
MakePE Directory Information:
	MakePE Directory:  	D:\wie_builder-2.0.1
	MakePE Builds:  	D:\wie_builder-2.0.1\Builds
	MakePE Components:  	
	MakePE Optional:  	D:\wie_builder-2.0.1\Optional
	MakePE Scripts:  	D:\wie_builder-2.0.1\Scripts
===============================================================================
AIK and ADK Installation Status:
	Windows 10 ADK:		C:\Program Files (x86)\Windows Kits\10
===============================================================================
WinPE Source Status:
	WinPE Version:  	10 
	WinPE Platform:  	x86
	WinPE Architecture:  	x86
	WinPE Language:  	en-us
	WinPE WIM:   		
	WinPE Type:  		
===============================================================================
WinPE Mount and Build Status:
	WIM Mount Directory:  	C:\Users\THEOPE~1\AppData\Local\Temp\
	WIM Temp:   		D:\wie_builder-2.0.1\Builds\TEMP WinPE 10 x86 .wim
	WIM BasePE:   		D:\wie_builder-2.0.1\Builds\tftpboot\boot\WinPE10x86.wim
===============================================================================
ISO Status:
	ISO Supporting Files:				D:\wie_builder-2.0.1\Builds\ISO-Support\Support
	ISO Source Directory:				D:\wie_builder-2.0.1\Builds\ISO-Support\WinPE10x86
	ISO Source WIM:					D:\wie_builder-2.0.1\Builds\tftpboot\boot\WinPE10x86.wim
	ISO Destination WIM:				D:\wie_builder-2.0.1\Builds\ISO-Support\WinPE10x86\Sources\Boot.wim
	ISO Destination (ISODestination):		D:\wie_builder-2.0.1\Builds\ISO\WinPE 10 x86 .iso
	ISO Label (ISOLabel):				WinPE 10 x86
	SuperISO Source Directory:			D:\wie_builder-2.0.1\Builds\SuperISO
	SuperISO Destination (SuperISODestination):	D:\wie_builder-2.0.1\Builds\ISO\WinPE SuperISO.iso
	SuperISO Label (SuperISOLabel):			WinPE SuperISO
===============================================================================
Windows Kit Status:
	Windows Kit:  		C:\Program Files (x86)\Windows Kits\10
	CABS:  			C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs
	dism.exe:  		C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe
	imagex.exe:  		C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\imagex.exe
	oscdimg.exe:  		D:\wie_builder-2.0.1\Builds\ISO-Support\Support\WinPE10x86\oscdimg.exe
	etfsboot.com:  		D:\wie_builder-2.0.1\Builds\ISO-Support\Support\WinPE10x86\etfsboot.com
	efisys.bin:  		D:\wie_builder-2.0.1\Builds\ISO-Support\Support\WinPE10x86\efisys.bin
===============================================================================
MakePE Options:
	TimeZone:		Eastern Standard Time
===============================================================================
WARNINGS:
Could not determine a WIM file to use 
===============================================================================

I'm left only with x64 images. Can't recreate boot files or anything because the files are missing, even after I transferred all files to that tftp boot folder, "merging" them.
What is wrong? I'm uploading screenshot, too.

It is not a problem reinstalling whole system if needed, as it is done in 15 minutes.

Hello!
On old CloneDeploy machine I had additional menu option for memtest; memtest was only one executable file, and I remember I had to ask on CloneDeploy forum for help, but that forum is now gone all I could remember is that I had to remove .bin form filename as grub (or something) treated bin files as something else.
Could you give us examples on how to do that, or if anyone knows, please, write here. I'd need memtest and disk checking (for example, badblocks command would be enough, smartctl would be preffered) so I need ISO booting.
Thank you all, and have happy holidays.

@itisljar OK, to reply to myself, I've disabled in BIOS every other boot device that pointed to HDD except Windows Boot Loader, and made image with that, and it works.
Will do that as workaround.

@theopenem_admin OK, I've updated the server, rebooted, and updated database through web interface, created the image but still there is problem.
Do I need to re-create boot files, too?

@theopenem_admin Thank you very much. Will upload tomorrow, and reupload these 3 images.
Thank you for being helpful.

@itisljar I just tried removing and re-adding the existing image, as I did when I migrated from CloneDeploy to OpenEm - the image size is seen in web interface, but "No Image Schema Found". Will try to put that whole image's folder to everyone-read... aaaand it didn't help at all.

Hello!
I have trouble with restoring image file. I will attach image upload and deploy logs. I've noticed it today, that in the web interface I don't see schema for that computer, I don't know if that's normal, I guess it isn't. Server version is 1.3.2.0.
Before I update server, I want to make sure what seems to be the problem, and if the update will solve the problem.
The error when restoring the image is this:
Unknown Error Occurred While Determining Minimum HD Size Required
I can take the image just OK, and I've checked if there is schema file on disk, it exists, but it isn't visible in web interface.
All logs attached.
Look for today's date, 29.6., it's the date when I took the image and tried to restore it afterwards. Computer is Dell Latitude 3500, UEFI, no secure boot. Booted through proxy on same machine which hosts server and DHCP on totally isolated network.

FrontEnd_toemsui.log e4_54_e8_1d_be_ef-unregupload.txt e4_54_e8_1d_be_ef-unregdeploy.txt ClientApi_toecapi.log Application_toemsapi.log

EDIT: I just tested it, it happened with three images I've done AFTER the upgrade to 1.3.2.0. But I can't say if this was the first one, because I usually restore the image immediately.