Debian 8, Fog trunk, PXELinux on MS Server and MS DHCP help

[george1421]

@FlowLive

Then take the wim file from MDT and move it to the ISO folder and rename it boot.wim. Then just follow the option 2 instructions. If you want to replicate what I’ve done here install MS waik and build this directory structure. None of this code belongs to me or my company.

[FlowLive]

@george1421
Yes but if I put it in the ISO folder it would be the one from the .iso as well, I would end up having the same boot prompts as if I was booting off the disc. Or can I take some files from MDT, like the bcd file and boot.sdi?

Just to clarify, i don’t know if it’s the new Debian settings or Fog that changed it but I do see DocumentRoot to be /var/www/html/ found this in /etc/apache2/available-sites/000-default.conf and 001-fog.conf files.

I’m trying to download the files but i guess dropbox is blocked over here, thanks anyways!

I did create the structure using WAIK, I will try to get this to boot see if it’s any different.

[FlowLive]

@george1421
“Then copied the LiteTouchPE_x86.wim from MDT deployment share to /var/www/html/ISO as boot.wim.”

There is already a boot.wim file in /var/www/html/ISO/boot/, you keep both of em or you made an error on the destination?

[george1421]

@FlowLive Sorry I got tied up in meetings this AM.

You want to copy that tar file to where your web root is. That is either /var/www or /var/www/html depending on your distribution. In the case of this tar file it creates an upper case folder called ISO when you run the tar -zxf command to extract the file.

When you get done, there should be wimboot in the http servers root directory and a folder called ISO. The LiteTouchPE_x86.wim comes from MDT and it needs to be copied into the ISO folder as boot.wim. That file does not go into the boot folder it self just into the /ISO folder as I defined in the option settings.

[FlowLive]

@george1421
Got it, like I said dropbox is blocked but I managed to get that ISO folder on there, Along with 2 different .wim files for English and French versions of windows and just need to call it properly in the settings, all is good!"

If the boot.wim is called differently, it would be called like this;

Parameters:
kernel http://<fog_server_ip>/wimboot
initrd http://<fog_server_ip>/ISO/boot/bcd BCD
initrd http://<fog_server_ip>/ISO/boot/boot.sdi boot.sdi
initrd -n boot.wim http://<fog_server_ip>/ISO/LiteTouchPE_x64.wim boot.wim
boot

I guess it calls boot.wim to load LiteTouchPE_x64.wim? Or whatever the .wim file is called…

Really happy with this, thanks george1421!

[george1421]

@FlowLive I know it works when you call the boot.wim boot.wim. In theory it should work that way too, because you are using a logical name (boot.wim) to the physical name mapping.

Just be aware there are a bunch of other files in that ISO directory structure you need. That is why I created the tar file. I’m sorry I didn’t think about it being blocked across the pond. But if you have WAIK then you have everything I have.

Let us know how it goes (good or bad [I expect good things only]).

[FlowLive]

@george1421
It works! Both solutions works!
I’m now playing around with adding entry in the menu, having some that tries a command with the description or item name… weird but naming it differently seems to work for now.

[Wayne Workman]

@george1421 Can we get a more formal post of both solutions for the WiKi?

[george1421]

@FlowLive Hey that’s great to hear that someone can repeat my madness…

@Wayne-Workman Le me see if I can clean it up a bit. I need to see if I can integrate what @Sebastian-Roth noted in this thread about using a logical to represent the fog server IP. I think I can make it work.