Right now your only option is to image on an isolated network away from your production network. I suspect that WDS is using proxydhcp which will override your setting in dhcp options 66 and 67. There is no way around this AFAIK.

It would be interesting to see what WDS is actually doing this tutorial tells you how to do this with the fog server: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Or you can use wireshark with the capture filters of port 67 or port 68 or port 69 or port 4011

If you want us (or me) to look at it upload the pcap to a google drive and either post the link here or IM me the link and I’ll review it. It would be interesting to know exactly what WDS is doing here. But in the end, having an isolated (but routable) imaging network is probably your only solution. You just need a network where you can limit the broadcast domain to only that subnet.

@quazz You’re right. Must have been a bad spot or something. One thing we all know Windows does is to add a minimum of two partitions on a clean install. Mine had 3 (ms system reserved, empty) partition. Did lots of research, found I don’t need three, just setup GPT with single partition, did base install, and now FOG imaging upload works.

Thanks for pointing me in the right direction.

@x23piracy said in [Windows (Powershell) / Username=Computername]

@Tywyn like @Avaryan said why not use unattend.xml to create local users?

Having a Powershell-script, that does more, for example, set ip-addresses, active office/windows, sets the correct time, etc.

AND: I have no idea how to use unattend.xml 🙂

@rabus The client communicates with the server over http for command and control functions and then NFS and FTP during imaging .

The client uses http and tftp during pxe booting process.

I feel there are some undisclosed meaning in your questions. If you were clearer with what you need, we may be able to provide a better quality answer for you.

@Joe-Schmitt wrote the slack plugin.

@george1421
That is gold. Thank you.

@joseska Sorry for the late reply! The fog-client detects the system language and uses that to display the messages. No configuration needed except for setting the system language to Spanish in your case.

@george1421 said in FOG MENU FILE:

@breit The boot.php script builds the iPXE menu on the fly based on what the client is asking, the state of knowledge about the clinet, and what the client is. There is no static file that can be changed. If you want to change the iPXE menu you can

Work within the frame work the developers have provided with the iPXE menu configuration in the FOG Settings. Write your own plugin to alter and hook into the boot menu creation. Hack the php code to make the boot.php page create things the way you want.

Each has its drawback and advantages, but beyond step 1 you add quite a bit of complexity to your task.

Thanks for the Info and all your help!

@freak
checkin and obtain taskid

http://FOGSERVER/fog/service/snapins.checkin.php?mac=MACADDRESS

then to update status:
http://FOGSERVER/fog/service/snapins.file.php?mac=MACADDRESS&taskid=TASKID&stateid=STATEID

@Foglalt Thanks for the thumbs up! You are welcome and I am sure we can figure out what’s wrong in case this is still happening with 1.4.4! Please keep us posted.

@thiagotw Hey I’m glad we were able to get it worked out. And I have to say, your graphic is way cooler than my avatar!! Maybe someday I will get that good with graphics to update my avatar. 🙂

Ah well … turns out i’m just simply blind 😛

I changed the path in the commands to my local folder structure but missed one spot … since it booted pretty far I thought everything must be written correctly, turns out: No.

Thanks for the help.

Yes there is a kernel parameter for that its the vga parameter.

vga=792 This should be 1024x768x24

ref: https://unix.stackexchange.com/questions/71231/grub2-and-kernel-vga-parameter/114980

Thanks a ton!

Thanks. I was just wondering. Before I recreated the /home/fog/ directory the image capture process kept giving errors. So I was thinking that there might be some script or something in that directory. However, now after just manually recreating that directory image capture is working just fine again. I had run the installofg.sh and I had thought that it would have recreated the fog home directory, since it did detect that the directory was missing. I didn’t read the screen carefully enough to see that it was directing me to manually delete and recreate the fog user. Recreating the home directory did the trick through.

Thanks for confirming that I am not missing anything critical in that directory though.

Tim

@alexvm said in Selecting which server to capture/deploy images on Fog:

is to select on which server I want the images to be captured first and which server to deploy them first.

There are some rules that you have to work with. Rule 1. Captures always, always, always go to the master of the storage-group the image is assigned to. This rule can’t be changed, it’s how fog works.

However, you can have many storage groups, and a storage node can belong to many groups. A storage node can be a master in one group, and a non-master in another - there’s a whole lot of ways to setup the nodes & groups & masters. Here’s more information on how replication works: https://wiki.fogproject.org/wiki/index.php?title=Replication

For the second part of your question, I think you might be looking for the Location plugin, here’s more details: https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin I think if you watch the video, a lot of your questions will be answered.

@tywyn said in Computer does not see DHCP on PXE-Boot, but it does with Windows running:

Your hint to put a dump hub/switch between client and network dose did solve the problem as well.

FWIW: This is a quick test we can use to see if standard spanning tree is the issue. The dumb switch will keep the building switch from transitioning during the boot of FOS.

@george1421
Thanks george, hopefully we will begin to implement the pxechain method and actually get this system off the ground.

Appreciate your help.

@tandersb said in Cannot capture image- fails at 'Saving original partition table':

Is there a mailing list I should be on to get notified of new releases?

Release Candidates and Releases are in the Announcements area:
https://forums.fogproject.org/category/22/announcements

But currently news.fogproject.org is not working.

Latest version is also shown right on the FOG login screen, and in FOG Configuration area too.

This has been fixed.