Chain INPUT (policy ACCEPT)
target prot opt source Destination
Chain FORWARD (policy ACCEPT)
target prot opt source Destination
Chain OUTPUT (policy ACCEPT)
target prot opt source Destination
For iptables. Appreciate the help on this!
Yeah I have it under the A name in my DNS, the actual client for other computers uses IP as well, so both are being used
{
"HTTPS": "0",
"Tray": "1",
"Server": "fogserver",
"WebRoot": "/fog",
"Version": "0.11.16",
"Company": "FOG",
"RootLog": "1"
}
Just checked again on my hosts, still only showing the ones I’ve added via registration in pxe
Sorry for the late reply, had a catastrophe with our server and had to rebuild it.
The only thing imported are the images and now I’m on Ubuntu.
The log is on my Windows 7 PC in the user folder, this is the most recent after the server rebuild
So what I’m expecting is having computers with the FOG client on, to be displayed in the hosts menu in FOG, but they arent listed, they get listed if I register them in PXE.
My log is reading;
3/29/2019 8:58 AM Service ERROR: Unable to parse sleep time
3/29/2019 8:58 AM Service ERROR: Input string was not in a correct format.
3/29/2019 8:58 AM Service Sleeping for 60 seconds
3/29/2019 8:58 AM Bus::Client ERROR: No connection could be made because the target machine actively refused it
3/29/2019 8:58 AM Bus::Client ERROR: No connection could be made because the target machine actively refused it
3/29/2019 8:59 AM Middleware::Response Success
------------------------------------------------------------------------------
----------------------------------AutoLogOut----------------------------------
------------------------------------------------------------------------------
3/29/2019 8:59 AM Client-Info Client Version: 0.11.16
3/29/2019 8:59 AM Client-Info Client OS: Windows
3/29/2019 8:59 AM Client-Info Server Version:
3/29/2019 8:59 AM Middleware::Response Success
------------------------------------------------------------------------------
------------------------------------------------------------------------------
-----------------------------DefaultPrinterManager----------------------------
------------------------------------------------------------------------------
3/29/2019 8:59 AM Client-Info Client Version: 0.11.16
3/29/2019 8:59 AM Client-Info Client OS: Windows
3/29/2019 8:59 AM Client-Info Server Version:
3/29/2019 8:59 AM Middleware::Response Success
------------------------------------------------------------------------------
------------------------------------------------------------------------------
--------------------------------DisplayManager--------------------------------
------------------------------------------------------------------------------
3/29/2019 8:59 AM Client-Info Client Version: 0.11.16
3/29/2019 8:59 AM Client-Info Client OS: Windows
3/29/2019 8:59 AM Client-Info Server Version:
3/29/2019 8:59 AM Middleware::Response Success
3/29/2019 8:59 AM DisplayManager ERROR: Invalid settings provided
------------------------------------------------------------------------------
3/29/2019 8:59 AM Service ERROR: Unable to parse sleep time
3/29/2019 8:59 AM Service ERROR: Input string was not in a correct format.
3/29/2019 8:59 AM Service Sleeping for 60 seconds
3/29/2019 8:59 AM Bus::Client ERROR: No connection could be made because the target machine actively refused it
3/29/2019 8:59 AM Bus::Client ERROR: No connection could be made because the target machine actively refused it
```Appears I’ve got somewhere with this, now i’m having the following in my log
Service ERROR: Input string was not in a correct format.
Okay interesting, so on mine I have the batch file look for existing installations of FOG, if theres non then just run the MSI, seems to have worked for that one client, but theres no way of telling since registering on the fog server seems sporadic right now
Also found the firewall things here;
https://wiki.fogproject.org/wiki/index.php/Client_Setup#Firewall_Exceptions
@george1421
Okay heres something wild, I dont know how but a random users PC just registered itself on the Fog server, though I havent set my script to deploy to anyone, only a specific OU…
So I guess the good news is that it worked for one machine, the bad news is I think I just pushed Fog out prematurely
edit: Okay turns out I deployed it somehow, no going back now. At least its worked for one computer!
I’m not seeing any in pending, my first ever machine I put the client on did work, and went to pending but two I’ve just installed it on arent showing with the log errors as above, I’m gonna check firewall out
Hey guys
So I’m working on mass deploying the Fog client to all of our users computers so I can send images to them. I have the MSI set to install via batch file with the correct parameters.
msiexec /i "C:\temp\FOGService.msi" /qn USETRAY="1" HTTPS="0" WEBADDRESS="192.168.10.138" WEBROOT="/fog" ROOTLOG="1"
The test computers I have deployed it on are getting the following:
------------------------------------------------------------------------------
----------------------------------AutoLogOut----------------------------------
------------------------------------------------------------------------------
3/20/2019 2:01 PM Client-Info Client Version: 0.11.16
3/20/2019 2:01 PM Client-Info Client OS: Windows
3/20/2019 2:01 PM Client-Info Server Version:
3/20/2019 2:01 PM Middleware::Response Success
------------------------------------------------------------------------------
------------------------------------------------------------------------------
-----------------------------DefaultPrinterManager----------------------------
------------------------------------------------------------------------------
3/20/2019 2:01 PM Client-Info Client Version: 0.11.16
3/20/2019 2:01 PM Client-Info Client OS: Windows
3/20/2019 2:01 PM Client-Info Server Version:
3/20/2019 2:01 PM Middleware::Response Success
------------------------------------------------------------------------------
------------------------------------------------------------------------------
--------------------------------DisplayManager--------------------------------
------------------------------------------------------------------------------
3/20/2019 2:01 PM Client-Info Client Version: 0.11.16
3/20/2019 2:01 PM Client-Info Client OS: Windows
3/20/2019 2:01 PM Client-Info Server Version:
3/20/2019 2:01 PM Middleware::Response Success
3/20/2019 2:01 PM DisplayManager ERROR: Invalid settings provided
------------------------------------------------------------------------------
3/20/2019 2:01 PM Service ERROR: Unable to parse sleep time
3/20/2019 2:01 PM Service ERROR: Input string was not in a correct format.
3/20/2019 2:01 PM Service Sleeping for 60 seconds
3/20/2019 2:01 PM Bus::Client ERROR: No connection could be made because the target machine actively refused it
3/20/2019 2:01 PM Bus::Client ERROR: No connection could be made because the target machine actively refused it
These machines are NOT registered to the server, but I was hoping the client would take care of that as I’ve seen it before for my Windows machines.
Could someone point where I’m going wrong?
Wait… Maybe I’ve been going at this wrong.
Am I supposed to manually register each computer I image? I assumed the client would register the computer in the FOG server. My bad if so, I’ve looked at the quick register settings, enabled it but that isnt bringing new clients on to the server
------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
3/18/2019 12:55 PM Client-Info Client Version: 0.11.16
3/18/2019 12:55 PM Client-Info Client OS: Linux
3/18/2019 12:55 PM Client-Info Server Version: 1.5.5
3/18/2019 12:55 PM Middleware::Response Module is disabled on the host
------------------------------------------------------------------------------
Okay this is the newest error so far
Dont think that did the trick.
Turned off all of the computers I had the image on, reset encryption, turned the host image on, double checked to see if the FOG Client was interacting with the server, it was working from what I could see on the logs, imaged that machine again and just put it on a VM to test. Now on that image its showing the hostname of the host image and the FOG log is showing
3/18/2019 11:58 AM Client-Info Version: 0.11.16
3/18/2019 11:58 AM Client-Info OS: Linux
3/18/2019 11:58 AM Middleware::Authentication Waiting for authentication timeout to pass
3/18/2019 11:58 AM Middleware::Communication Download: http://192.168.10.138/fog/management/other/ssl/srvpublic.crt
3/18/2019 11:58 AM Data::RSA FOG Server CA cert found
3/18/2019 11:58 AM Middleware::Authentication Cert OK
3/18/2019 11:58 AM Middleware::Communication POST URL: http://192.168.10.138/fog/management/index.php?sub=requestClientInfo&authorize&newService
3/18/2019 11:58 AM Middleware::Response Invalid host
3/18/2019 11:58 AM Middleware::Communication URL: http://192.168.10.138/fog/service/register.php?hostname=90b11c97f848&mac=08:00:27:98:51:8D&newService&json
I’ll give this a try now! I had issues with the ‘Reset encryption Data’ button previously when my original master image didnt want to speak to my FOG server. I’ve also removed that host out of the group I had it in, just in case there was any conflicts. I’ll keep you guys posted, thanks for the help
Yeah its all enabled in there, I saw a post saying to disable them and re-enable and I tried that, but no luck. I’ll go through it again though
So I’ve had luck with one client changing name. My original image was named something different, then I noticed the hostname changed at some point after installing the client. Now my issue is, after capturing that image and deploying it on both a virtual machine and an actual machine, it keeps the old hostname of the previous computer.
My fog.log reads
//3/15/2019 4:18 PM Client-Info Version: 0.11.16
3/15/2019 4:18 PM Client-Info OS: Linux
3/15/2019 4:18 PM Middleware::Authentication Waiting for authentication timeout to pass
3/15/2019 4:20 PM Middleware::Communication Download: http://192.168.10.138/fog/management/other/ssl/srvpublic.crt
3/15/2019 4:20 PM Data::RSA FOG Server CA cert found
3/15/2019 4:20 PM Middleware::Authentication Cert OK
3/15/2019 4:20 PM Middleware::Communication POST URL: http://192.168.10.138/fog/management/index.php?sub=requestClientInfo&authorize&newService
3/15/2019 4:20 PM Middleware::Response Invalid host
3/15/2019 4:20 PM Middleware::Communication URL: http://192.168.10.138/fog/service/register.php?hostname=90b11c97f848&mac=08:00:27:98:51:8D&newService&json
Quick edit: I found this as well.
------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
3/15/2019 4:45 PM Client-Info Client Version: 0.11.16
3/15/2019 4:45 PM Client-Info Client OS: Linux
3/15/2019 4:45 PM Client-Info Server Version: 1.5.5
3/15/2019 4:45 PM Middleware::Response Module is disabled on the host
------------------------------------------------------------------------------
------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
3/15/2019 4:45 PM Client-Info Client Version: 0.11.16
3/15/2019 4:45 PM Client-Info Client OS: Linux
3/15/2019 4:45 PM Client-Info Server Version: 1.5.5
3/15/2019 4:45 PM Middleware::Response Module is disabled on the host
------------------------------------------------------------------------------
------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
3/15/2019 4:45 PM Client-Info Client Version: 0.11.16
3/15/2019 4:45 PM Client-Info Client OS: Linux
3/15/2019 4:45 PM Client-Info Server Version: 1.5.5
3/15/2019 4:45 PM Middleware::Response Module is disabled globally on the FOG server
3/15/2019 4:45 PM PrinterManager Module is not compatible with Linux
------------------------------------------------------------------------------
------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
3/15/2019 4:45 PM Client-Info Client Version: 0.11.16
3/15/2019 4:45 PM Client-Info Client OS: Linux
3/15/2019 4:45 PM Client-Info Server Version: 1.5.5
3/15/2019 4:45 PM Middleware::Response Module is disabled on the host
------------------------------------------------------------------------------
------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
3/15/2019 4:45 PM Client-Info Client Version: 0.11.16
3/15/2019 4:45 PM Client-Info Client OS: Linux
3/15/2019 4:45 PM Client-Info Server Version: 1.5.5
3/15/2019 4:45 PM Middleware::Response Module is disabled on the host
------------------------------------------------------------------------------