@kermit1991 Do you see this issue on all your clients or just when using an USB ethernet adapter? Have you tried using the ethernet adapter together with different clients. Sometimes adapters and client’s BIOS/UEFI firmware just don’t play together well enough. On the other hand some USB ethernet adapters just don’t play nicely altogether. It’s a long process to figure out what exactly the issue is. So start by telling us more about the exact USB adapter you have and make/model of PC/laptop you use.

@vince-villarreal this is the purpose of the persistent groups plugin. When a host is added, the new host will get whatever the template host has defined. This, to my knowledge, only happens when a new host is added. If you add a host to the group, then later edit the host itself, it should retain the new changes regardless of the template, until you remove and readd the host to the group.

@salginer The partition layout looks pretty straight forward. Is your Windows partition bitlocker encrypted? Run manage-bde -status C: in a admin command shell.

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

@uwpviolator I’m not sure if such a file/key exists. We should ask @joe-schmitt about that. You could just do a wholesale - uninstall and reinstall for all your machines.

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

@Wayne-Workman the 6 first of the mac are the same and fog could see somes of theese MAC.

i’m still looking for BUT you’re right @Sebastian-Roth , the forticlient have an integrated FW, maybe the problem… today i will look if I can turn off the FW part and you say after

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

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

@tom-elliott Updated the production server and it is now multicasting. As a side note though I tried to start a ‘test’ session of multicast, the same name I had used pre-update, and it did the same thing(started and instant ended). But if I picked a new name that I hadn’t used before, it appeared to start and wait for connections normally.

Philip

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.

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

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

Thanks I figured as much but was wondering why my storage nodes only had minimal traffic between them even though i had re-uploaded an image.

My summer projects started and I was planning to update our FOG system. Re-install and deleting old FOG database worked. Plus our database got a little sloppy so a purge is always good IMO.

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)

@dj FOS (name for the FOG system that loads at that point) doesn’t need /sbin/mount.nfs

I just checked and tested and it all works fine in my environment.

Can you run mount -v | grep images on a system where you were able to mount the nfs share and take a screenshot/paste it here?

What Ubuntu version is the FOG server running btw?

Did you test the mount in FOS on a system that mount does work in a full linux distro?

@george1421
As always, I appreciate the help! I am happy to help out where I can.

@george1421 Pffft…i’m there with ya brother.

I was able to remote in and find out what was going sideways with the OP’s system. I’ll fill out the details in a bit, but there is the keys.

mods-enabled/php5.conf set handler

9.4

sites-enabled/001-fog.config

It appears to be an issue with at least debian 9.4 at the moment where php-fpm wasn’t being enabled causing the sluggish UI and high apache usage.