Adding a ZenImaging server to Advance boot options
-
Hello, currently at my workplace we use Zen Imaging over the network. I would like to introduce FogServer to this network but have the Zen Imaging server as another option to boot to. I was wondering if this is possible and if someone could point me in the right direction to get this started. Thank you very much.
-
!http://fogproject.org/wiki/index.php/Am_I_able_to_modify_the_PXE_menu_to_run_other_applications?
Which looks like a way to add zenworks imaging to the old menu. How would do this with the new advance menu?
-
After the chainload to tftp://10.100.0.72/nvlbnp.sys
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.
-
It contacts the Novell Preboot Policy service. Then pressing the boot key sequence (Alt + Ctrl) takes you into the Zenworks Preboot Services menu.
!https://www.novell.com/documentation/zenworks11/zen11_cm_preboot_imaging/data/bg4g38s.html
-
for those of us who’ve never used zen imaging before, what’s supposed to come next?
-
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.
Thanks for the help by the way.
-
This post is deleted!
-
it looks to me like the novel agent is expecting to find additional files where it’s loading [I]nvlnbp.sys [/I]from[I]. [/I]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
-
@causan805, post: 45379, member: 29341 said:
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:
If you guys have any ideas that would be great thank you.
#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.
-
What sql errors did you get?
If it’s referring to keys not being found to be removed, they’re perfectly safe.
-
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:
If you guys have any ideas that would be great thank you.
-
Yes, SVN is a great start as you can edit the menu within the web interface! But I doubt that the tutorials about ISO loading will work for you. I’d suggest looking into plain chainloading (http://ipxe.org/cmd/chain).
chain tftp://10.100.0.72/nvlbnp.sys
-
Well, firstly… I would suggest updating to trunk for this endeavor. The latest developmental revisions of FOG allow simple boot menu alteration. This functionality is built into the web interface.
Read about updating to trunk here: http://fogproject.org/wiki/index.php/SVN
Secondly, I’m not entirely sure about the process for what you want to do but, I think a really good starting place is looking through the forms for “Booting to ISO” and such, and following those. There are numerous threads here about it, all with different titles.
Basically,
You’ll need to add a menu item, and then point that item to 10.100.0.72 and nvlbnp.sys somehow.Here are some that I found to get you started:
http://fogproject.org/forum/threads/pxe-boot-menu.12377/#post-41921
http://fogproject.org/forum/threads/help-how-to-load-iso-with-http-ipxe.11935/#post-38574
http://fogproject.org/forum/threads/add-iso-to-fog-server.11608/#post-36287
http://ipxe.org/howto/winpe?sYou might even need to put that boot file in the web directory on the FOG server - I’m just guessing…
Maybe you’ll be able to point the menu item to the kernel/files that nvlbnp.sys actually calls…I might play around with the idea this weekend… I have no idea if it’ll work or not…
If you find anything else or make progress, let us know. Also, check back here from time to time, others may reply as well with maybe better help.
This really should be do-able though, from what I can tell.
-
66: Boot Server Host Name 10.100.0.72
67: Bootfile Name nvlnbp.sys
-
You’ll need to tell us about ZenImaging a little…
Where is the boot file located? The share path, exactly.
A better question, actually…
Look on your 2008 DHCP server, and under scope options, tell us what options 066 and 067 are set to.
-
We just have a standard MS sever 2008 handling DHCP. No proxyDHCP that I know of.
-
What is your DHCP setup currently? Are you using any sort of ProxyDHCP at all?
