@paddymccdrc

Bit of an unusual request but how do we use Theopenem for imaging devices that have both Emmc and NVME drives?

We cannot disable or remove the Emmc in the BIOS and its the default option that Theopenem tries to image to but they are only 16GB in capacity.

The drives are:

/dev/mmcblk0
/dev/nvme0n1

They are a Dell Wyse 5470 laptop.

Ive successfully got Theopenem up and running and managed to image a few test machines via legacy and UEFI BIOS's but i need to build Theopenem with a proxy DHCP service so i can do both instead of having to switch in the web interface.

Ive managed to get the Toems Proxy DHCP working and serving both types of BIOS successfully but it requires an extra machine running.

Is there a way to setup a virtual machine inside the same server where Theopenem is running and run the Toems Proxy DHCP inside said virtual machine?

My setup is a flat network with 1 x Windows Server 2019 running Theopenem and clients connecting via a gigabit switch for ondemand imaging.

To follow this up.....

For anyone else that has this error please do not put the port address in with the upload interface IP.

It should be set to the IP without Port address so in my instance it would be

192.168.56.100

It should not be 192.168.56.100:8888

Im getting the following error when trying to upload an on-demand image to the server that i've just setup to test things.

The client computer goes through preparing the drive then gets to

preparing client com imaging server for upload
An error has occurred
...... could not start server image receiver

When i look in my Com Server ive set the correct Upload Interface IP which is set to:

192.168.56.100:8888

Any help would be appreciated as ive tried reinstalling this a few times and i keep hitting this brickwall. Here is the imaging log:

Setting webPath to http://192.168.56.100:8888/clientimaging/

System Model: Satellite Pro ET10-G-104

** Looking For Active Task For 0c:37:96:7c:5f:ff.90241804G.358cd25e-f80a-11ea-82bb-a8937c7f9000 **

{"computerId":"false","task":"ond","taskId":null,"computerName":null}

...... This Computer Was Not Found

** Looking For Model Match Task For Satellite Pro ET10-G-104 **

{"imageProfileId":null,"imageName":null,"imageProfileName":null}

System Model: Satellite Pro ET10-G-104

** Looking For Active Task For 0c:37:96:7c:5f:ff **

{"computerId":"false","task":"ond","taskId":null,"computerName":null}

...... This Computer Was Not Found

** Looking For Model Match Task For Satellite Pro ET10-G-104 **

{"imageProfileId":null,"imageName":null,"imageProfileName":null}

This Computer Is Not Registered. No Active Web Tasks Were Found For This Computer. Starting Registration.

** Displaying Boot Arguments **

IpxeBoot initrd=initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web="http://192.168.56.100:8888/clientimaging/" USER_TOKEN=BEA140605DFD483DB9A04096FC5C66A5 consoleblank=0 MAC: 0c:37:96:7c:5f:ff
Linux client_console 5.17.3 #1 SMP PREEMPT Thu Apr 14 12:41:19 EDT 2022 x86_64 GNU/Linux

Boot Image Version: 1.5.0

** Using On Demand Mode **

** Creating Active Task **

image_name=test1 profile_id=4 pre_scripts="" before_file_scripts="" after_file_scripts="" file_copy=False sysprep_tags="" image_type=Block set_bootmgr=True web_cancel=true task_completed_action="Reboot" compression_algorithm=lz4 compression_level=-1 image_server="http://192.168.56.100:8888/clientimaging/" upload_server="192.168.56.100:8888" computer_id=-187421

...... Success

** Checking Current Queue **

...... Complete

** Verifying Image Server **

...... Success

** Looking For Hard Drive(s) **

...... Displaying Available Devices
RO RA SSZ BSZ StartSec Size Device
rw 256 512 512 0 159744000 /dev/ram0
rw 256 512 512 0 31037849600 /dev/mmcblk0
rw 256 512 512 2048 104857600 /dev/mmcblk0p1
rw 256 512 512 206848 16777216 /dev/mmcblk0p2
rw 256 512 512 239616 30102519808 /dev/mmcblk0p3
rw 256 512 512 59033600 810549248 /dev/mmcblk0p4
ro 256 512 512 0 4194304 /dev/mmcblk0boot0
ro 256 512 512 0 4194304 /dev/mmcblk0boot1
Disk /dev/ram0: 152.35 MiB, 159744000 bytes, 312000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mmcblk0: 28.93 GiB, 31037849600 bytes, 60620800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A8C7A0DC-E245-4F3C-9F58-3AC71847739E

