@Tom-Elliott
So I believe I solved this - your chmod is exactly right - I was chewing on the /images permissions owner last nght, got into the office and looked at it with fresh eyes…simple problem, simple solution.
[root@FOG /]# ls -la images/
total 0
drwxrwxrwx. 4 root root 61 Mar 8 18:04 .
dr-xr-xr-x. 20 root root 284 Mar 8 17:33 ..
drwxrwxrwx. 3 root root 46 Mar 8 18:02 dev
-rwxrwxrwx. 1 root root 0 Mar 8 18:00 .mntcheck
drwxrwxrwx. 2 root root 30 Mar 8 17:33 postdownloadscripts
[root@FOG /]# chown -R fog images/
[root@FOG /]# ls -la images/
total 0
drwxrwxrwx. 4 fog root 61 Mar 8 18:04 .
dr-xr-xr-x. 20 root root 284 Mar 8 17:33 ..
drwxrwxrwx. 3 fog root 46 Mar 8 18:02 dev
-rwxrwxrwx. 1 fog root 0 Mar 8 18:00 .mntcheck
drwxrwxrwx. 2 fog root 30 Mar 8 17:33 postdownloadscripts
[root@FOG /]#
I then bounced my test client and it picked up its capture task immediately as it did in my test lab. (Test lab in esxi server hosting fog to a pc on same vlan hosting test client in vmware workstation worked 1st try. Implementing this in a Windows Domain environment was still easy with the exception of this one speedbump)
To be utterly complete I will still need to Deploy a Captured image.
This solution is painfully obvious I admit, Your tutorial is excellent- however I might suggest for those following it to spec this albeit obvious permissions update might be included as optional for this error only?