Hello I am getting this same message 12 times, then it starts shrinking the Volumes.
Then I get a few more and then it starts to upload the volumes. Is this a setting or is it the way the Dell Laptop has its partitions built?
It eventually works but adds almost 5 minutes to the upload time.
Can you put this updated file in your toec-api\bin and toems-api\bin folder on all of your servers, it should ovewrite an existing file. I think this should fix the checkin issue, but I suspect if you try to pull reports for the processes it will still crash, I'll take care of that later.
The computer won't boot if you change this. You need to install Windows and create the image with it not set to RAID. I typically make all of my images on a VM and then I can leave all the computers not set to RAID. The other option is to use the Windows Imaging Environment which should work with RAID on.
@theopenem_admin Yeah, the IP is populated there. I was actually messing around and decided to put the IP into the multicast settings too and it starting working when I tested again.
Also another odd thing happened. It made records of the images I tried to create and since they were empty I just cleared them all out and deleted them from the images list in the web interface. After doing that, the next two times I tried to do an on demand upload it wouldn't give me the option to make a new image and just told me there were no images. Not sure what happened there but it worked on the 3rd try and I am now able to successfully upload and deploy. Barring any weird stability issues, its also possible it was weird input issues in my WMware box that I'm using for testing... sometimes the web console in vmware does strange things so maybe it hit enter twice instead of once bypassing the options for new or existing image
Perhaps your presence scared it into working for me? Sometimes IT work is a mystery haha. Anyways thanks for the ridiculously fast response. Still very confused why it started working though
To answer my own question, procedure is quite easy:
Download and unpack Toems Proxy DHCP 1.0.0
Set TOEM to work with ProxyDHCP, and setup what you would like to boot, which kind of image. Generate boot images.
In unpacked folder, edit config file and add IP adressess to reflect your installation.
TFTPD - in GUI for DHCP remove boot file, and under DHCP additional option enter number 60, then "PXEClient"; and restart the service.
ProxyDHCP starts with toems_dhcp_proxy.exe --debug to stay in command line. You can start it as service with some additional tools.
This is the screenshot of the multicast. I tried 2 PCs in this figure. When I start the second PC it supposedly automatically continue the same as in clone deploy since I only set my multicast count to 2. In the figure photo I need to press any key in order to continue, unfortunately when I did press any key only 1 PC starts and in every partition I have to attend to press the key. I hope I describe it correctly. I appreciate your time and effort on this issue. I really want to recommend this system to our university as part of our educational tool once I can proved all the features and advantage on this system. Thank you once again. @theopenem_admin ![alt text]( image url)