Posts made by Quazz

@Tom-Elliott said:

@Robx64 First update to the latest then you will need to edit the quick image menu item from the GUI.

This is the original information

login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

Make it read as:

params
param mac0 ${net0/mac}
param arch ${arch}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

@Robx64 said:

@Quazz said:

I’m on git version 5475

Yeah sure, where can i get it ?

If you’re using svn:

Navigate to the svn directory you set up earlier

svn up -r 4408

Then just install as usual.

Svn and git versioning are different, hence the different number here.

I’m on git version 5475 if you want to try a (from what I’ve seen) stable trunk release.

@Jbob said:

@Rusty This is the best guide that has been written so far. It does include some text on fog server setup, so skip to the “WORKSTATION IMAGE CREATION” section

https://forums.fogproject.org/uploads/files/1443813159297-imaging-server.pdf

I second this. Although if you’re not using AD you need to change a few things.

@ch3i Really? I was never able to login with that.

For quick image you need to create a new user for it at the FOG WebGUI management page in order to use it.

Not sure about the rest, does your network have a firewall? Does it have an existing DHCP?

@Hanz As far as I know, the pxe binaries come with the FOG package itself, whereas the bzimage is downloaded upon installation.

ipaddress (My understanding is that this is the ip address of the fog server itself)

interface (This is the interface fog will use for everything, by default. Multicast interface and what not can be altered later in the database)

submask (The subnet mask for the network your fogserver is on, this is there irrespective of whether you enable FOGDhcp)

dnsaddress (The DNS address to be used by the FOG server)

Password (the password FOG generates on install for the fog account, this should match the storageftppass password)

@Sebastian-Roth It doesn’t, you’re correct, it’s merely used to support UEFI booting based on the client’s capabilities.

@Tom-Elliott Ahhh, can’t believe I was that stupid, you are right of course. I was led to thinking this when I installed the server in a VM and imported the database but obviously forgot to update the storage password.

My bad, sorry for taking up your time with my nonsense.

@Tom-Elliott I think I may not have made myself clear.

The fields are indeed prepopulated. But when you then alter the data (aka you go into the field and manually change it) it will display these changes to you, but then when you go to save it it will save the prepopulated data, rather than the data you deliberatily filled in.

@Sebastian-Roth If this is the case, would it be possible for the FOG DHCP to automatically create specific classes for those manufacturers so that it will choose the right binary regardless?

I created one for realtek because of certain NICs and it’s been working great.

You need to add the following option for the code below:

option architecture-type code 93 = unsigned integer 16;

class "realtek" {
  match if option vendor-class-identifier = "realtek";
 if option architecture-type = 00:00 {
  filename "realtek.kpxe";
  } elsif option architecture-type = 00:09 {
  filename "realtek.efi";
  } elsif option architecture-type = 00:07 {
  filename "realtek.efi";
  } elsif option architecture-type = 00:06 {
  filename "i386-efi/realtek.efi";
  } else {
  filename "realtek.kpxe";
  }
}

@Tom-Elliott You’re correct, but under normal circumstances if you alter the data after it autofills, it will accept and store the new data. It does not for the storage node login information, however.

@Wayne-Workman

The Storage Node password update thing seems to have trouble whenever you save the password of the WebGUI login (at least it does for chrome, not sure for other browsers)

It will overwrite the password in the field with the WebGUI password.

Did you add the Ubuntu folder to the exports file as nfs location?

Hi.

To fix the sysprep fatal error issue, simply stop the Windows Media Player Network Sharing service.