@mp12 I noticed your topic is marked as solved when its not really solved you are just using a work around.

@Joe-Schmitt said in Trunk 5735 PC doesnt restart after joining the domain.:

This issue has been addressed in v0.11.2. Please test when you get a chance.

The Update worked for me Joe, Thanks!

@wayne-workman
That Worked!

[root@10fogserver MonitorFogStorageNodes]# git log -1
commit bb920e4367b5076ac2bb7bb70575ec4b647d5aee
Author: wayneworkman <13314799+wayneworkman@users.noreply.github.com>
Date:   Wed Feb 21 13:53:10 2018 -0600

    Fix spacing in evaluations
[root@10fogserver MonitorFogStorageNodes]# ./MonitorNodes.sh
[root@10fogserver MonitorFogStorageNodes]#

Thanks @Wayne-Workman

@sebastian-roth I don’t know how that happened but I copied the srvpublic.crt from a backup and it is fixed.

Thanks for all the help

I am trying to deploy snapins from our Storage nodes and I am getting an error in the fog.log.

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 7/21/2016 1:40 PM Client-Info Client Version: 0.11.4
 7/21/2016 1:40 PM Client-Info Client OS:      Windows
 7/21/2016 1:40 PM Client-Info Server Version: 1.3.0-RC-1
 7/21/2016 1:40 PM Middleware::Response Success
 7/21/2016 1:40 PM SnapinClient Snapin Found:
 7/21/2016 1:40 PM SnapinClient     ID: 378
 7/21/2016 1:40 PM SnapinClient     Name: 01 - TeamViewer
 7/21/2016 1:40 PM SnapinClient     Created: 2016-07-21 13:39:35
 7/21/2016 1:40 PM SnapinClient     Action:
 7/21/2016 1:40 PM SnapinClient     Pack: False
 7/21/2016 1:40 PM SnapinClient     Hide: False
 7/21/2016 1:40 PM SnapinClient     Server: http://192.168.18.39/fog
 7/21/2016 1:40 PM SnapinClient     TimeOut: 0
 7/21/2016 1:40 PM SnapinClient     RunWith: cmd.exe
 7/21/2016 1:40 PM SnapinClient     RunWithArgs: /c
 7/21/2016 1:40 PM SnapinClient     Args:
 7/21/2016 1:40 PM SnapinClient     File: TeamViewer-AllSites.sfx.exe
 7/21/2016 1:40 PM Middleware::Communication Download: http://192.168.18.39/fog/service/snapins.file.php?mac=C0:3F:D5:9C:6C:36||00:00:00:00:00:00:00:E0&taskid=378
 7/21/2016 1:40 PM SnapinClient C:\Program Files (x86)\FOG\tmp\TeamViewer-AllSites.sfx.exe
 7/21/2016 1:40 PM SnapinClient ERROR: Hash does not match
 7/21/2016 1:40 PM SnapinClient ERROR: --> Ideal: 9B87981143F24BF592603402DE7D6F5E8B6BDCC97F37328C8474DB95635C07CAF792B8ECCE422A6235AE3F130E717417B902059580C62314E4026BBEC9889E4B
 7/21/2016 1:40 PM SnapinClient ERROR: --> Actual: 7FF6B7E4378EC39EFFC8A042F445AA6618E765B6F39C8BC53FA5F1E3A5924129F239A6CA0FD7C0350D63C808EFB2FD3E18D48EE6A151C75CCA4C3D1E0B6A2A23
 7/21/2016 1:40 PM Middleware::Communication URL: http://10fogserver/fog/service/snapins.checkin.php?taskid=378&exitcode=-1&mac=C0:3F:D5:9C:6C:36||00:00:00:00:00:00:00:E0&newService&json
------------------------------------------------------------------------------

Although: http://18fogserver/fog/status/getsnapinhash.php?filepath=/opt/fog/snapins/TeamViewer-AllSites.sfx.exe Returns

9b87981143f24bf592603402de7d6f5e8b6bdcc97f37328c8474db95635c07caf792b8ecce422a6235ae3f130e717417b902059580c62314e4026bbec9889e4b|10239200

Remote Node

[root@18fogserver snapins]# sha512sum TeamViewer-AllSites.sfx.exe
9b87981143f24bf592603402de7d6f5e8b6bdcc97f37328c8474db95635c07caf792b8ecce422a6235ae3f130e717417b902059580c62314e4026bbec9889e4b  TeamViewer-AllSites.sfx.exe

Our Main Fogserver

root@10fogserver:/opt/fog/snapins $ sha512sum TeamViewer-AllSites.sfx.exe
9b87981143f24bf592603402de7d6f5e8b6bdcc97f37328c8474db95635c07caf792b8ecce422a6235ae3f130e717417b902059580c62314e4026bbec9889e4b  TeamViewer-AllSites.sfx.exe

Thanks Tom for helping me troubleshoot this.

Here is a Video showing an example.

I prefer Centos so my instructions are based on Centos.

# yum update && yum install conspy

Follow the instructions here to modify the Init Image:
Modifying the Init Image

Once you have the init image extracted and mounted, add your ssh key.

cd /var/www/{html,}/fog/service/ipxe/initmountdir
cd root
mkdir .ssh
/bin/echo "==yoursshkeystringgoesbetweenthequotes==" >> .ssh/authorized_keys

copy Conspy to the image:

cp /usr/bin/conspy /var/www/{html,}/fog/service/ipxe/initmountdir/bin
cp /usr/lib64/libncurses.so.x /var/www/{html,}/fog/service/ipxe/initmountdir/lib64
cp /usr/lib64/libncurses.so.x.x /var/www/{html,}/fog/service/ipxe/initmountdir/lib64
cp /usr/lib64/libncursesw.so.x /var/www/{html,}/fog/service/ipxe/initmountdir/lib64
cp /usr/lib64/libncursesw.so.x.x /var/www/{html,}/fog/service/ipxe/initmountdir/lib64
cp /usr/lib64/libtinfo.so.x /var/www/{html,}/fog/service/ipxe/initmountdir/lib64
cp /usr/lib64/libtinfo.so.x.x /var/www/{html,}/fog/service/ipxe/initmountdir/lib64

replace x in libncurses++.so.x with the version of libcurses you have installed.
Follow the instruction on how to recompress the image and you’re done.

ssh to the PC and login as root.
run the conspy command to view the progress.

@Wayne-Workman contents of /tmp/whoami.txt is “root”

@wayne-workman
Thanks I will truncate the snapins.sHash table.

UPDATE snapins SET sHash=NULL;

Re: Using Conspy to View remote PC imaging progress

Here is the script I use to install conspy on the fogserver/storage nodes.

yum install conspy -y
echo -e '#(>)##### UnPacking Init.xz #####'
cd /var/www/fog/service/ipxe/
xz -d init.xz
mkdir initmountdir

echo -e '#(>)##### Mounting Init #####'

mount -o loop init initmountdir
cd /var/www/fog/service/ipxe/initmountdir
rm -f root/.ssh/authorized_keys
#### Install SSH Keys
echo -e '#(>)##### Installing SSH Keys #####'

needreload=0
if [ ! -d root/.ssh ]; then
    echo -e '#(->)Creating SSH File'

    # Create the autorized keys and add the keys
    mkdir root/.ssh
    touch root/.ssh/authorized_keys
    # ssh Keys

    /bin/echo 'ssh-rsa rrrrrrrrrrreeeeeeeeeeeeeeaaaaaaaaaaaaallllllllllllyyyyyyyyyylllllllloooooooooonnnnnnnnnnnggggggggggkkkkkkkkeeeeeeeyyyyyy11111111' >> root/.ssh/authorized_keys
    /bin/echo 'ssh-rsa rrrrrrrrrrreeeeeeeeeeeeeeaaaaaaaaaaaaallllllllllllyyyyyyyyyylllllllloooooooooonnnnnnnnnnnggggggggggkkkkkkkkeeeeeeeyyyyyy22222222' >> root/.ssh/authorized_keys
else
    if [ ! -f root/.ssh/authorized_keys ]; then
        echo -e '#(->)Creating new SSH File'

    # Add all the keys
    touch root/.ssh/authorized_keys
    /bin/echo 'ssh-rsa rrrrrrrrrrreeeeeeeeeeeeeeaaaaaaaaaaaaallllllllllllyyyyyyyyyylllllllloooooooooonnnnnnnnnnnggggggggggkkkkkkkkeeeeeeeyyyyyy11111111' >> root/.ssh/authorized_keys
    /bin/echo 'ssh-rsa rrrrrrrrrrreeeeeeeeeeeeeeaaaaaaaaaaaaallllllllllllyyyyyyyyyylllllllloooooooooonnnnnnnnnnnggggggggggkkkkkkkkeeeeeeeyyyyyy22222222' >> root/.ssh/authorized_keys
    fi
fi

echo -e '#(>)##### Coping ConSpy #####'

rsync -avh --progress /usr/bin/conspy /var/www/fog/service/ipxe/initmountdir/bin
rsync -avh --progress /usr/lib64/libncurses.so.6 /var/www/fog/service/ipxe/initmountdir/lib64
rsync -avh --progress /usr/lib64/libncurses.so.6.1 /var/www/fog/service/ipxe/initmountdir/lib64
rsync -avh --progress /usr/lib64/libncursesw.so.6 /var/www/fog/service/ipxe/initmountdir/lib64
rsync -avh --progress /usr/lib64/libncursesw.so.6.1 /var/www/fog/service/ipxe/initmountdir/lib64
rsync -avh --progress /usr/lib64/libtinfo.so.6 /var/www/fog/service/ipxe/initmountdir/lib64
rsync -avh --progress /usr/lib64/libtinfo.so.6.1 /var/www/fog/service/ipxe/initmountdir/lib64

echo -e '#(>)##### Coping Nano #####'
rsync -avh --progress /usr/bin/nano /var/www/fog/service/ipxe/initmountdir/bin

echo -e '#(>)##### Re-Packing Init.xz #####'

cd /var/www/fog/service/ipxe/
umount initmountdir
rmdir initmountdir
xz -C crc32 -9 init
chown fogproject:apache init.xz

#ls -al
echo -e '#(-)##### Completed #####'
cd /root

@Sebastian-Roth Thank you!

@sebastian-roth said in Boot Porteus Kiosk iso from fog pxe menu:

@Greg-Plamondon From what I read you can’t really install the kiosk client. Maybe I missed that part. But the FAQ states that you can customize the ISO file.

For PXE booting, have you tried memdisk iso booting yet? Thou this is legacy BIOS mode only:

initrd http://${fog-ip}/path/to/porteus.iso
chain memdisk iso raw
boot || goto MENU

Edit: Quickly extracted the ISO and found this in boot/pxelinux.cfg/default:

label pxe
kernel vmlinuz
append initrd=initrd.xz,pxelinux.cfg/initrdpxe.xz quiet http_server=

So you might be able to boot the extracted ISO. But on the other hand we don’t know too much about the kernel parameters for network booting this beside the litte information on their website: https://porteus-kiosk.org/pxe-server.html

Be aware that FOG is not using pxelinux anymore. We use iPXE now and while you can do many more things with iPXE it’s not always possible to translate things over from the old pxelinux.

Thanks @Sebastian-Roth for looking into this for me. I guess I will stick the the USB stick installs for now.

We use Porteus Kiosk for our open enrollment process. instead of inserting a USB stick and installing the kiosk, I would like to install it from PXE.
If someone could help me with this it would be greatly appreciated.

After uploading the FOG Banner image, the fields are empty for both:
FOG_CLIENT_BANNER_IMAGE
FOG_CLIENT_BANNER_SHA
in the GUI.

When accessing the user reports section I get the following message:

Could I please have Wiki access?
Thanks.

the Force Reboot option does not update the DB “hostEnforce” value stays at ‘0’ if you manually set it to ‘1’ in the database the GUI shows it checked and unchecking it returns the value to ‘0’ as expected.

The browse for file dialogue window does not appear.

Keep up the good work the new interface looks amazing!

Is there any way that I can see what fog clients are having issues with the fogserver?
I have come across multiple clients recently that have not been checking in for user reports. A simple resetting of the Encryption Data in the GUI fixed the issue. If there was a report I could run that displayed the last successful check-in of the clients I think that would help.

@sebastian-roth yes I believe that was the case. I don’t remember the record count as I already purged data older than 30 days. I set up a SQL event that runs daily.

DELETE from userTracking WHERE utDate < now() - interval 30 DAY;

I can now run the reports

any time I try and use the user tracking to find what PC a user is logged into I get:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

The apache error.log:

[Wed Apr 07 09:39:23.233725 2021] [proxy_fcgi:error] [pid 23644] (70007)The timeout specified has expired: [client 192.168.10.170:49336] AH01075: Error dispatching request to :, referer: http://10fogserver.xxxxxxx.com/fog/management/index.php?node=report