Posts made by KnightRaven

@KnightRaven So my bootable USB has wds files as well. So at least I know its the same setup info.

@george1421 Well I used the AIK/dism/imagex tools to modify or inject some drivers to the boot.wim. Just not the laptop I am testing. But the desktop does the same thing. I appreciate your assistance but don’t work to hard at it. This is just a test and see if I can get it done myself. nothing critical for the most part.

As I am looking in the sources directory I am seeing wds files. Not sure if that is normal or not. I may be remembering something wrong or maybe copied extra files from another spot. It was awhile ago when I first tried this then got on to assigned duties.
I may just recreate the files\setup when I get time this week.

thanks again.

@george1421 From bootable(and usable) USB boot. That came from our win7 ISO. So I am wondering now if that boot.wim is looking for a specific location?

@george1421 Thats kind of what I’m asking though. Does it have to be done in a script to work before the default setup pops up. Everything else is being done. I connect to a network share on my fog server and rerun setup.exe but it still gives me the cd/dvd driver error. I can’t find anywhere that still addresses why that may still pop up.

Ok, so I have seen several topics or threads on this. However, I still can not get past the spot of supposedly needing a driver or that windows install is missing the CD/DVD drive. I can wimboot just fine(or seems to) as I can get to the Install windows button. I can also get the NIC to work and map a drive back to the sources directory. However, when I run setup.exe from sources I still get that CD/DVD drive error that looks like a driver is missing.

My adv fog pxe wimboot script…

kernel http://${fog-ip}/fog/service/ipxe/Win7/wimboot pause gui
#initrd http://${fog-ip}/fog/service/ipxe/Win7/x32/bootmgr                    bootmgr
initrd http://${fog-ip}/fog/service/ipxe/Win7/x32/boot/bcd                    bcd
initrd http://${fog-ip}/fog/service/ipxe/Win7/x32/boot/boot.sdi             boot.sdi 
initrd http://${fog-ip}/fog/service/ipxe/Win7/x32/sources/boot.wim      boot.wim
imgstat || echo "ERROR at IMGSTAT"; sleep 3
prompt || echo "ERROR at PROMPT"; sleep 3
boot || echo "ERROR AT BOOT"; sleep 3;goto MENU

Since I found this script I modified it for my locations. the last 3 lines may or may not be doing anything useful but were left there. At least since it boots I don’t know that the echos and sleeps actually do anything.

When I get booted to the winpe setup I shift-f10 to get the cmd prompt.
On the laptop I use drvload to enable to NIC.
run wpeinit
Once I get an IP I map a drive back to sources.
cd as needed and run setup.exe
usually nothing happens. So I click through and get the error screen.
I rerun setup.exe and quickly close the initial setup.
New setup appears with same error results.

So, what is actually missing? Am i missing a step? Do the NIc drivers have to be loaded/injected into the boot.wim file? Or can they be loaded manually if needed and still should work? Also I can only get to the new setup.exe after clicking through the initial setup that pops up. Is that part of the problem? Do i have to automate it with a script? I have read not to click on that first setup but thats the only way to see the new setup screen. I know, it sounds confusing. I understand from looking into it that this stems from missing setup info/files. But I dont know what is missing. I made the boot.wim file following instructions using the dism/imagex tools from MS. I can try and re-make it(again) but the files work from a usb drive. Or at least that’s the reference I used. A working win 7 bootable usb install.

I am testing on DELL optiplex PCs and a dell mini laptop.
Fog using 1.2.0 on Linux mint 17.3(ubuntu version 14.x)
Fog runs OK
Trying Win 7 currently
Would like to add Win 10 but hear thats problematic for differenct reasons

I understand that this isn’t a fog issue or that it’s not what it was intended for. But if anyone can give some ideas or clues on whats going on(or not going on as it may be) that would be awesome and appreciated.

I’ll update with any needed info, however like many I come from windows. So you may have to help me with linux details.

It’s just frustrating to be so close and follow the info out there and still not work. And not know why.

Thanks,
Jason

@Wayne-Workman
Yes that article helped originally. I started trying fog a year ago but my original install quit working and I gave up. When I tried again a couple of months ago I was having problems with the next-server issue. What most docs seem to say is to change the DHCP settings. Well since I can’t change the actual school server and my fog box isn’t doing real dhcp I had trouble nailing down where to make the change. I found pages talking about the dhcp-option that I posted but it didn’t fix it in the ltsp.conf file. I finally tried to add the change to dnsmasq.conf and that’s when it started working. I’m not sure what the difference is or was.

