/build/static/layout/Breadcrumb_cap_w.png
05/31/2017 1362 views
Hi guys,

It's probably a little late for this to be of use to anyone now but I wrote this report help with the reporting of our MS17-010 patching.

I used this article as the basis of the report. https://support.microsoft.com/en-us/help/4023262/how-to-verify-that-ms17-010-is-installed

I'm curious if anyone else can run this report and get the expected results. And if it does work, why didn't Quest release this report themselves?

Oh and if i made any stupid mistakes, please let me know (nicely). :)
https://pasgroup-my.sharepoint.com/personal/andrewc_pasgroup_onmicrosoft_com/_layouts/15/guestaccess.aspx?docid=0a4c5b35672e74788bcf517fe66a8a727&authkey=Ad2d0FH5ptFcF1U9Q_jdvzg

EDIT: For the uninitiated, to import this report, save the report to your 'client' share on your K1000. The in the Admin console in your K1000, go to Settings > Resources > Import. Then click the 'Choose action' menu in the top left corner of the main window pane > Import from network share. If you save the file to your K1000 correctly in the previous step, you should be able to find it in the list that you presented with. (Well, this is how it works in our environment anyway. Hopefully, yours is similar and this helps you get the job done.☺ )

Cheers,
AC

0 Comments   [ + ] Show comments

Comments


All Answers

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
0

I can run the report fine. If the purpose is to find non-complaint machines, then the report is backwards: it shows all that have it installed instead of those missing it.

Quest did create a KB article about it: https://support.quest.com/kace-systems-management-appliance/kb/229420

Answered 06/06/2017 by: JasonEgg
Red Belt

  • Nope, it's not backwards in my mind. It's a *compliance* report. It's written to show me all the computers on the networks that have the MS17-010 installed.

    I would call what you are suggesting a non-compliance report. I have written one of those too but I haven't shared it.

    Yeah I am aware of the article Quest created but it would have been much clearer if a report like this (or the inverse which i haven't shared) was shared with us. We could have seen at a glance how protected/exposed we are.

    EDIT: Doh! Now I see the report they shared via link in that article. >_< Still, it doesn't cover all the patches from Microsoft, only 4 of the 30.
    • Thank you very much for shareing the compliance report. Helped me al lot.

      Would you be so kind to share your inverse compliant report as well?

      Thank you,
      RZ

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share