@EAHarvey lol. He’s been a user here for two years.

@Wayne-Workman If I understand the OP’s post there were two actions that were needed.

Since there is a firewall between the two subnets, 2 rules needed to be crafted to allow communication between the devices on the subnet where the fog server was not. On the subnet where the fog server was not he had to update the dhcp to include the next server and boot file settings. On this one I gather (guess) that each subnet has its own dhcp server.

Tom Elliot has resolved the installer not asking for any info issue but now fails with error:

* Adding needed repository....................................Failed!

I’ve checked the log at /var/log/fog_error_5893.log which shows

Package epel-release-6-8.noarch already installed and latest version Nothing to do package http://rpms.remirepo.net/enterprise/remi-release-6.7.rpm is not installed Loaded plugins: fastestmirror Setting up Install Process Cannot open: http://rpms.remirepo.net/enterprise/remi-release-6.7.rpm. Skipping. Error: Nothing to do ../lib/common/functions.sh: line 439: yum-config-manager: command not found

So the remi repo needed to be enabled, doing this alone was not sufficient to fix problem, Tom Elliot also had to enable yum-config-manager. Tom has updated this in git and i’m now running on trunk@4617

Tom/Wayne, thanks again for your efforts, really do appreciate it.

regards Kiweegie.

@ManofValor We’ll need to remote in to see exactly whats causing your issue. We’ve sent you a chat message with further detail.

I’ve solved the thread.

The timeout was because this system is on an isolated network.

The isolated network IP is 192.168.1.1, but the wifi lan is set to 192.168.1.207 (which gives the device internet for upgraded/updating).

To enable the installation to operate, I changed the IP address to 192.168.1.207 as the DB settings were already set.

This ipaddress was used to generate the default.ipxe file which was what was causing the problem and I over looked it.

Sorry 😞

@templink People new to FOG always blame every little bump in the road on FOG… I’ve been getting hit with nonsense from co-workers for almost a year now. Just seems like that’s how it goes.

Either way, you’re always more than welcome to post issues here.

Hey, after tessting it really looks like the problem is on that SSD. Could deploy and upload on other clients. I guess the first imaging tool brokes it. But after all fog is better than that anyway. Thank you for your help!

What OS are you using on the FOG server?
Ubuntu LTS 14.04.3 -> ubuntu-14.04.3-desktop-amd64.iso

What version of FOG are you using. I will guess 1.2.0, but did you upgrade to the trunk version (i.e. pre 1.3.0)?
1.2.0

yesterday evening i think about this options and now i am sure that i mixed up with Norton Ghost.
In FOG u build the the Hosts to Groups and if all Groupmembers ready then starts the Multicasting-Task.
As is told, in Ghost there was the 2 Options (‘wait for last member then start’ or ‘start on my command’)
confusing on my side - already fine…
u can close this thread 😃

@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.