@theopenem_admin Where is it located?

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

It's not required, just an easy way to run some extra commands after the computer boots the first time. It wouldn't change your issue since you aren't getting that far.

@theopenem_admin Excellent. Thank you again for your response and assistance!

@cycy Thank you very much

@theopenem_admin after "only upload schema" check and "update profile"
"only upload schema" unchecked automatically and upload all partitions images ( not schema only) upload from client ,not from server

All you need is a Windows server in AWS and it will work fine. If you plan to deploy and upload images, you will need an additional server on a local network to upload images, they can be deployed anywhere.

Could be a driver issue, I would try adding that specific nic driver to your winpe image.

I had similar issue in the past - if the "5K" on the screeshot is the size of your toec client installer, it means it was not built properly server-side. It should be over 5 Megs in size.
Check your Admin Settings -> Toec screen and see 'Client MSI Arguments'. Does it have value for all the arguments (SERVER_KEY, CA_THUMBPRINT, COM_SERVERS)? Mine was having empty SERVER_KEY due to having wrong dbencryption key in web.config.
Application log was saying "ERROR Toems_Service.EncryptionServices Could Not Decrypt Password. Ensure Your Encryption Key is Correct."
Once I've put the correct dbencryption key, the toec client installer started builing correctly.

Nevermind. I didn't read the test instructions carefully enough. I missed the port number.

Script module runs as the system account, there wouldn't be a %username% variable because no user is logged in.