Reports to Audit for GDPR compliance
This listing contains 4 different reports. The main one called GDPR Compliance will help overlook the security aspect of your environment. It will provide a quick look at the Antivirus status, Anti-Malware status, the VSA Users, the local Admins and patch status of your environment.
Three more reports are to provide a more detailed summary of Antivirus, Anti-Malware and the patch status of all endpoints.
The reports show some poor information, not very logical or useful. Will be looking into this a lot more. Reports do work fine in Kaseya 9.3, which is great. Do heed the Review below by Decio to find out where your reports can be found after the import.
I imported the set flawlessly into our Kaseya 184.108.40.206 from the menu System -> Server Management -> Import Center After the import you will find them on Info Center -> Reporting -> Reports in the Shared Tree, under myReports - Administrator -> GDPR branch.
Three of the reports don't import into 220.127.116.11
Doesn't import into 18.104.22.168.
Same here with 22.214.171.124.. Unexpected error - System.ApplicationException: The message key 'ReportDesignerInstanceAddFailed for : Failed to retrieve DataSet 'AV Summary' at Kaseya.ImportCenter.Report.ReportDesignerDataSetInstance..ctor(XmlNode reportDataSetInstanceNode, Decimal partitionId) at Kaseya.ImportCenter.Report.ReportDesignerInstance..ctor(XmlNode reportInstanceNode, Decimal partitionId) at Kaseya.ImportCenter.Report.ReportImporter.ImportCustomReport(XmlNode reportNode, Boolean systemLoad, ImportResponse response, Boolean overRide, Int32 sortOrder, String treeFullPath) ' is not in the message file ImportCenter/ImportCenterMessages.xml at Kaseya.ImportCenter.MessageMap.GetMessage(String key) at Kaseya.ImportCenter.ViewImportLogDetail.LoadGrid()
The reports were created on a 126.96.36.199 server, it may be using report parts that you are currently missing. From the error message you are getting, you are missing the "AV Summary" report parts which prevents the import. I would suggest updating the VSA to the latest version, or opening a ticket with support to find out why the import is failing.