release date options for computer compliance
Believe it or not I just recently changed the 'Release date From:' other than the deault in the Windows Compliance by computer report. (see screenshot). After thinking a load of machines were 100% compliant - i changed this from 1 years previous patches (which it seems to default to ) to patches from 2000. Doh! it now updates reports with a sh*tload of patches I didn't know about. whats the point in this field? Your machine is either fully patched or not. Why have a default that only goes back 1 year and shows machines 100% compliant if they have that years patches when old patches might not be in compliance.!
so, my question is - I have a load of patches that have not been staged and downloaded. I have downloaded and staged a few and tested on a few servers. Now because they aren't all neatly sequential/together Its difficult to combine a lot into the one policy. I also notices that when applied to a server they seem to update some, want a reboot, install more patches later on at random times, require a reboot, same again. Just when I thought this software couldn't get worse, and belive me, ITS BUGTASTIC,...
Anyone any ideas on resolving this quickly..... OTHER THAN GET SCCM and ms tools!