A malware report is only useful if the people with the power to address an issue can access the report. One of the paradigms of integrating your anti-virus with SCCM is the fact that many more people in an organization will now need access to SCCM. While the new role-based privileges alleviate this pain point somewhat, there will likely be some individuals with whom you just are not comfortable giving access to the SCCM console,who will need to access SCEP reporting data.
Luckily, this can be addressed by granting them access to the SCEP reports within SQL Reporting Services. This recipe will walk you through the procedure for doing so.
For this recipe, you will need to utilize an account that has administrator privileges for the SQL Reporting Services instance that is hosting your SCCM reports. This recipe is written from the perspective of being logged into the server that is hosting the reports and running IE locally. The procedure can also be done remotely; just replace localhost with the DNS name of the server.
In order to be able to deliver report subscriptions over email, it is required that the SMTP information has been entered into the SQL Reporting Services Configuration Utility and that the corresponding Exchange server allows for the SQL reporting services server to send SMTP traffic through its SMTP connector.
Follow these steps:
ConfigMgr_XXX
(XXX representing your site code) and then selecting the Endpoint Protection
directory.SQL Reporting Services provides an ideal platform for SCEP reports, because it allows you easily assign access to an Active Directory user or a group and can be relied upon to deliver reports on a schedule. Keeping your admins from setting up an Outlook rule to automatically place the e-mails in the recycling bin is another matter entirely.