@theopenem_admin You're right, I did shrink it before hand. I will recreate the image, thanks heaps!

@theopenem_admin Problem Resolved Thank you. AT least this is here now for others to see if needed!

@theopenem_admin
did it again even on a new machine.
I just don't get it to work

i try and is ok thank you for your reply

@theopenem_admin that's my fault, I just realized the deploy log is from before I re-uploaded the image and changed the name to win11. I did try the newer image (win11) and it was the same error. That's what I'm noticing also, it seems like its not finding the schema file. Updated deploy log: Deploy log.txt

I need the imaging logs. There is a specific upload and deploy log for that image.

No fix has been released yet.

In the toec api web.config change the log level from INFO to DEBUG

Can you post your com server multicast.log

@theopenem_admin Thought you might find this of interest. There is a tool called PsExec that can remotely call up gui applications via command line. Can be downloaded from https://learn.microsoft.com/en-us/sysinternals/downloads/psexec. Below are some examples:

psexec \\computername -u domain\username -p password -i 1 -d notepad psexec \\computername -u username -p password -i 1 -d C:\Windows\System32\DisplaySwitch.exe 2

Perhaps this can be integrated into TOEMS?

@theopenem_admin

Is the com server test where you put in the http://10.129.128.33:8888/Provision/VerifyDb link and it returns "60"? I am getting "60" as the result.

It is possibly to make this with Secure Boot enabled?
Could you tell me what is the cause of this issue?
I can install another PCs with Secure Boot enabled and it works fine.

@theopenem_admin Was this added in a release? I'm running into the same problem. I'm unsure how to script a condition as well, where can I find that?

What does your Toec client service log say?

@theopenem_admin wow that worked like a charm!!! Thank you very much for your prompt response. You are amazing!!!!

@theopenem_admin
No Nothing but Windows 10.
I will check the Bios and see if something happened to the Boot Drives.
If not I can just reload the OS from the Download and start fresh.
The 5500 however appears to have just the 4 Partitions. I states that something is corrupt but no blocked. Was not sure what that was all about. That install has been my main Image for CloneDeploy for several months and works fine on that server. Any ideas, Should I run a chkdsk and make sure nothing is corrupt?

@theopenem_admin Ah, I must have mis-read the instructions. OK, it installed on the Theopenem server.

Looks good, you shouldn't need to worry about the client log files. They are capped at 10MB with a max of 2 files.

@theopenem_admin said in Fresh install and PXE not working:

I'm confused with your proxy settings. In your initial post you say you are using the proxy but your images show that you are not using proxy.

My apologize, I didn't try proxy, only tested PXE with vSphere UEFI boot. And it was working.

@theopenem_admin I was able to get this fixed, I needed to point to each of the different ARCH to their respective bootmgfw.efi once I did this the WIM images worked just as expected ! Thanks for all of the help and assistance !