@Wayne-Workman While that is true, it’s not always a possibility.

I would highly recommend upgrading if that was an option, but from the sounds of it, this is not necessarily the case. I’d really highly recommend going to trunk rather than 1.2 as well, if only so I can get more feedback on bugs and what not.

@cotec said:

The user which i can setup in FOG-WebGUI are admins or user? has this user access to webgui?

They are all sort of equal. the switch for “mobile only” really isn’t good because FOG mobile is in a state of disarray at the moment.

There is an access control plugin that is intended to limit what users can do based on location - but it doesn’t totally work right.

If you are concerned with other people goofing things up - just make everyone an account and tell them to use their own account. There is a history table in the database that will list most actions and the user that executed those actions.

Also - training goes a long way.

What version of fog @Sparky? I ask because in dev versions there is no more “Red X”

Please start a new thread since your issue will get lost in this thread’s title.

But it sounds like you have two dhcp servers running in your environment.

@Junkhacker Yeah, I’m with Wayne on this one. Do a sanity check with a second 5450. Just in case there is something wonky with this unit you can rule it out by compare and contrast.

As will all systems, make sure it is on the latest bios and be sure to reset the bios settings back to default first then make any system required changes.

I also found out through testing the target hard drive will have an impact on deployment times. Does the unit have a ssd or a rotating hard drive?

@Tom-Elliott The upgrading process should replace spaces in computer names with hyphens.

@Tom-Elliott Did a fresh pull and can confirm the install script now finishes successfully on CentOS 7. Will test on the Ubuntu box later just to confirm - but I imagine it will work there now as well. Thanks again for all of the help with this Tom.

@george1421

Thank you for all of the assistance. I really appreciate it. I have all of the keys for all of the Windows install’s so typing them in shouldn’t be an issue.

Thanks again!

@Rusty said:

Do I just add an entry like in the pic ? Is the change on the network pretty quick or do the changes need to be propagated somehow ?

It’s hard to tell from the picture, but I can see that the .local Top Level Domain is selected. Generally it’s not good in the long run to use the generic top level domains like .local See this for more details on best practices: http://serverfault.com/questions/402580/what-is-active-directory-domain-services-and-how-does-it-work

The entry looks right, but is you’re fog server actually named “fog-server” ? Maybe create an A record for it’s real name too?

Also - is DHCP configured to hand out this particular DNS server? Also - are the hosts in the environment set to automatically configure DNS or is DNS statically set?

On windows, you can use the nslookup utility to resolve IPs and names, you can also specify which DNS server to use.

Go to https://rom-o-matic.eu

Click the drop down and choose
UNDI only (.kpxe)

Paste this script into the script box:

#!ipxe dhcp cpuid --ext 29 && set arch x86_64 || set arch i386 params param mac0 ${net0/mac} param arch ${arch} param product ${product} param manufacturer ${product} param ipxever ${version} param filename ${filename} isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :bootme chain http://10.50.0.48/fog/service/ipxe/boot.php##params

Click Proceed, save the new undionly.kpxe, transfer it to your FOG server’s /tftpboot and give it another whirl.

Either portfast/RSTP or you can try using iPXE with native driver support. On your DHCP server change bootfile option from undionly.kpxe to ipxe.pxe and see if it makes any difference.

@Wayne-Workman Hi Wayne, I had to give up on the Storage node set up and go with a separate Normal node as I need to get this back up and running sooner than later 🙂

The node which is causing issue is the storage node for head office so I’m just going to set up that box as a normal node instead and split the roles so we have one node for head office and one for the remote sites. It may even make things simpler.

I can spin up another Storage node at some point to aid in diagnosis of the original issue but for now my priority is getting our FOG solution back up and running again.

regards Kiweegie

@mobile_bob It’s up to you. Feel free to upload the MBR file and I’ll have a look. Might be helpful to other users but can’t say for sure before I have seen the file (might find nothing unsuspected).

@AsciiReign said:

How do i mark the thread as solved?

It’s done

@Ph3noM Fog doesn’t set a DB password - if fog sets up the DB on a new server, it’s left blank. The installer (at least in FOG 1.3.0 beta) asks you for a DB password just in case you set one in the back end. And of course if that’s the case (and 99% of the time it is) then the field in /opt/fog/.fogsettings would be blank as well.

How is DHCP setup in your network? Maybe this is dnsmasq ProxyDHCP and the new EliteBooks (EFI??) don’t like to talk to it?!? Just a random guess.

@Wayne-Workman Sorry Wayne ignore last re fog certificate. Issue was only on my laptop and has since been resolved.

I have not come across this issue since starting this thread (I did update FOG somewhere after the start of the thread which included updates for the binaries)

At worst it will ask me to enter the IP address which is a small price to pay for peace of mind.

So I guess this can be considered solved for now.

@GregorS
The problem is with your server. Notice the log lines

14.12.2015 12:53 Data::RSA ERROR: Certificate validation failed 14.12.2015 12:53 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid) 14.12.2015 12:53 Middleware::Authentication ERROR: Could not authenticate 14.12.2015 12:53 Middleware::Authentication ERROR: Certificate is not from FOG CA

@Tom-Elliott would be able to help you debug why your server certs are incorrect.