Adding a ZenImaging server to Advance boot options
-
Thank you both for your responses. I did try updating to the latest SVN but I recieve some MYSql errors when I do. So I just reverted back to the 1.2.0 release and I tried adding the chain loading to the advance menu which seemed to work:
menu
item --gap – ---------------- iPXE boot menu ----------------
item zenimaging zenimaging
item return return to previous menu
choose --default return --timeout 5000 target && goto ${target}:zenimaging
chain tftp://10.100.0.72/nvlnbp.sys ||
goto MENU:return
chain tftp://10.135.0.10/undionly.kpxe ||
prompt
goto MENUautoboot[/QUOTE]
and it boots to the zen server but then it hangs because it looks like its still looking at the wrong server:
[IMG]http://i61.tinypic.com/nf66nb.jpg[/IMG]
If you guys have any ideas that would be great thank you.
-
What sql errors did you get?
If it’s referring to keys not being found to be removed, they’re perfectly safe.
-
[quote=“causan805, post: 45379, member: 29341”]Thank you both for your responses. I did try updating to the latest SVN but I recieve some MYSql errors when I do. So I just reverted back to the 1.2.0 release and I tried adding the chain loading to the advance menu which seemed to work:
and it boots to the zen server but then it hangs because it looks like its still looking at the wrong server:
[IMG]http://i61.tinypic.com/nf66nb.jpg[/IMG]
If you guys have any ideas that would be great thank you.[/quote]
#bootmenu
just hash tagging this for my own personal use in the future.
Great that you got it going, mad props to Uncle Frank for helping!
And, Tom is right. The SQL errors when you update from something as old as 1.2.0 (yes, “old as”) are expected and safe. The queries that don’t execute are related to upgrading from much older versions of FOG.
-
it looks to me like the novel agent is expecting to find additional files where it’s loading [I][SIZE=12px]nvlnbp.sys [/SIZE][/I]from[SIZE=12px][I]. [/I][/SIZE]you might be best off setting your DHCP to serve out the original next-boot server the zen imaging server was using, but setting the boot-filename to undionly.kpxe. then move the undionly.kpxe and default.ipxe files to the original location of nvlnpb.sys
-
This post is deleted! -
I tried as you suggested Junk and now says it is sending queries to 10.100.0.72 which is correct but now it just hangs.
[IMG]http://i62.tinypic.com/2dmb4b5.jpg[/IMG]
Thanks for the help by the way.
-
for those of us who’ve never used zen imaging before, what’s supposed to come next?
-
It contacts the Novell Preboot Policy service. Then pressing the boot key sequence (Alt + Ctrl) takes you into the Zenworks Preboot Services menu.
[IMG]http://i61.tinypic.com/2irvvrl.jpg[/IMG][IMG]http://i58.tinypic.com/1pcku9.png[/IMG]
There might be a way to have the FogServer as a option here but I rather have Fog being the default pxe booting option.
Here is a link to the ZENworks documentation:
[url]https://www.novell.com/documentation/zenworks11/zen11_cm_preboot_imaging/data/bg4g38s.html[/url] -
After the chainload to [FONT=Consolas]tftp://10.100.0.72/nvlbnp.sys[/FONT]
Is there any way to re-assign via code the correct Boot Server Host Name options??
Perhaps just before the chainload, even? That’s the issue. -
[IMG]http://i57.tinypic.com/20jpdtz.jpg[/IMG]So I came across this in the wiki :
[URL=‘http://fogproject.org/wiki/index.php/Am_I_able_to_modify_the_PXE_menu_to_run_other_applications%3F’]http://fogproject.org/wiki/index.php/Am_I_able_to_modify_the_PXE_menu_to_run_other_applications?[/URL][FONT=sans-serif][COLOR=#000000]Which looks like a way to add zenworks imaging to the old menu. How would do this with the new advance menu?[/COLOR][/FONT]
