Mbam windows5/17/2023 I continued to work with Microsoft Product Group and particularly Frederic Mokren (thanks Frederic) until we figured out my issues.įirst of all I could see the issue with reading reports in the above screenshots, but further digging revealed permission denied errors on the ConfigMgr database. I alerted the Microsoft Product Group about this and a known issues was appended to the release notes, however the suggested workaround didn’t solve my reporting issues. (rsProcessingAborted)Īt .ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)Īt .InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)Īt .RenderServerReport(ServerReport report)Īt .PerformOperation()Īt .AsyncReportOperationWrapper.PerformOperation()Īt .ProcessThreadMain(Object arg) Sadly however when I tried to run any of them I got an error: Īn error has occurred during report processing. That release contained a bunch of reports for MBAM located in the Reporting node shown below. In a later Technical Preview (TP1909), reporting ability was added to the Reporting node in ConfigMgr and I blogged about that here. A brief history of my MBAM reporting experiences in ConfigMgr However, reporting capabilities were not included. It finally brought together native integration of MBAM within ConfigMgr for on premises devices. Initially, when TP1905 shipped with MBAM integrated, there was a lot of excitement about this new integration within ConfigMgr. Microsoft have been hard at work adding MBAM (Microsoft BitLocker Management and Monitoring) features natively to Microsoft Endpoint Manager Configuration Manager, and those features have been improved since they were first released, with bug fixes and new features added over time.
0 Comments
Leave a Reply. |