It's difficult to say. It really depends on how you are using the software, how many policies, size of packages, are you imaging?

With that many clients, I would have 2-3 com servers setup. CPU and memory typically aren't an issue. Any modern CPU and 16GB of ram should be fine.

I run 3 com servers, 1 internal(16GB), 1 external(4GB), and 1 dedicated for imaging for 1000 clients.

If it's for imaging, you need to use the imagingclient_powershell script option

@theopenem_admin
nope, the only thing I changed recently was the IP address they Com server was using. I went from the inside address to a port forwarded address.

@mikespears check log on client side : c:\program files\Toem\logs\service.log and you can place it here as well.

I went through of that these days so maybe can help.

check log sync time on client machine
-check if client isn't waiting for Approval Requests or Reset Requests (inside server GUI - Computers)

Tomas

WIW, I have the same situation, and the only thing that seemed to work for me was to make sure that all storage settings were set to local, on the main server, and secondary com servers, and to make sure upload/deploy direct to SMB was disabled. Works like a charm after that.

@theopenem_admin I got it working thank you for all your help!

@alext1024 well thanks for your input, now the problem is well resolved, Thank you.

@theopenem_admin

Yes secure boot disabled when generating usb booting key is ok now i see the status and kernel loading.
I ran into another problem, drive is encrypted, even if its not enabled on the client machine
So if it could help others:
I launched in CMD:

manage-bde -off C:

Also to see progress:

manage-bde -status C:

I will retry in a few minutes to upload image.
Still got the same error in com server log could not find the path, but hopefully its because of encrypted drive.
Thanks

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

Hmm, I never knew that setup complete would not run with an OEM license. I guess you would just need to change your policies a little to work with your setup.

Sorry, there is not

@theopenem_admin
The only nic I see listed is microsoft kernel debug adapter.
I downloaded the drivers off the manufacture site and extracted the inf from the files and placed it into the optional/drivers folder and re-ran the ToemsPE-build script and am still getting the same error.

There were some deadlocks. I tried to restart the service, it did not work. Restarted the server, did not work.
Lastly I backed up the db and reinstalled MariaDB. Seems to be working for now except for some connection issues..

You can't currently specify multiple ou's. You would need to leave it blank to sync the entire tree to get multiple ou's.

Just add the --help flag to get the options to run it or install it

It's only saving a text file. Doesn't matter what's in it. Only two reasons I've ever seen for this are permissions on the image folder and special characters in the name

@theopenem_admin

@theopenem_admin

On the client box, logged in with the credentials, clicked upload, typed in Win10-3 and received the same error. Log files are attached. I received this error.

63de5571-3a47-4722-8d6f-5eb6c4f28b59-Application.log
a73845f9-87f0-493e-8ab2-95b7ea6f20bc-ClientApi.log
Thank you Greg

@theopenem_admin ok I'll psot it there, I'll try to survive with unicast for now

Yea just put them in the drivers folder before you build, in inf format

Are you just testing this installation, or have you pushed it out to your computers. If you are just testing so far. I would regenerate your toems ca and and intermediate. Install the new certs on your server, regenerate Toec. Install Toec on a new machine. To rule all of those things out.