FOG Client not processing snapin tasks

[BedCruncher]

Server

• FOG Version: 1.4.4
• OS: Centos 7

Client

• Service Version: 0.11.12
• OS: Windows 7 Pro x64

Description

Some clients aren’t checking in on snapin tasks. They stay in queued status. I’ve rebooted the system and client. They never seem to process those tasks. Thoughts on how to rectify this?

[Tom Elliott]

If this is a problem with FOG itself, then I would think ALL snapin tasks would fail to process.

Is there potential there’s logs to go along with the machines that are failing to process things?

[BedCruncher]

@Tom-Elliott
Gimme a sec to grab the logs from the client. Which logs are you needing from the server?

EDIT:
Here is a link to the logs from the problem client
fog.log

[BedCruncher]

@Tom-Elliott
Follow up. I’m using the same image on multiple like model laptops, most work without issue. The ones that never seem to process the snapin tasks are few and far between. In the most recent multicast session, I did 4 identical ones. 3 pushed the snapin tasks without issue.

[Tom Elliott]

@BedCruncher Then I might suggest seeing if those machines need to be “reset encryption data”?

[BedCruncher]

@Tom-Elliott
I just tried something that seems to work for now. I have swapped out the switch they are all plugged into in reference to the lines from the log that say
7/6/2017 10:05 AM Middleware::Communication ERROR: Could not contact FOG server
7/6/2017 10:05 AM Middleware::Communication ERROR: Unable to connect to the remote server

The clients have so far checked in OK. I’ll go back and revisit the other machines that were having issues and reply back to let you know what’s going on. Hopefully it’s not truly a switch issue so that I don’t look like a friggin idiot.

[Tom Elliott]

@BedCruncher I suppose if they cannot communicate to the server that could cause issues for obvious reasons…

[BedCruncher]

@Tom-Elliott
That’s the thing though… They could talk through the server because I could mount a shared drive and do all other things using that same previous setup. Imaging worked fine. It’s freaking weird

[Tom Elliott]

@BedCruncher Maybe DNS handling in FOS is better than how it’s being handled when the OS is opened?