@Lemeunier Sounds strange. Possibly your disk is full? Run df -h and post output here.

I can’t see your screen shot, but I had a problem with a similar error message yesterday. Turns out it was because I had moved my image folder and missed one of the configs you have to change. Searching the forum should being up numerous other threads with that error message, I’d try some of those fixes.

Philip

@wayne-workman

Perfect. I already made the script, just didn’t know if it would add the machines to my list or just install the software and then not communicate with the server. Thanks!

@kellym Sorry I didn’t check the forums yesterday, glad you found it!

@vijaybomble OK great you have the prerequsites in the proper configuration.

If your fog server is your dhcp server, and your pxe booting client are on the same subnet, lets use your fog server to capture what is pxe booting is doing on your network. You can use tcpdump on the fog server to capture only the traffic we need. I have a tutorial here on what you have to do: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Upload the pcap to this forum or use a private google drive and im me the link and I’ll take a look to see what is going wrong.

@tom-elliott Hello Tom! I know that. But you misunderstand me!
What I do is the following:
I change an entry under “Active Directory” and press “Update” in this section -> Feedback: “successfully saved”.
If I then go to any other menu item in the FOG (e.g., Dashboard) and back to the “FOG Settings” to “Active Directory”, the changes made will still be there!
If I now change another item in the settings (for example, PXE MENU TIMEOUT and change the value 5 to 3) and press Update under this section, appears again “successfully saved”.
But if I switch to the dashboard and go back to the FOG settings under “Achtive Directory”, the entries made there have disappeared and also the change in the section above it (in PXE MENU TIMEOUT is again stored 5 instead of 3!)!
Printscreens:
First Change in Active Directory:
0_1528959423881_1-first_change.jpg

Press update:
0_1528959483221_2-success.jpg

Going to dashboard and back to FOG-Settings changing “PXE MENU TIMEOUT from 5 to 3” and press update:
0_1528959526220_3-second_change.jpg

Going to dashboard and back to Fog-Settings, all changes are gone!!:
0_1528959638221_4-go_to_dashboard_and_back_to_settings.jpg

mysql> select * from userTracking where utHostID=1312; +-------+----------+------------+----------+---------------------+--------+------------+---------+ | utID | utHostID | utUserName | utAction | utDateTime | utDesc | utDate | utAnon3 | +-------+----------+------------+----------+---------------------+--------+------------+---------+ | 5583 | 1312 | rechit | 0 | 2018-04-03 16:50:44 | | 2018-04-03 | | | 19841 | 1312 | rechit | 1 | 2018-04-18 10:57:47 | | 2018-04-18 | | | 26357 | 1312 | rechit | 1 | 2018-04-25 09:41:23 | | 2018-04-25 | | | 33295 | 1312 | rechit | 1 | 2018-05-16 08:40:23 | | 2018-05-16 | | | 43095 | 1312 | rechit | 0 | 2018-05-28 14:19:27 | | 2018-05-28 | | | 43111 | 1312 | rechit | 1 | 2018-05-28 14:32:43 | | 2018-05-28 | | +-------+----------+------------+----------+---------------------+--------+------------+---------+ 6 rows in set (0,00 sec) mysql> select count(*) from userTracking; +----------+ | count(*) | +----------+ | 53885 | +----------+ 1 row in set (0,00 sec)

@vince-villarreal Yep. This can be automated with group policy though. When a box joins your domain automatically via the FOG Client, you can have group policy turn on TPM. I suppose TPM would need turned off somehow via postinit scripts.

I had to go in and manually delete each unused version. After that if fixed my issue. I was able to successfully update fog.

Thanks for your help.

@tom-elliott not sure how the fog version got mixed… I just ran the git pull and rerun the installfog.sh in command to update to latest in dev-branch.
maybe something in 1.5.0 rc10 that I had that screwed it up going to 1.5.4??
btw, I’ve been running 1.4.4 and been updating in command line ever since.

coming in this morning, the replicator is looking normal. the node usage pie chart is normal compare to the main server chart. before it would show 20-40% as it was constantly deleting and replicating. replicator logs are saying No need to sync which is good.

Interesting to see others in here experienced the same issue updating to 1.5.4

I appreciate the offer but I have to get these computer labs up and running soon. Love the support and fog has been a life saver. 😃

@steuve68 and in the end it was the online check from fog activating that computers, like i told you 😉 I still have the ping check enabled i solved my problems around that with hibernating off und pattern match in nic drivers disabled.

Regards X23

Thanks - i have discovered there is an issue between the keyboard and chair at my workstation - i have 2 imaging servers - and i obviously fired up the wrong one. all is now well . disregard !

@fogmbr There probably is a way around this but it will cost us together some time to figure out and I thing the image shouldn’t be used on the 5570 as is anyway. Starting from the different disks (needs different windows drivers) and probably there is other hardware being different that needs to be addressed after imaging manually anyway. My guess is you are way better of capturing a separate image…

I’m running 1.5.4 and have this issue. Are there any updated workarounds?

Now this is a dirty way to do it as I don’t have the MYSQL skills or database background. What you can do it go to reports and run an inventory report. Export that. Now cant the column that has the hostname and change it to what you want. Find and replace or just trim your hostname down to asset tag them add whatever your naming convention is. So now you have a new column of hostname and the MAC address that was exported from inventory report. Follow the format for CSV upload here https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Hosts

Now under the 4th column add “Description” name this something like import and the date. This will be used to group the hosts you just imported. Go into FOG add whatever hosts you want to change to a group. Delete that group and check and delete hosts. NOTE this will remove all history assigned images settings and login history (Hence Dirty Way) Now import the hosts you want back in. After you successfully import your assets back in go to the hosts tab and search the description you added on import. Select all those hosts and add them to a group to apply all the new settings to. Once you add service settings and AD info they will start renaming your computers and depending on your settings may or may not reboot the computer.

@vince-villarreal Wiki is back up again.

@quazz Got the result:

noTftpBuild=''

Not sure if thats good or bad.

@ablohowiak Can you please let us know what the issue was? Others might find this information helpful as well.

Sorry for the late reply, got distracted with the weekend.

Are you deploying the same resizable image to both the 380 and 390 or are these different images?

They’re not hardware independent images, so I’ve been creating the master image on a 390 and then deploying to other 390s, and I’ve been trying to do that with the 380, but as mentioned it isn’t working.

Have you ever successfully imaged an optiplex 380 with fog before? I believe I have several optiplex 380s here at home, they all image just fine.

On our old FOG server they deployed just fine, but it seems there is some issue with this newer version of FOG or something.

FOG version?

I’m not at the office currently, but I believe it’s 1.5.2 or 1.5.3

@sutra Sorry for the late reply! Can you provide the contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions? You find those files on your FOG server in /images/Alienware-i9-010618.