• There were a couple of issues and I’ve, seemingly, fixed them. Hope this helps you out.

    Please redownload and test with r930

    HostManager.class.php which does the update/insert for the hostname still was referencing hostOS which doesn’t exist.


  • As far as I can tell, the GUI side of this is working properly, but the client side may be having issues. I’ll test for sure, but I’m not certain how to rebuild the client.

  • Moderator

    Also, I’ve just reverted to fog 0.32 and the exact same VM booted and changed hostname as expected without issue.

  • Moderator

    Error in the log which got overwritten during troubleshooting, and none of the 4 VMs I was using would change their hostnames.

    If nobody else is experiencing the issue, then maybe it’s just a one off. I was only able to run a few tests.

    I can try to replicate it in a couple of days if needed. I have 0.33b saved in a snapshot.


  • Also, how is it that you know hostnamechanger isn’t working? It isn’t changing the hostname after image upload? it isn’t joining active directory?

    What exactly is letting you know hostname changer isn’t working?


  • I don’t know that compression choices could be set from GUI. The init.gz file performs the compression using pigz, but that doesn’t mean it couldn’t be using gzip or bzip compression, but I think that would be better suited on the client level from the fog script.

  • Moderator

    Hostname changer doesn’t seem to be working in 33b.

    Great work so far. things are looking great.

    While your doing reconfiguration… could you try to add compression choices to the GUI?


  • r928 out. Contains Plugins again. Sorry I didn’t know they even existed.


  • [quote=“Tom Elliott, post: 17763, member: 7271”]I don’t think so. PXE in it’s native form doesn’t do anything bios related, however, there are PXE based EFI configurations out there from some of the research I’ve looked into.[/quote]

    This seems very viable…no??

    [url]https://wiki.ubuntu.com/UEFI/PXE-netboot-install[/url]


  • I don’t think so. PXE in it’s native form doesn’t do anything bios related, however, there are PXE based EFI configurations out there from some of the research I’ve looked into.


  • [quote=“Tom Elliott, post: 17758, member: 7271”]As I’m relatively new and mainly been working on the GUI, I’ll try seeing if I can update my init.gz file to test around with EFI a little bit. The kernel’s that I’ve been building have already included support for EFI, so it may just be a matter of … finally … switching to partclone to get true UEFI support imaging. Again, I’m new so it may not work right away and may take a little bit more time, but I will try and keep trying until I get it for you all. I will, as per usual, request others to test out as well as all I’ve got is a VM that I can tell to use EFI for bootup.[/quote]

    Hey Tom

    That would be awesome… All new devices are being churned out with UEIF bios, and when they start becoming cheaper, then the ability to boot in non UEfi mode will diminish…

    Does this also mean that you would not be able to pxe boot anymore?


  • As I’m relatively new and mainly been working on the GUI, I’ll try seeing if I can update my init.gz file to test around with EFI a little bit. The kernel’s that I’ve been building have already included support for EFI, so it may just be a matter of … finally … switching to partclone to get true UEFI support imaging. Again, I’m new so it may not work right away and may take a little bit more time, but I will try and keep trying until I get it for you all. I will, as per usual, request others to test out as well as all I’ve got is a VM that I can tell to use EFI for bootup.


  • [quote=“Todd Holte, post: 17741, member: 141”]Did you convert the GPT Disk to MBR Disk? I used “AOMEI Partition Assistant Standard Edition 5.2” its free for private and commercial use. [url]http://www.disk-partition.com/download-home.html[/url][/quote]

    Hey Todd

    I actually resolved this issue today…

    I originally did convert the GPT disk to MBR disk, however, it was still giving me the same errors.

    The eventual setup that worked was the following:

    Boot into windows 7 install disk, and shit + f10 on the first screen before you start the install process, blow away the partitions etc and create a new one so that you can have a single partition windows 7 install.

    I then decided to use single disk, single partition to upload the image, thats when FOG told me that no partitions can be located. It turns out, there is a post on this forum (which I can no longer find for some reason) I found while googling the error message which led me to a free tool called fixpart (there is a windows version) that you download and run on the computer with the following steps:

    fixpart.exe 0:

    it then immediately told me that there were left over GPT signatures on the drive mixed in with the MBR and that it would take care of them if I pressed Y.

    After that, i committed the changes with “w”, it wrote the new MBR, I rebooted and presto… the image got taken up.

    after I deployed it back to another laptop, the image went down fine however fog complained that partition 2 to 5 were missing but wasnt bombing out with IO errors like before… it then said task completed and it rebooted into windows 7…

    so happy days!!


  • Did you convert the GPT Disk to MBR Disk? I used “AOMEI Partition Assistant Standard Edition 5.2” its free for private and commercial use. [url]http://www.disk-partition.com/download-home.html[/url]


  • Hey guys… sincerely appreciate the work, however, I must point out that prior to main release, fog 0.33 must be able to deal with UEFI bios… we have just purchase 100 HP650 laptops and they are junk… their bios has an option to go legacy mode, but its not real… after blowing away the original install, and fdisk to only get 1 partition windows 7 install, fog still uploads 3 partitions for some reason, on putting the image back, it says that it cannot find partition 3 4 and 5 and then bombs with IO errors…

    I truly believe fog needs UEFI compatibility for it to remain viable…


  • No worries, I will.

    LOL 😉


  • Ok, my bad. Since it was hosted on your own server, I thought it was isolated. Please ignore me, and simply go on ;))


  • I don’t know what you mean Gilou.

    I’ve been updating the main SVN for FOG for the last few weeks. My branch simply sync’s with the original branch.


  • Hi Tom,

    Maybe I haven’t read about that somewhere else, but though I’m really excited about some activity on FOG, I’m concerned by the fact this is a fork-ish way of dealing with things.

    What’s the status on the main FOG repository, and why not handle the work over there rather than on a separate SVN setup. This will in the long run make it hard to track evolutions, should there be any, of the original project. The more reasonnable approach here would be to get in touch with the current developpers, and have them include your patch, or give you access to the repository.

    I will nevertheless have a shot at your branch, because I need FOG to go further, especially on the partclone/W8 evolutions, but let us not make a fork of something that isn’t dead, or at least that doesn’t appear to be dead. Maybe it is, then, fix before going down a potentially painful path 😉

    Cheers


  • Will pull down and have a play. Tom ur a star. ;):)

368
Online

9.0k
Users

15.6k
Topics

145.0k
Posts