Device Start End Sectors Size Type
/dev/mmcblk0p1 2048 206847 204800 100M EFI System
/dev/mmcblk0p2 206848 239615 32768 16M Microsoft reserved
/dev/mmcblk0p3 239616 59033599 58793984 28G Microsoft basic data
/dev/mmcblk0p4 59033600 60616703 1583104 773M Windows recovery environment

Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

all_hard_drives: /dev/mmcblk0

disk_label: gpt /dev/mmcblk0

partitions: /dev/mmcblk0boot0
/dev/mmcblk0boot1
/dev/mmcblk0p1
/dev/mmcblk0p2
/dev/mmcblk0p3
/dev/mmcblk0p4

...... Found Drive(s)

...... Drive(s): /dev/mmcblk0

** Removing All Files For Existing Image: test1 **

** Creating Image Schema **
The protective MBR's 0xEE partition is oversized! Auto-repairing.

The protective MBR's 0xEE partition is oversized! Auto-repairing.

The protective MBR's 0xEE partition is oversized! Auto-repairing.

Current NVRAM Entries
BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0004,0005,0006,0007,0003,0000
Boot0000 Windows Boot Manager HD(1,GPT,98db197f-c136-4ea1-8286-f278662e70a9,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...1................
Boot0003* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0004* UEFI: USB Network Card PciRoot(0x0)/Pci(0x15,0x0)/USB(11,0)/MAC(0c37967c5fff,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()..BO
Boot0005* UEFI: USB Network Card PciRoot(0x0)/Pci(0x15,0x0)/USB(11,0)/MAC(0c37967c5fff,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006* UEFI: USB Network Card PciRoot(0x0)/Pci(0x15,0x0)/USB(11,0)/MAC(0c37967c5fff,0)/IPv6([::]:<->[::]:,0,0)/Uri()..BO
Boot0007* UEFI: USB Network Card PciRoot(0x0)/Pci(0x15,0x0)/USB(11,0)/MAC(0c37967c5fff,0)/IPv6([::]:<->[::]:,0,0)..BO
The protective MBR's 0xEE partition is oversized! Auto-repairing.

Calculating volume size for /dev/mmcblk0p1
Partclone v0.2.90 http://partclone.org
Starting to clone device (/dev/mmcblk0p1) to image (/dev/null)
Reading Super Block
we need memory: 30276 bytes
image head 4160, bitmap 25600, crc 516 bytes
Calculating bitmap... Please wait...
used_size:29
volume_size:106

Partition Volume Size
volume_size:106

Partition Used Size
used_size:29
The protective MBR's 0xEE partition is oversized! Auto-repairing.

Calculating volume size for /dev/mmcblk0p2
Partclone v0.2.90 http://partclone.org
Starting to clone device (/dev/mmcblk0p2) to image (/dev/null)
Reading Super Block
get device size 16777216 by ioctl BLKGETSIZE64,
we need memory: 8772 bytes
image head 4160, bitmap 4096, crc 516 bytes
Calculating bitmap... Please wait...
used_size:17
volume_size:17

Partition Volume Size
volume_size:17

Partition Used Size
used_size:17
The protective MBR's 0xEE partition is oversized! Auto-repairing.

...... Shrinking NTFS Volume On /dev/mmcblk0p3 (This May Take A Few Minutes)
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
NTFS partition /dev/mmcblk0p3 was processed successfully.
ntfsresize v2020.4.13 (libntfs-3g)
Device name : /dev/mmcblk0p3
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 30092030464 bytes (30093 MB)
Current device size: 30102519808 bytes (30103 MB)
New volume size : 17637999104 bytes (17638 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 17125 MB (56.9%)
Collecting resizing constraints ...
Needed relocations : 0 (0 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/mmcblk0p3'.
You can go on to shrink the device for example with Linux fdisk.
IMPORTANT: When recreating the partition, make sure that you

1. create it at the same disk sector (use sector as the unit!)
2. create it with the same partition type (usually 7, HPFS/NTFS)
3. do not make it smaller than the new NTFS filesystem size
4. set the bootable flag for the partition if it existed before
   Otherwise you won't be able to access NTFS or can't boot from the disk!
   If you make a mistake and don't have a partition table backup then you
   can recover the partition table by TestDisk or Parted's rescue mode.

...... Success

...... ntfssize:
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... FIXED
NTFS volume version is 3.1.
Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
NTFS partition /dev/mmcblk0p3 was processed successfully.

Calculating volume size for /dev/mmcblk0p3
Partclone v0.2.90 http://partclone.org
Starting to clone device (/dev/mmcblk0p3) to image (/dev/null)
Reading Super Block
we need memory: 546532 bytes
image head 4160, bitmap 538272, crc 4100 bytes
Calculating bitmap... Please wait...
used_size:17146
volume_size:17656

Partition Volume Size
volume_size:17656

Partition Used Size
used_size:17146
The protective MBR's 0xEE partition is oversized! Auto-repairing.

Calculating volume size for /dev/mmcblk0p4
Partclone v0.2.90 http://partclone.org
Starting to clone device (/dev/mmcblk0p4) to image (/dev/null)
Reading Super Block
we need memory: 32996 bytes
image head 4160, bitmap 24736, crc 4100 bytes
Calculating bitmap... Please wait...
used_size:718
volume_size:812

Partition Volume Size
volume_size:812

Partition Used Size
used_size:718

...... image_schema: {"harddrives": [ {"name":"/dev/mmcblk0","size":"60620800","table":"gpt","boot":"","lbs":"512","pbs":"512","guid":"A8C7A0DC-E245-4F3C-9F58-3AC71847739E","active":"true","partitions": [ {"number":"1","start":"2048","end":"206847","size":"204800","volumesize":"101","type":"","usedmb":"27","fsType":"vfat","fsid":"EF00","uuid":"E8A2-72D4","guid":"98DB197F-C136-4EA1-8286-F278662E70A9","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"#\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI","volumegroup": { } },{"number":"2","start":"206848","end":"239615","size":"32768","volumesize":"16","type":"","usedmb":"16","fsType":"","fsid":"0C01","uuid":"","guid":"FEEA37A6-71A1-4932-A767-B1BF82C945F6","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"","volumegroup": { } },{"number":"3","start":"239616","end":"59033599","size":"58793984","volumesize":"16838","type":"","usedmb":"16351","fsType":"ntfs","fsid":"0700","uuid":"1866BA8266BA5FE4","guid":"33E597A0-C245-4055-AA72-FA9B2B2361F4","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"","volumegroup": { } },{"number":"4","start":"59033600","end":"60616703","size":"1583104","volumesize":"774","type":"","usedmb":"684","fsType":"ntfs","fsid":"2700","uuid":"4C6495A864959574","guid":"59B7988A-0403-4D76-81AD-D391BDF6F97C","active":"true","customsize":"","customsizeunit":"","forcefixedsize":"false","prefix":"p","efibootloader":"","volumegroup": { } }] }] }

...... Complete

** Checking For Partition Table Types Before Upload On /dev/mmcblk0 **
The protective MBR's 0xEE partition is oversized! Auto-repairing.

The protective MBR's 0xEE partition is oversized! Auto-repairing.

...... gpt_status: present mbr_status: protective

** Saving MBR / GPT On /dev/mmcblk0 **
The protective MBR's 0xEE partition is oversized! Auto-repairing.

...... drive: checkPartStart: 2048 toSave: 2047
2047+0 records in
2047+0 records out
1048064 bytes (1.0 MB, 1.0 MiB) copied, 0.0071436 s, 147 MB/s

...... Success

** Determining Partition Count On /dev/mmcblk0 **

...... Found 4 Partition(s)

** Starting Image Upload For /dev/mmcblk0p1 **

...... partition_number: 1 filesystem_type: vfat

** Preparing Client Com Imaging Server For Upload **

** An Error Has Occurred **

...... Could Not Start Server Image Receiver

** Expanding Shrunk Volume /dev/mmcblk0p3 **
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
NTFS partition /dev/mmcblk0p3 was processed successfully.

volumeMargin: 12464520704

** Expanding NTFS Volume on /dev/mmcblk0p3 **

Expanding NTFS Volume To: 30092034048
ntfsresize v2020.4.13 (libntfs-3g)
Device name : /dev/mmcblk0p3
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 17637999104 bytes (17638 MB)
Current device size: 30102519808 bytes (30103 MB)
New volume size : 30092030464 bytes (30093 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 17125 MB (97.1%)
Collecting resizing constraints ...
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/mmcblk0p3'.

...... Success
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... FIXED
NTFS volume version is 3.1.
Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
NTFS partition /dev/mmcblk0p3 was processed successfully.

Hopefully someone can point me in the correct direction but ive recently setup a 2019 Server and installed Theopenem and gone through the steps pointed out in the installation video.

However i've hit a brick wall....

When i try to install the 2 x certificates that ive generated and exported i get the following message:

Invalid Public Key Security Object File
This file is invalid for use as the following: Security Certificate