@george1421 said in Installation stops during setting up fogproject password: @Deimos If you look in the directory where you installed fog from in the bin directory (where installfog.sh script is) there should be an error log directory. In that directory is the error logs that explain what happened to the install. Yes, thanks. I know this, but the Fedora Server is in the office and it’s weekend. I thought may reply was enough for now. I will post the error log tomorrow in the morning.

@george1421 I had time to spin up two new fog servers in my test area, one for imaging and one for client interaction. The client interaction one is set to connect to the DB of the imaging one. I also imported the certs from my production machine to both. Unfortunately I ran out of time before I could actually test anything. Holding pattern until Monday I suppose.

@Testers Anyone able to replicate this?

@george1421 said in Capture problem: I have noticed an uptick in people reporting this invalid storage group. Aß mentioned in my last post it’s not the same error message everytime. A couple of times we hat the “Invalid Storage Node” but this one is not.

@jtappen From what you wrote it seems like you are on the right track with this - Active Directory Defaults in the FOG settings should be the was to go. So which way do you actually register your clients? Our Fog is on versoin 1.5.6 This is not the latest version. I cannot say for sure we have found und fixed in the latest but if we find this to be a bug I need you to update to the very latest version.

@ibivibiv Ok I was correct! I think maybe there is a more clever way to update the grub directory contents (grub update command etc.) but basically if I do the following I find myself with a fairly close to working system: dd the MBR file to /dev/sda sfdisk the partitions to /dev/sda partclone restore d1p1.img to /dev/sda1 Take the grub contents from the original machine and overwrite them onto sda1 partclone restore d1p6.img to /dev/sda6 mkswap to /dev/sda5 with the uuid from the orig uuid file This drops me into the grub menu and after the timeout it boots as normal. Not too bad, and hopefully it helps anybody else that asks this question. I saw it gets brought up sometimes.

@Brad-Schumann From what you wrote so far I am fairly sure this is a different issue than we had before. Please open a new topic and post more details on when this is exactly happening. When there is a task scheduled or if you try to register the host or what?

@Fernando-Gietz Possible bug in the location plugin. What do you think?

@Greg-Plamondon you would need to use hooks to achieve this. look at removehosteditgen.hook.php in hooks folder on webserver

@chris-lynn said in New latitude E7400. No internal NIC, Boot to USB-C Puck NIC. Gets IP from DHCP but does not connect to Fog.: We have since updated our FOG DHCP boot file to ipxe.efi FWIW: If the fog server IS your dhcp server for imaging and you had FOG install and configure the dhcp server, it should automatically manage the right boot file based on the pxe booting computer. You should not have to change anything. If you have a MS Windows dhcp server then there are somethings you can do to make it dynamic.

Los directorios que cuelgan de /images2 pueden tener todos los permisos habilitados pero si /images2 no los tiene, no puede acceder drwxrwxrwx 284 fog root 16384 oct 11 14:11 images

@astrugatch The link is in my signature. Testing is suspended by request of @Sebastian-Roth until the 20th of this month. The last test results can be seen on the site.

@darkxeno In the dell firmware switch the disk controller from Raid-on to AHCI mode. Unless you have more than one disk connected in a raid configuration raid-on mode doesn’t help you. There is a document issues between linux and intel controllers in raid-on mode. Once you have imaged with fog you can switch back to raid-on mode or leave it in ahci mode. It doesn’t matter to windows.

@Middle Unfortunately, aside from the latency kernel argument there isn’t anything else we can do from our side as far as I’m aware. Unfortunately manufacturers don’t always check how their stuff works on linux…

@Celena said in I have a problems! I need your help: he computer reboots before Windows has a chance to set up completely. This is probably because you didn’t follow the guidance on the wiki about disabling the fog service on your reference image and then enabling it in your setupcomplete.cmd batch file. https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep (but that’s just a guess)

George, I have another question, this time about sysprep. Why do we need to go through OOBE for an installation that is all in the same locale? Wouldn’t it be easier to just generalize and be done? And if doing that, do I still need to disable the Fog Client Service before doing it? Thank you, Dave

@Gamienator said in Choose the right location on PXE Boot - Is that possible?: Wouldn’t it be possible to automate the meta data sync? I’m thinking of using the FOG API. It should be possible to grab all the needed Information and then update it on every other FOG server in the different locations. The short answer is yes. The longer answer is that it will take a programmer to write an external application to query the api on the master node and then on the remote node to update. This probably could be done in powershell, but to make the finished product useful to the fog project writing the data migration module in php would be the best. Then at least we could setup a cron job to run the php script and migrate the data that way. It would be a bit of giving back to the fog project if you were so inclined.

@TBuzaTechnician You would need to run the mysqladmin command first, then do the command. That should set your mysql password and ensure FOG will install using that now set password. Thank you,

@Mr_Matten Ah, glad you figured it out!

What device is your dhcp server. I’m going to guess it is a soho (home) router? The reason I think this is your gateway is 192.168.0.1 and your next server (from the picture) is also 192.168.0.1. Home (soho) routers will often say they are the pxe boot server and not the fog server.