Latest Development FOG
-
@Bill Rice
The issue you’re seeing is because of the HostnameChanger.cs file in the fog client is not taking in consideration of the product key.
If you uninstall the client you installed from the SVN and use the installer from the 0.32, 1.0.0, 1.0.1, 1.1.0, 1.1.1, or 1.2.0 you should be fine. The one in SVN was a test build and it recompiled with an improper file. We’re rewriting the service which is why I have not reverted the file yet as it will be complete changed here shortly.
-
SVN 2454 released.
What this release brings is a more proper check to get the start sector of the image you’re trying to deploy.
Basically, 1.2.0 brought in the greatness that is linux resizable, but it made assumptions to the chunk size and start sector of the disk. It assumed all disks started at 2048. I found this out a while ago in reference to Vista/XP images, and made corrections for that, but it did not take in consideration a Windows 7/Windows 8 image that might, for some reason, start at sector 63. This broke these particular types of images.
This should now be corrected for in this release.
Further more, as there are a few changes, it also addresses some issues in the way the MAC’s are parsed. I May have to remove the tasking check in BootMenu.class.php but that’s because it should now be checked by the HostManager.class.php file.
I’m sure there may be better methods for this checking, but basically the method/function: getHostByMacAddresses had the potential to return multiple hosts if you use the ignore MAC stuff. Why? Well, let’s just use the USB nic example we’ve tried making a work around for.
Let’s say you have 10 USB nics, and those nic’s are only used to image systems that don’t have a built in nic besides wireless.
So you set the system to image and all goes fine, but when it completes, the image boots to the client and starts the FOG Service checks.
Under the “problem” we had, you may have put the WIFI address as a separate host so when it connected it would rename, join to domain, or what have you. So now, you potentially, have two nics on the same system trying to request information.
Where the problem lies is the getHostByMacAddresses function. It was getting both of the macs and returning both of the registered systems. The BootMenu system only cares about imaging tasks so it was able to work. Seeing as bootmenu can’t see the wireless nic, all is fine and the proper host is returned. But, once it booted to windows, it knows of both nics and passes it to the corresponding service files. The function was returning the error: Multiple Hosts with this mac address, which is correct. So to fix, I basically added checks in this field. If the Host that’s found is Valid and is in a tasking AND is Not imageIgnored, all is returned properly otherwise fail out as if the host doesn’t exist.
If the Host does not have a tasking, it then checks that the received MAC is not on the clientIgnored list. I’m starting to think all this jabber about it there may be potential issues in booting the host if there isn’t a tasking, but the client is rebooted. I’ll test as I believe I did make these checks too.
Thank you,
-
SVN 2455 released.
Properly fixes legacy resizable images but existing with the d1.original.partitions file.
While the fixes from above are correct, one of the methods I overlooked was checking for the sys.img.000 file. Basically if sys.img.000 existed, it preset the file information to what was assumed. This still happens, but only if the d1.original.partitions file does not exist, which really should only come from 0.32 (partimage) or I believe 1.1.2 and all between before the new resizable linux stuff was implemented.
-
ok updated to the latest and greatest
here is what the fog log shows now.
10/22/2014 6:47 AM FOG::HostnameChanger Module is active…
10/22/2014 6:47 AM FOG::HostnameChanger Index was outside the bounds of the array.
10/22/2014 6:47 AM FOG::HostnameChanger at FOG.HostNameChanger.changeHostName()
10/22/2014 6:47 AM FOG::GUIWatcher Message found, attempting to notify GUI!
10/22/2014 6:47 AM FOG::GUIWatcher The system cannot find message text for message number 0x%1 in the message file for %2
10/22/2014 6:47 AM FOG::GUIWatcher at System.Windows.Forms.Form.UpdateLayered()
at System.Windows.Forms.Form.set_Opacity(Double value)
at FOG.AbstractFOGService.attemptPushToGUI()
at FOG.GUIWatcher.startWatching()Tom, you recommend I switch back to the client updater for the 1.2 fog revision and use that?
or have you repaired this one and I should try to install the client updater for the newest revision? has that file changed as well? -
I have since utilized the service from release 1.20 and it seems to be working now as you suggested.
I hope that it will be fixed when the new release is done.
Thanks for your assistance and great work on a Farly superior software package for imaging. -
I have reverted the installer in svn for the fogservice.zip file to that of the 1.2.0 release file. This way anybody else that uses the svn to install shouldn’t continue having the problems.
-
SVN 2471 released.
With this release comes nothing in particular but a few edits. Mainly to some of the hooks for example reasons.
I’ll likely be editing the BootItem.hook.php to give more information as I’ve added the main variables to allow hooking into as well.
You can’t change the variables before they’re presented, but you can use these variables and edit them for the customization of menu items and the liking.
Basically what this will allow is you to edit all of the items the boot menu presents from a hook.
It also fixes an issue where the bandwidth graph was displaying all nodes regardless of if their graph is to be enabled or not.
-
Tom… since the Fog Client is being rewritten is there going to be a feature built in where the old Fog client will automatically be updated or will we physically have to go around to all the pcs and update to the new version of the client ?
-
The new FOG Service will not have built-in functionality to replace the old one due to the complexity. However, I should be able to create a snapin to do the upgrade processes for you. So all that would need to be done is deploy the Service-Upgrade snapin to all of your hosts.
-
Alright awesome. Sounds good to me.
-
Hey I don’t want to sound like a noob here but what is the easiest way for me to update my 1.2 fog to the new trunk version. I want to test UEFI imaging on my Dell Venu 11 tablets. They also use usb to Ethernet so im curious to see how that goes and to provide you guys with feedback.
-
[CODE]svn co https://svn.code.sf.net/p/freeghost/code/trunk /some/local/folder[/CODE]
Then navigate to the folder you specified and run:
[CODE]sudo /bin/./installfog.sh[/CODE]
-
Where can I find snap in’s to use with fog? this is an area I have wanted to utilize but have not had the time to investigate.
Thanks
Bill -
I did that but now I cant update my database. Where can I find config.php ? More then likely MySQL password needs to be entered.
-
Never mind I found it
-
So im running the latest 2472 and im trying to image a Dell Venu Pro 11 and im using the an EDI-Max EU-4208 usb to ethernet and not able to load PXE menu of fog. The docking station for it uses same chipset. Im guessing the drivers arent in the kernal. Can you please add it or is there a way i can manually do this. I have 150 of these to image. Bios is UEFI with Secure boot disabled and UEFI Network Stack enabled.
-
Tried to do an unofficial kernel and this is what i get guys on the update
FOGFTP: Failed to rename file. Remote Path: /var/www/fog/service/ipxe/backup/bzImage20141024_162312, Local Path: /var/www/fog/service/ipxe/bzImage, Error: ftp_rename(): Rename failed.
-
[quote=“Ray Zuchowski, post: 38203, member: 24449”]Hey I don’t want to sound like a noob here but what is the easiest way for me to update my 1.2 fog to the new trunk version. I want to test UEFI imaging on my Dell Venu 11 tablets. They also use usb to Ethernet so im curious to see how that goes and to provide you guys with feedback.[/quote]
Actually there is now a new articale in our wiki to show 3 different methods on installing the latest trunk. Give it a look.
[url]http://fogproject.org/wiki/index.php/Upgrade_to_trunk[/url] -
Thanks Wolfbane .
Thanks for fixing the kernel update guys in 2473. I tried the latest published kernals x86 and 64 for those Dell Venus and the latest unofficial as well with no success. If you can please add that into next unofficial kernel release.
The actual controller for these and the usb Ethernet adaptor are ASIX AX88772B Chipset. Thanks again. My school district will love you for this if you can add it.
Ray Z
-
The ASIX AX88772B’s are already built with the kernels.
Do you know between which two kernels problems started occurring?