And thanks for the replies. I wasn’t expecting much but to lend a few tidbits of knowledge. Wasn’t expecting a developer to reply. Very cool.

@Sebastian-Roth Thanks for the info. I was unaware of that problem. This month was the first time i tried using pxelinux.0 and it helped me debug. I will refrain or at least make aware that there could be problems using that method in future posts.

Just wanted to add my $.02 worth of info.
This may already be covered somewhere but I couldn’t find it. At least not where it makes it clear enough

My experience has been with ubuntu based linux. Specifically LinuxMint currently 17.3

I say this because most of the write ups assume or seem to assume either you have a configurable dhcp or that all the options in ltsp.conf work as expected. Or that you took mind reading 101. I, like many , am not a linux guru but i can manage. I’ve played with linux for many years but not enough to know everything like in windows. So hopefully this is helpful to some of you.

so…here we go…

For anyone having next-server problems I found that you may need to add the dhcp-option setting into dnsmasq.conf in

/etc/dnsmasq.conf

to make clear… if you have next-server, tftp download problems, or download/operation not supported errors with undionly.xxx try adding :

dhcp-option=66,"x.x.x.x"

to /etc/dnsmasq.conf
Where x.x.x.x is the IP of your tftp server.
At least in my case my tftp/fog/dnsmasq are all the same. DHCP is seperate and not mine to edit/config. This has been mostly for testing.

I’m not sure if the quotes are needed or not. try both ways if one doesn’t work.
you can also try adding:

dhcp-boot=undionly.kkpxe,,X.X.X.X

use whatever undionly.xxx you may need. Or try the ipxe.xxx. although the ipxe files havent worked for me yet. Just in case you new…these files are located in /tftpboot. Or whtever you made be your tftp root. /tftproot is default with ubuntu/fog This line may also NOT be needed as the boot file can come from the next info in ltsp.conf.

/etc/ltsp.conf

The line:

pxe-service=x86PC, "Boot from Network", pxelinux

is what will load your boot file. in this case it will look for pxelinux.0
No I dont know why it adds the 0. Just rename your undionly file to match. I usually make a copy and then rename.
so in my case i usually make a list:

pxe-service=x86PC, "Boot from Network pxelinux", pxelinux
pxe-service=x86PC, "Boot from Network undi.kpxe", undionly.kpxe
pxe-service=x86PC, "Boot from Network undi.kkpxe", undionly.kkpxe

The line in quotes is what will appear when you initially network boot. The file name at the end is what is important. At least as far as the file name it will try to find. The bit in quotes is just an echo for you at the console. You could put “I’m going to boot someones ass if this doesnt work again” but rem, you may not be the only one reading the text.

Oh also these pxe-service…etc work just fine from ltsp.conf. at least so far.
(etc/ltsp.conf) But can be added to dnsmasq.conf. Although I havent tested that to see how it works yet.

If you decide to use pxelinux.0 it will try to point to a folder called pxelinux.cfg
and a file called default. from your tftp root.

so in my case my tftp root is /tftpboot
pxelinux.0 will point to

/tftpboot/pxelinux.cfg/default.0

That location will have to be created manually. And make a basic config in default.0 such as:

DEFAULT vesamenu.c32
MENU TITLE Fog Reimage Menu
MENU COLOR TITLE        1;36;44    #ffffffff #00000000 std
LABEL iPXE Boot
MENU DEFAULT
KERNEL ipxe.krn
APPEND dhcp && chain http://x.x.x.x/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 1

That will at least boot you to fog menu. rem. to change the x.x.x.x to your fog server.

there is a write up here for more details:
https://wiki.centos.org/HowTos/PXE/PXE_Setup/Menus

As far as I understand that is the older way of doing things but it may solve some frustrations.

now if anyone can help with Wimboot and getting past needing a driver… That would be awesome.

Hope this helps someone.

I don’t know much but will offer any assistance I can from my trials and errors.

A brief recap. If some of the settings in /etc/ltsp.conf are not working. Try them in /etc/dnsmasq.conf.

Thanks for stopping by.
Jason