Latest FOG 0.33b
-
r1254 should fix many of the issues reported.
Specifically:
3, 6 and the error thrown. it’s based on Location. I forgot to add checking if the plugin was enabled or not. If it is, it actually matches the location if all hosts in the group match. -
Items 1 and 2 weren’t necessarily an issue, just an oversight that’s relatively simple to fix.
Haven’t fixed #4 yet is it’s more complex logic, so I just added all snapins in the system. If they aren’t associated with the host, they won’t deploy to the host.
Item number 5 is more of an issue due to the login, nothing that I can fix right now. Item number 7 once again just the same as item number 5.
Haven’t worked on 8 yet, will work now.
-
r1255 released.
Fixes item #8, please let me know if there’s any more issues. Thank you for the detailed report.
-
r1256 released.
Fixes an issue in the TaskManagementPage.class.php where The taskType wasn’t returning properly.
Fixes the Wakeup icon to show up properly. Still needs edit’s though.
-
r1257 released.
Fixes the TaskManagementPage scheduled tasks stuff. Can delete scheduled tasks now, and they display more appropriate.
-
Tom, have updated to 1257 and now I am unable to deploy or register new hosts
-
Can you provide error logs by chance?
I just tested registration and deployment and all works well on my end.
-
client screen says, during host reg: Fatal: INT18: BOOT FAILURE
and deploy says unable to find fog/kernel/bzimage
-
I will uninstall fog and I will reinstall
-
AHHH NO
-
Change the fog settings
It can’t find service/ipxe/fog/kernel/bzImage
-
You have to change the kernel, memtest, and bzimage in the fog settings to only point to memtest, init.gz, memtest, not fog/memtest/memtest, fog/images/init.gz, fog/kernel/bzImage
-
This post is deleted! -
all sorted
-
I was doing some more testing on snapins this AM and noticed a few things.
I am still having an issue with group deploy of all snapins. It states Snapins Are already deployed to this host. If I deploy the snapin another way successfully then try it again it creates the task.
I tried to do a quick deploy of snapins to a group and it didn’t create the snapin task. The single snapin didn’t have an option to select which one.
A quick deploy of all snapins for a host worked fine, but the quick deploy of single snapin did all snapins.
I tried group single deploy and it had the drop down which successfully worked.
I cancelled single deploy and all deploy active task for both host and group deploy which also removed the snapin task. It wasn’t working before. Also was able to cancel a single snapin from a deploy all snapins with out issue.
-
Sorry if I don’t get to Snapins at the moment. Currently bug tracking Windows 8 deployment to a machine. I believe I got it working. Now to just fix the UEFI crap!
-
Just done a one off speed test deploying on r1257 against 1249.
an 8gb W7 single partition image, went from 3 mins 43 to 3 mins exactly.
On a sample of one, the NFS tweaks look to be worthwhile. -
Yessir!
-
Just so all are informed. I was able to get an EFI Windows 8 system to upload an image, which was to be expected. All that worked perfectly. I was also able to deploy the Windows 8, and later boot it back up, from EFI (after disabling Secure boot). Sounds like success right? Well, I was very excited and all initially. However, I have yet to replicate the results. I can only do the deploy once, but nothing after that. It appears (just in case anyone else wanted to give a go as my mind is currently fried.) that the 1st partition (300MB ntfs) overwrites the GPT data structures and damages it. It can’t find the 2nd, 3rd, or 4th partitions (on a base install MPS image).
I think I can fix it but will have to wait until tomorrow. I suspect that Windows 8 is using a Hybrid-Protective MBR style GPT system that I need to actually, on upload, create an MBR backup as well as a GPT Backup. On deploy, write the GPT Backup, then the MBR. It’s just a theory, so no guarantees yet. Just wanted to give a status update.
-
[quote=“wolfemi, post: 23540, member: 5740”]I was doing some more testing on snapins this AM and noticed a few things.
I am still having an issue with group deploy of all snapins. It states Snapins Are already deployed to this host. If I deploy the snapin another way successfully then try it again it creates the task.[/quote]
I think this is sort of expected. The checks on the snapin/task generation basically check if a job is already created with the particular task (or job) and will not “re-deploy” until those previous snapins complete. Why you’re able to generate successfully, and then create the task is a little odd. Do you mean they deploy and complete, or you just create the task, then go to group and create?
[quote=“wolfemi, post: 23540, member: 5740”]
I tried to do a quick deploy of snapins to a group and it didn’t create the snapin task. The single snapin didn’t have an option to select which one.[/quote]
I can quick deploy the snapins to a group, but I don’t remember if I added the “checking” needed to send the snapins through this method. It’s not high priority as I finally got a Windows 8 system to play with. This is a relatively easy thing to “fix”/implement, just didn’t get to it yet.
[quote=“wolfemi, post: 23540, member: 5740”]
A quick deploy of all snapins for a host worked fine, but the quick deploy of single snapin did all snapins.
[/quote] See one above. I never implemented it, yet, on the task management page as I basically recreated the deploy scripts.
[quote=“wolfemi, post: 23540, member: 5740”]
I tried group single deploy and it had the drop down which successfully worked.[/quote] Expected!
[quote=“wolfemi, post: 23540, member: 5740”]
I cancelled single deploy and all deploy active task for both host and group deploy which also removed the snapin task. It wasn’t working before. Also was able to cancel a single snapin from a deploy all snapins with out issue.[/quote]
Expected.Thank you!
