Worked great, thanks for the fast replies!
Posts made by Stealth111
RE: Imaging standard Image to EFI PC
When I change the option to Standard and then click on Update Deploy Options, I get a yellow warning message that states: When Using A Standard Partition Layout Only One Partition With The Operating System Can Be Active. And then it does not save the change.
Imaging standard Image to EFI PC
In your description you state that CloneDeploy can "Deploy EFI images to legacy computers and vice versa(Currently only Windows images)"
I love your program and everything you have provided to us! However, I have a small issue that I seem to be stumbling on. I have an image that we carefully made that will support about a dozen different systems (Windows 10 x64). I have not yet run into a system that doesn't work, until now. A new system we have had built is based on the new Gigabyte 310 series Motherboard, which is EFI ONLY. There is no legacy support at all. So here is where the challenge started. I wanted to use our image and try to image the new system with our old image, hoping it would work as described in your description as above. It took a bit of fiddling around, but I was able to get the solution to PXE boot this new system and actually image the PC with no errors to be seen. It is weird as when you first boot the PC before imaging and look in the bios, you don't even see the drive as an availbale boot device, you only see the UEFI PXE boot device. OK, no problem it seems, as after it EFI PXE Boots, CloneDeploy sees the drive and completes the process, however that is where the good times stop. After it completes the process and reboots, it just goes back to UEFI PXE boot sequence, and going into the bios still shows NO boot device other than network, so it seems like CloneDeploy is not somehow completing the process correctly. Am I missing a step somewhere? We DID take the machine afterwards and manually imaged it with CloneZilla via USB drives, and after it rebooted it DID show up as a boot device in the bios and proceeded to boot fine, so I know that it is capable of being imaged and can work, it just seems like maybe I am missing a step possibly to get it to image a standard image to an EFI system. Please let me know anything I can try!
RE: Not finding NetBoot after upgrade to 1.3.3
Just my 2 cents here, but try restarting the tftp service. I have had it flake out after doing windows updates or rebooting server. After the server rebooted the service showed "running", but it would not actually deliver the boot image. After I clicked on restart of the service, all was well again. This might not be the fix for your problem, but I had similar issue and wanted to throw it out there for you...
Best of luck!
RE: Multicast Options
When I select and define client count in the multicast to 3 for example, each client now DOES give me the "press enter to start" until it reaches the 3 threshold, and then it starts, The 3 clients start out very fast, then eventually crawl to a complete standstill (58.1%) and sit there for hours. Any ideas on things to try. Unicast works on the same machines at 10+ Gig/minute.
I still cannot get it to work when leaving the client count blank (none of them say "press a key to start")
I am looking for a way to make the default multicast group use 22.214.171.124 instead of the default of 126.96.36.199. How would I go about changing that? I have the exact same issue with On-Demand Multicasting as here: https://forum.clonedeploy.org/507-help-with-on-demand-multicast
I am not getting any type of prompt to start the multicast session on any of the clients, even though they are connecting and showing up in the console, they wont start, so I am assuming a network issue, and our old Ghost Solution was on 188.8.131.52
Edit, when I select and define client clount in the multicast to 3 for example, each client now DOES give me the "press enter to start" until it reaches the 3 threshold, and then it starts, but it wont work when leaving the client count blank......
Also, Is there a list of multicast arguments available?
RE: 1.3 Web UI login issue
So, clean install on Server 2016 (Fresh Install) went smooth as butter! I will say this, I LOVE CloneDeploy! WE were using a cobbled together Ghost based solution that was really pretty unique in what we could do with it, but it was suffering from not supporting newer hardware (HP G3+ and all the rest of their new unified bios systems to name a few), and deploying a 20 gig image was taking 15-20 minutes with a unicast and 40 minutes to multicast a lab. I can successfully deploy the same image to the same PC's in 2 minutes and 4 seconds! I am yet to try the multicast, but I am optimistic! I will say that there was a bit a figuring out to do to actually get up and started, even though I thoroughly went through the documentation. Small price to pay for such a sweet program. I really cannot say enough how much I appreciate the work you have put into this! After holiday break, I will be doing the rest of my needed testing. If all goes well, expect a well deserved donation to be heading your way! Happy Thanksgiving to everyone here!
RE: 1.3 Web UI login issue
Windows 10 (64bit), receiving the same error: Could Not Contact Token API, When going to http://10.0.0.14/clonedeploy, I cannot get http://localhost/clonedeploy to load, but IP does..
2017-11-18 13:50:52,936  ERROR CloneDeploy_ApiCalls.TokenApi Error With Token API: System.Xml.XmlException: '"' is an unexpected token. Expecting white space. Line 1, position 50.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.DtdParserProxy.System.Xml.IDtdParserAdapter.Throw(Exception e)
at System.Xml.DtdParser.ParseExternalId(Token idTokenType, Token declType, String& publicId, String& systemId)
at System.Xml.DtdParser.ParseInDocumentDtd(Boolean saveInternalSubset)
at System.Xml.DtdParser.Parse(Boolean saveInternalSubset)
at System.Xml.DtdParser.System.Xml.IDtdParser.ParseInternalDtd(IDtdParserAdapter adapter, Boolean saveInternalSubset)
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Parse(String text, LoadOptions options)
at RestSharp.Deserializers.XmlDeserializer.Deserialize[T](IRestResponse response)
at RestSharp.RestClient.Deserialize[T](IRestRequest request, IRestResponse raw)
I also get a different different error when going to http://10.0.0.14/clonedeploy/api/token
I get this:
Fresh install, tried 1.3.0 and also tried upgrading to 1.3.1
Tried 3 or 4 time to reinstall... Any ideas, please? I am dying to try this out!
Also just tried 1.3.2, same results.