Posts made by aaron

@theopenem_admin thanks for confirming.

Will have to look at the TOEC side at a later date. Will remove the agent and use just as image tool for now.

@theopenem_admin this might be the issue (limited to 20) - as thought wasn't using SMB the 20 limit didn't apply and i thought the check-in would be more staggered.

Only error I have seen is this showing in Toems UI/API

2021-02-03 14:17:26,976 [33] ERROR Toems_ApiCalls.ApiRequest Response Data Was Null For Resource: FileSystem/GetSMBFreeSpace/
2021-02-03 14:33:21,584 [67] ERROR Toems_ApiCalls.ApiRequest Response Data Was Null For Resource: FileSystem/GetSMBFreeSpace/
2021-02-03 14:35:01,921 [79] ERROR Toems_ApiCalls.ApiRequest Response Data Was Null For Resource: FileSystem/GetSMBFreeSpace/
2021-02-03 14:37:32,741 [83] ERROR Toems_ApiCalls.ApiRequest Response Data Was Null For Resource: FileSystem/GetSMBFreeSpace/
2021-02-03 14:49:50,577 [23] ERROR Toems_ApiCalls.ApiRequest Response Data Was Null For Resource: FileSystem/GetSMBFreeSpace/
2021-02-03 15:00:34,513 [77] ERROR Toems_ApiCalls.ApiRequest Response Data Was Null For Resource: FileSystem/GetSMBFreeSpace/

@theopenem_admin just win10 pro

Hi,

Have a freshly built server and all appears working with imaging as well as TOEC deployment.

However seem to have intermittent issue with theopenem webpage hanging and becoming unresponsive.

I am also not currently seeing any devices looking for approval that I would be expecting.

After several minutes the page often loads again but not always. a reboot would "cure" it.

Any ideas on what could be causing this?

Hi,

Would be really useful when looking at the list of groups it also shows how many members are in that group.

Hi all,

Have made some good progress on a second run using a Windows10 Desktop. Was able to test and confirm working USB booted Image, Legacy PXE and attempted to remove the Console/Web task password prompt.

Since then I am no longer able to PXE either legacy or UEFI as get the following error

"could not download script, response code 403"

I have done the usual applying of PXE and boot menu as we usually do with Crucible/CD whenever a change is made.

I had changed the admin password also as per the documentation.

Thanks,

Have tried that and took a clone, but after cloning (To CloneDeploy) I see no attempt to seek approval.

Will be deploying 1 final image using CloneDeploy to bring the systems into TOEMS.

Building TOEC Agent into Image I have yet to get it working.

Is it literally using;

Toec.exe --prepareImage [SERVER_KEY] [CA_THUMBPRINT]

or do I enter the codes from the server? I have tried both but the device didnt request approval.

I came accross this which looks like same issue.

https://superuser.com/questions/1580490/pxe-boot-tftp-file-transfer-fails

Further testing with opening ports has not made any improvement.

I have tried to EFI PXE from 1 of each device and i get different errors.

1 Device Model times out (Timeout Waiting for ACK Block) the second throws an error in TFTP advising "PEER RETURS ERROR <USER ABORTED TRANSFER>

i tested all EFI pxe options in TOEMS but all get stuck same way at 0% of getting the pxeboot.0 file

@theopenem_admin yeah,

These are out-of-box and the TOEC will be ran via script after the image to onboard them.

Thanks for letting me know.

@theopenem_admin

So the only way is to Add manually via PXE menu?

Hi,

Is it possible to import all my computers from the Export.csv of CloneDeploy into TOEMS?

Unable to see option in UI.

@theopenem_admin I tested the USB method which worked fine, so at least that is something. I had to restore FW settings and may have now lost the rules created during install.

Is there a list of ports I can open up or a way I can reapply the FW changes applied during install?

@theopenem_admin

Ill revisit the testing and see what happens.

Same error in TFPT Log.

but on screen Legacy PXE using Legacy BootFile I am getting.

This is a system that does Legacy PXE without fault using CloneDeploy currently.

PXE-T00 Undefined error code
PXE-E36 Error received from TFTP server

Willing to look at USB option depending on time it will take to deploy using that method, but as a last resort due to volumes and once proven TOEMS is working on our box.

Guessing it still pulls image over the network just not via the PXE method but using a small OS on the stick?

@theopenem_admin

I understand, i was just testing both.

As so far I've yet to have Legacy or UFI load a boot menu at all with TOEMS.

@aaron tried the same in UFI on the device that usually supports legacy and same as above , time out.

@theopenem_admin it does this on any system. systems which do image using clonedeploy (using legacy)

if i try and use legacy to reach UFI boot menu i get a different error saying the file is too large. which was mentioned in your video.

I think behind the scenes this is hanging at the TFTP stage (which you cant see in UFI but can in legacy)

EDIT, Logs from a legacy PXE attempt

Connection received from 10.108.160.6 on port 2070 [28/01 14:11:49.479]
Read request for file <pxeboot.0>. Mode octet [28/01 14:11:49.479]
OACK: <tsize=882048,> [28/01 14:11:49.479]
Using local port 53785 [28/01 14:11:49.479]
Connection received from 10.108.160.6 on port 2071 [28/01 14:11:51.510]
Read request for file <pxeboot.0>. Mode octet [28/01 14:11:51.510]
OACK: <tsize=882048,> [28/01 14:11:51.510]
Using local port 53786 [28/01 14:11:51.510]
Connection received from 10.108.160.6 on port 2072 [28/01 14:11:55.516]
Read request for file <pxeboot.0>. Mode octet [28/01 14:11:55.516]
OACK: <tsize=882048,> [28/01 14:11:55.516]
Using local port 53787 [28/01 14:11:55.516]
Connection received from 10.108.160.6 on port 2073 [28/01 14:12:01.516]
Read request for file <pxeboot.0>. Mode octet [28/01 14:12:01.516]
OACK: <tsize=882048,> [28/01 14:12:01.516]
Using local port 53788 [28/01 14:12:01.516]
TIMEOUT waiting for Ack block #0  [28/01 14:12:04.563]
TIMEOUT waiting for Ack block #0  [28/01 14:12:06.594]
TIMEOUT waiting for Ack block #0  [28/01 14:12:10.609]

@theopenem_admin pxe_fail_log.txt