Search the Community
Showing results for tags 'sccm 1806'.
-
My reports are not showing up under my console. (Monitoring, Reporting, Reports). I've added Administrator User for the Reporting. And created a custom role for this purpose. When I go to reports in the console, it shows as: http://sccm2016/Reports_SCCMTEST16, and when it attempts to open, it gives this error: The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. (rsReportServerDisabled) Get Online Help Keyset does not exist (Exception from HRESULT: 0x80090016) this is a fresh install, so I do not have a backup. The name of the server is sccm2016; how can I get that changed, maybe that's the issue, but I don't think it is. In the Site Status, (Site System Role: Reporting Services Point - the error shows: The report server service is not running on Reporting Service Point server "sccm2016.xxx.xxx"; start the service to enable reporting. - Which I have done, multiple times. Am I able to uninstall SQL without uninstalling SCCM?
- 3 replies
-
- sql server 2017
- sccm 1806
-
(and 1 more)
Tagged with:
-
Hi, I've updated to 1806 with all the hot fixes applied and decided to turn on "Enable a PXE responder without Windows Deployment Service" unfortunately it doesn't work and I've had to turn WDS back on which works. Below is the lines from the SMSPXE log. We have IP Helpers rather than using DHCP Scope options. PXE: BC:83:85:F5:0B:63: Parsed a discover/solicit packet. 17/10/2018 16:24:14 PXE: BC:83:85:F5:0B:63: C76B7D02-EA50-B10F-5E89-8BEFAA6609C9: Client is 64-bit, UEFI, Firmware. 17/10/2018 16:24:14 PXE: BC:83:85:F5:0B:63: Prioritizing local MP http://(our MP). 17/10/2018 16:24:14 Not in SSL 17/10/2018 16:24:14 Not in SSL 17/10/2018 16:24:14 Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="15673" ClientID="GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="1"/><ClientIDInfo ItemKey="16798564" ClientID="GUID:39A05B11-0A61-4CB5-8827-5052E9CD3191" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="2"/></ClientIDReply> 17/10/2018 16:24:14 PXE: BC:83:85:F5:0B:63: System records: 17/10/2018 16:24:14 PXE: BC:83:85:F5:0B:63: 15673, GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E, SMBIOS ID is a match, MAC Address is NOT a match. 17/10/2018 16:24:14 PXE: BC:83:85:F5:0B:63: 16798564, GUID:39A05B11-0A61-4CB5-8827-5052E9CD3191, SMBIOS ID is NOT a match, MAC Address is a match. 17/10/2018 16:24:14 PXE: BC:83:85:F5:0B:63: Using system record 15673, GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E. 17/10/2018 16:24:14 PXE: Sending reply to 255.255.255.255, DHCP. 17/10/2018 16:24:14
- 8 replies
-
- sccm 1806
- pxe responder
-
(and 1 more)
Tagged with: