I agree. There should be a delete all power management entries on the group power management screen.

I installed it fresh on a client without all of the CAD programs and it worked. So it is not a 10 Enterprise problem.

I then did a fresh install on the client - Deleting the FOG program folder and re-installing (and resetting the Encryption key). And this also has worked.

I have updated the server copy and I am sysprepping right now. I will let you know the results in about an hour.

I kept getting fatal errors on the httpd startup (Error 2) during installation.

I found that if I put a ‘sleep 2’ between the ‘service httpd restart’ and the ‘service httpd status’ in the redhat functions library then it would complete the httpd installation.

I am now getting errors during installation of the SVN trunk on a Red Hat 6.6 system. I found that $linuxReleaseName and $OSVersion are not being set correctly in bin/.install.sh

Here are the files and contents that those variables depend on.

[root@clstfogi ~]# ls -ld /etc/*release*
-rw-r--r--. 1 root root  152 Jun 17 10:42 /etc/lsb-release
drwxr-xr-x. 2 root root 4096 Jun 17 10:42 /etc/lsb-release.d
-rw-r--r--. 1 root root   55 Sep 15  2014 /etc/redhat-release
lrwxrwxrwx. 1 root root   14 Jun 17 10:41 /etc/system-release -> redhat-release
-rw-r--r--. 1 root root   49 Sep 15  2014 /etc/system-release-cpe
[root@clstfogi ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.6 (Santiago)

If you notice that both the name is being set as ‘Red’, not Redhat. And the version is coming from an incorrect file (/etc/lsb-release). What I did was to add the check for Red and set the correct values:

else
        linuxReleaseName=`cat /etc/system-release 2>/devnull | head -n1 | awk '{print $1}'`;
    if [[ "$linuxReleaseName" == "Red" ]]; then
        linuxReleaseName="Redhat";
        OSVersion=`awk -F'[^0-9]*' /[Rr]elease*\([^.]*\).*/'{print $2}' /etc/redhat-release | head -n1`
    fi
fi

I did not check this into the SVN because I had to change the /etc/release to /etc/system-release. I guess that we need to do another check like the /etc/os-release for the /etc/system-release link before falling through to the default one.

3642 fixes this.

Here is the whole paragraph that should be production ready. I think that it will work with Centos too. I basically added the code from the elif to the else.

if [ -f "/etc/os-release" ]; then
        linuxReleaseName=`sed -n 's/^NAME=\(.*\)/\1/p' /etc/os-release | tr -d '"'`;
    OSVersion=`sed -n 's/^VERSION_ID=\([^.]*\).*/\1/p' /etc/os-release | tr -d '"'`;
elif [ -f "/etc/system-release" ]; then
    linuxReleaseName=`cat /etc/system-release 2>/dev/null | head -n1 | awk '{print $1}'`;
    if [[ "$linuxReleaseName" == "Red" ]]; then
        linuxReleaseName="Redhat";
    fi
    OSVersion=`awk -F'[^0-9]*' /[Rr]elease*\([^.]*\).*/'{print $2}' /etc/system-release | head -n1`
else
    linuxReleaseName=`cat /etc/*release* 2>/dev/null | head -n1 | awk '{print $1}'`;
fi

I have 250 computers that apparently need their Encryption Data reset. The reset encryption data option would be nice on the group management window.

Here are the values assigned on the 3619 SVN:

linuxReleaseName = LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
OSVersion =

The current fix does not work as the /etc/<star>release<star> pulls up unwanted files.

Works okay in fog version 3642

The FOGScheduler logs just show my 7 scheduled cron wake up jobs. I have disabled all of the FOG services and they still started up. Thus it does not appear to be FOG. I am trying to get a hold of a network analyzer to trace who is really sending this signal. Thanks for your help in understanding how FOG works, it has helped me narrow down who is causing the problem.

I know it is a WOL being sent as my boot is SSD, then IP/PXE and it is PXE booting. Also, it is only happening in one of my three buildings. And only about 1/3 to 1/2 of the computers that I have in that building. So it looks like I have a rogue server somewhere in that building.

I did not receive any packets from the server subnet using your tcpdump command. Unfortunately the computers in question are on a different subnet. I know that it is a WOL packet since the following shows up in the server messages log:

Dec 16 23:04:02 clstfogi in.tftpd[16975]: tftp: client does not accept options
Dec 16 23:04:02 clstfogi in.tftpd[16976]: Client 10.4.134.75 finished undionly.kpxe
Dec 16 23:04:07 clstfogi in.tftpd[17006]: tftp: client does not accept options
Dec 16 23:04:07 clstfogi in.tftpd[17007]: Client 10.4.134.78 finished undionly.kpxe
Dec 16 23:04:09 clstfogi in.tftpd[17053]: Client 10.4.134.75 finished default.ipxe
Dec 16 23:04:14 clstfogi in.tftpd[17111]: Client 10.4.134.78 finished default.ipxe

The computers all boot to the SSD, but have WOL+PXE boot enabled. So I should not see anything unless it is a WOL boot. So it does not appear to be a FOG issue, but rather a rogue server on that subnet.

Found about 140 rows, but they still turn back on. I even rebooted to make sure that nothing was in memory.

There are only two scheduled tasks for deploying snapins to other computers. Power management only shows a scheduled 11pm shutdown, but then turn back on 15 min later.

I have FOG 1.4.4 on RedHat and most everything seems to be working okay. Except that I have a number of hosts that get turned back on by FOG about 10-20 min after I shut them down (either manually, remote desktop, or via FOG power management). I have not been able to find anything in FOG’s logs to indicate that this is happening. I assume that I have something in my database that is causing this since is only happening on 35 of 280 computers. Any ideas of where to look?

The error that I had was a firefox problem.

What privileges do I need to upload a picture?

Windows 10

How do you do that? It is whatever it loaded when the client updated. In the Programs and Features list there is no .net less than 4.5.

I have a client with 2 power management cron jobs and the following error happens when I reimage the client:

------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 8/17/2016 9:26 AM Client-Info Client Version: 0.11.5
 8/17/2016 9:26 AM Client-Info Client OS:      Windows
 8/17/2016 9:26 AM Client-Info Server Version: 1.3.0-RC-8
 8/17/2016 9:26 AM Middleware::Response Success
 8/17/2016 9:26 AM PowerManagement ERROR: Data conversion using the DataContract FOG.Modules.DataContracts.PowerManagement failed
 8/17/2016 9:26 AM PowerManagement ERROR: Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.List`1[FOG.Modules.PowerManagement.Task]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'tasks.1'.

I am not sure if this is a client and/or server issue.