Demo report — entirely fictitious data (site “PS1”, 36 invented machines), produced by the script itself by replaying a test set. No customer data.
← Back to the tool
LB IT Cloud · Health check and security posture of the Configuration Manager sitev1.72.2

MECM health check

Site PS1 — Primary site - SYNTHETIC (5.00.9128.1000)

Customer
Contoso (fictitious)
Captured
2026-09-24 06:00 UTC
Source
AdminService (https://replay/AdminService/wmi)
SMS Provider
CM01.corp.local

Is this Configuration Manager site working, and is it safe. Read live from the site itself, plus whatever the hardening collector last brought back from the site server.

Everything on this page is read-only. The script queries the site and reads settings; it changes nothing, deploys nothing and touches no client.

Not returned by the site, so the checks over them report as unmeasured: SMS_SCI_Component, SMS_SCI_SiteDefinition, SMS_BootImagePackage, SMS_StatusMessage (history).

Critical

20

Attention

76

OK

151

To verify

85

not gradeable automatically

Checks passing

61%

151 of 247 graded checks pass

Every check, by status

332
Critical 20Attention 76OK 151To verify 85

Where it stands, by area of the site

Site1
Roles and components9
Deployments3
Content distribution3
Software updates3
Collections3
Status messages3
Administration1
Client push3
Accounts1
Client communication3
OS deployment and PXE4
Boundaries3
Infrastructure9
Shares16
Local accounts25
Password policy15
Services23
Network protocols30
Firewall15
NTLM15
Credential protection25
Remote Desktop9
WinRM10
Endpoint protection15
Operating system updates5
Auditing5
PowerShell20
System20
TLS30
Active Directory5
CriticalAttentionOKTo verify

To deal with first, across every area

96 to deal with
  • Critical

    Site system role · SMS Distribution Point — DP-LYON.corp.local

    Configuration Manager reports SMS Distribution Point on DP-LYON.corp.local at status 2 (0 healthy, 1 warning, 2 critical).

    Open Monitoring, then Site Status, for the messages this role has recorded.

  • Critical

    Site component · SMS_DISTRIBUTION_MANAGER — CM01

    SMS_DISTRIBUTION_MANAGER on CM01 is at status 2, with 37 error(s) and 5 warning(s) over the summary interval.

    Open Monitoring, then Component Status, and read this component’s recent messages.

  • Critical

    Deployment failure rate · Contoso CAD 2026 → Engineering laptops

    39 of 64 targets failed (60.9%). Succeeded 22, in progress 1, no answer 2.

    Open this deployment under Monitoring, then Deployments, and work back from the error codes the clients returned.

  • Critical

    Failed distribution · PS100001 — DP-LYON.corp.local

    Package PS100001 could not be placed on DP-LYON.corp.local and is no longer being retried (state 3).

    Redistribute the package to this distribution point, and check the disk space and the content library on it.

  • Critical

    Automatic deployment rule failing · Defender definitions

    Defender definitions last ran on 2026-09-22 01:00 UTC and ended with error 0x87D01101.

    Re-run the rule by hand and read the error it returns; a rule that has failed silently deploys nothing at all.

  • Critical

    Task sequence deployed to a built-in collection · Windows 11 24H2 build → All Unknown Computers

    The task sequence Windows 11 24H2 build is deployed to All Unknown Computers, which is a built-in collection rather than a chosen population.

    Deploy the task sequence to a collection built for it, and make it available rather than required.

  • Critical

    Free space on a drive · DP-LYON.corp.local — E:

    E: on DP-LYON.corp.local has 2.8% left — 11.0 GB of 400 GB.

    Free space on the content library, or move the library to a larger volume. A distribution point that fills up fails the packages it is asked for without failing itself.

  • Critical

    Wide directory group in the local administrators · RPT01 — CORP\Domain Admins

    CORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.

    Remove the group and use one dedicated to administering this server.

  • Critical

    Wide directory group in the local administrators · DP-NANTES — CORP\Domain Admins

    CORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.

    Remove the group and use one dedicated to administering this server.

  • Critical

    Wide directory group in the local administrators · DP-LYON — CORP\Domain Admins

    CORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.

    Remove the group and use one dedicated to administering this server.

  • Critical

    Guest account · DP-LYON — Guest

    The guest account Guest is enabled.

    Disable the guest account.

  • Critical

    SMBv1 protocol · DP-LYON

    SMBv1 is enabled on this server.

    Remove SMBv1: the protocol is obsolete and unauthenticated attacks against it are public.

  • Critical

    Windows Firewall profile · DP-LYON — Domain

    The Domain profile is disabled.

    Turn the firewall back on for this profile.

  • Critical

    Windows Firewall profile · DP-LYON — Private

    The Private profile is disabled.

    Turn the firewall back on for this profile.

  • Critical

    WDigest credential caching · DP-LYON

    WDigest is enabled, so plain-text passwords can sit in memory.

    Set UseLogonCredential to 0 so credentials stop being cached in clear text.

  • Critical

    Automatic logon · DP-LYON

    Automatic logon is configured and its password sits in the registry in clear text.

    Turn off automatic logon on a production server, and change the password immediately if one is stored.

  • Critical

    Network Level Authentication · DP-LYON

    Network Level Authentication is not required, so the logon screen is reachable before anyone authenticates.

    Require Network Level Authentication, so an unauthenticated caller never reaches the session host.

  • Critical

    Wide directory group in the local administrators · SQL01 — CORP\Domain Admins

    CORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.

    Remove the group and use one dedicated to administering this server.

  • Critical

    Windows Firewall profile · SQL01 — Domain

    The Domain profile is disabled.

    Turn the firewall back on for this profile.

  • Critical

    Wide directory group in the local administrators · CM01 — CORP\Domain Admins

    CORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.

    Remove the group and use one dedicated to administering this server.

  • Attention

    Site system role · SMS Software Update Point — CM01.corp.local

    Configuration Manager reports SMS Software Update Point on CM01.corp.local at status 1 (0 healthy, 1 warning, 2 critical).

    Open Monitoring, then Site Status, for the messages this role has recorded.

  • Attention

    Site system role · Storage Object — SQL01.corp.local

    Configuration Manager reports Storage Object on SQL01.corp.local at status 1 (0 healthy, 1 warning, 2 critical).

    Open Monitoring, then Site Status, for the messages this role has recorded.

  • Attention

    Site component · SMS_WSUS_SYNC_MANAGER — CM01

    SMS_WSUS_SYNC_MANAGER on CM01 is at status 1, with 0 error(s) and 3 warning(s) over the summary interval.

    Open Monitoring, then Component Status, and read this component’s recent messages.

  • Attention

    Site component · SMS_SRS_REPORTING_POINT — RPT01

    SMS_SRS_REPORTING_POINT on RPT01 is at status 1, with 0 error(s) and 2 warning(s) over the summary interval.

    Open Monitoring, then Component Status, and read this component’s recent messages.

  • Attention

    Component stopped while reporting OK · SMS_SITE_BACKUP — CM01

    SMS_SITE_BACKUP on CM01 is not running, and therefore reports no recent errors — which is why its status still reads healthy.

    Restart the component, or confirm deliberately that the site is meant to run without it.

  • Attention

    Targets that never reported · 2026-09 Cumulative Update → All Workstations

    288 of 420 targets (68.6%) have never reported on this deployment.

    Targets that never answer are usually a client-health problem rather than a deployment one. Check that the collection’s machines still have a working agent.

  • Attention

    Distribution being retried · PS100002 — DP-LYON.corp.local

    Package PS100002 is still being retried towards DP-LYON.corp.local.

    Leave it if the retry is recent; if it has been retrying for days, treat it as a failure.

  • Attention

    Age of the last successful synchronisation · CM01.corp.local

    Last successful synchronisation 13 day(s) ago, on 2026-09-11 02:04 UTC. Raw state reported: 6702.

    A catalogue that stops synchronising stops offering new updates without failing. Restore the schedule.

  • Attention

    Errors and warnings over the window

    Over the last 72 h the site recorded 5 error(s) and 4 warning(s).

    Open Monitoring, then System Status, then Status Message Queries, for the full text of each message.

  • Attention

    Component reporting repeatedly · SMS_DISTRIBUTION_MANAGER

    SMS_DISTRIBUTION_MANAGER recorded 4 error(s) over the last 72 h.

    A component repeating the same error is usually one problem, not many. Start with the oldest occurrence.

  • Attention

    Component reporting repeatedly · SMS_WSUS_SYNC_MANAGER

    SMS_WSUS_SYNC_MANAGER recorded 1 error(s) over the last 72 h.

    A component repeating the same error is usually one problem, not many. Start with the oldest occurrence.

  • Attention

    Automatic client push installation

    The site installs the client automatically by push.

    A documented route to credential relay. Prefer deployment by group policy or by Intune, and disable automatic push.

  • Attention

    Distribution point serving over HTTP · DP-LYON.corp.local

    DP-LYON.corp.local serves content over plain HTTP.

    Move this distribution point to HTTPS, or enable Enhanced HTTP on the site.

  • Attention

    PXE open to unknown machines · DP-LYON.corp.local

    DP-LYON.corp.local answers PXE for machines the site has never heard of.

    Answering unknown machines lets anyone on the segment start an operating system deployment. Turn it off outside of a build window.

  • Attention

    Excessively wide boundary · Corporate

    Corporate covers 16 777 216 addresses (10.0.0.0/8).

    A boundary this wide gives content and site assignment to machines nobody intended. Split it along the network segments it actually covers.

  • Attention

    Boundaries in no group

    1 of 4 boundaries belong to no boundary group, so they route nothing.

    A boundary in no group does nothing. Attach it or remove it, so the boundary list still describes the network.

  • Attention

    Free space on a drive · SQL01.corp.local — D:

    D: on SQL01.corp.local has 6.2% left — 62.0 GB of 1000 GB.

    Free space on the content library, or move the library to a larger volume. A distribution point that fills up fails the packages it is asked for without failing itself.

  • Attention

    Site system reporting nothing · DP-NANTES.corp.local

    DP-NANTES.corp.local holds DP, Component, Site system and reports no component at all, so the console shows it as healthy on the strength of silence.

    Either the machine has stopped talking to the site, or its roles were removed and its record left behind. Both look healthy in the console.

  • Attention

    Free space on a drive · DP-NANTES.corp.local — E:

    E: on DP-NANTES.corp.local has 8.5% left — 34.0 GB of 400 GB.

    Free space on the content library, or move the library to a larger volume. A distribution point that fills up fails the packages it is asked for without failing itself.

  • Attention

    Distribution point behind the site build · DP-NANTES.corp.local

    DP-NANTES.corp.local is on 5.00.9058.1000 while the site is on 5.00.9128.1000.

    Check the distribution point upgrade under Monitoring, then Distribution Point Configuration Status. A distribution point that never takes the upgrade quietly stops supporting new content.

  • Attention

    WinRM listeners · DP-NANTES

    At least one WinRM listener accepts plain HTTP.

    Prefer an HTTPS listener with a valid certificate.

  • Attention

    SMB share · DP-LYON — Temp

    Temp points at C:\Temp and grants write access far too widely: Everyone (Change) — at share level. NTFS permissions were not read: effective access is the stricter of the two, so check them before concluding.

    This share was created by hand: restrict write access to named groups (content administrators) and check the underlying NTFS permissions. For a package source share, the site server computer account needs read access; also secure the channel with SMB signing, as Microsoft recommends.

  • Attention

    Built-in administrator account · DP-LYON — Administrator

    The built-in account Administrator is enabled.

    Disable it in favour of named accounts, or manage its password with LAPS.

  • Attention

    Minimum password length · DP-LYON

    Local minimum password length is 7 characters.

    Raise the minimum to fourteen characters or more.

  • Attention

    Password complexity · DP-LYON

    Password complexity is not required locally.

    Require complexity in the local security policy.

  • Attention

    Account lockout threshold · DP-LYON

    No account lockout threshold is set locally.

    Set a lockout threshold, ten attempts for instance, so a password cannot be guessed at leisure.

  • Attention

    WebClient service (WebDAV) · DP-LYON

    The WebClient service is running on this server.

    WebDAV makes credential coercion easier. Disable the service unless something needs it.

  • Attention

    Print Spooler service · DP-LYON

    The Print Spooler service is running on this server.

    A known vector for privilege escalation and coercion. Disable it unless this server prints.

  • Attention

    SMB signing required (server) · DP-LYON

    SMB signing is not required for inbound connections.

    Require SMB signing so an intercepted session cannot be relayed.

  • Attention

    SMB signing required (client) · DP-LYON

    SMB signing is not required for outbound connections.

    Require SMB signing on outbound connections as well; the server half alone does not stop a relay.

  • Attention

    NetBIOS over TCP/IP · DP-LYON

    NetBIOS over TCP/IP is enabled or left at its default on: Ethernet0; Ethernet1

    Disable NetBIOS over TCP/IP to close name-poisoning attacks such as Responder.

  • Attention

    LLMNR · DP-LYON

    LLMNR is not explicitly disabled, so the default applies and it answers.

    Disable LLMNR by group policy, alongside NetBIOS.

  • Attention

    LAN Manager authentication level · DP-LYON

    Set to 2, which still accepts authentication weaker than NTLMv2.

    Set the LAN Manager authentication level to 5, which sends NTLMv2 only and refuses LM and NTLM.

  • Attention

    LSA protection (RunAsPPL) · DP-LYON

    The LSA process does not run protected.

    Enable LSA protection once third-party drivers and agents have been tested against it.

  • Attention

    WinRM listeners · DP-LYON

    At least one WinRM listener accepts plain HTTP.

    Prefer an HTTPS listener with a valid certificate.

  • Attention

    WinRM TrustedHosts · DP-LYON

    TrustedHosts is set to the wildcard, so this client will authenticate to any host.

    Replace the wildcard with an explicit list of trusted servers.

  • Attention

    Microsoft Defender Antivirus · DP-LYON

    Real-time protection: true. Antivirus engine: true. Signatures are 14 day(s) old.

    Make sure real-time protection is on and the signatures current, or confirm an equivalent third-party agent.

  • Attention

    Most recent operating system update · DP-LYON — KB5036893

    The most recent update on record is KB5036893, installed on 2026-04-10 00:00 UTC — 165 day(s) ago.

    Review the patching process for this server.

  • Attention

    Command line in process creation events · DP-LYON

    Process creation events do not include the command line.

    Include the command line in event 4688; without it, process auditing rarely names what actually ran.

  • Attention

    PowerShell script block logging · DP-LYON

    Script block logging is not enabled.

    Enable PowerShell script block logging: it is the single most useful source for detecting what a script did.

  • Attention

    PowerShell v2 engine · DP-LYON

    The PowerShell v2 engine is still installed.

    Remove PowerShell v2: it supports neither AMSI nor script block logging, and it can be requested deliberately to escape both.

  • Attention

    Anonymous enumeration of SAM accounts · DP-LYON

    Anonymous enumeration of SAM accounts is not explicitly refused.

    Refuse anonymous enumeration of SAM accounts and shares.

  • Attention

    Legacy TLS/SSL protocol · DP-LYON — SSL 3.0

    SSL 3.0 is active server-side.

    Disable this protocol: it is obsolete.

  • Attention

    Legacy TLS/SSL protocol · DP-LYON — TLS 1.0

    TLS 1.0 is active server-side.

    Disable this protocol: it is obsolete.

  • Attention

    Legacy TLS/SSL protocol · DP-LYON — TLS 1.1

    TLS 1.1 is active server-side.

    Disable this protocol: it is obsolete.

  • Attention

    Cipher suites · DP-LYON

    1 weak cipher suite(s) remain enabled: TLS_RSA_WITH_3DES_EDE_CBC_SHA

    Remove the obsolete suites from the cipher order.

  • Attention

    Built-in administrator account · SQL01 — Administrator

    The built-in account Administrator is enabled.

    Disable it in favour of named accounts, or manage its password with LAPS.

  • Attention

    Minimum password length · SQL01

    Local minimum password length is 8 characters.

    Raise the minimum to fourteen characters or more.

  • Attention

    Account lockout threshold · SQL01

    No account lockout threshold is set locally.

    Set a lockout threshold, ten attempts for instance, so a password cannot be guessed at leisure.

  • Attention

    Print Spooler service · SQL01

    The Print Spooler service is running on this server.

    A known vector for privilege escalation and coercion. Disable it unless this server prints.

  • Attention

    Unquoted service paths · SQL01

    1 service(s) have an executable path that contains a space and is not quoted: SqlMonitor : C:\Program Files\Contoso Tools\sqlmon.exe -service

    Quote each executable path so a file dropped earlier in it cannot be started instead.

  • Attention

    SMB signing required (server) · SQL01

    SMB signing is not required for inbound connections.

    Require SMB signing so an intercepted session cannot be relayed.

  • Attention

    SMB signing required (client) · SQL01

    SMB signing is not required for outbound connections.

    Require SMB signing on outbound connections as well; the server half alone does not stop a relay.

  • Attention

    NetBIOS over TCP/IP · SQL01

    NetBIOS over TCP/IP is enabled or left at its default on: Ethernet0

    Disable NetBIOS over TCP/IP to close name-poisoning attacks such as Responder.

  • Attention

    LLMNR · SQL01

    LLMNR is not explicitly disabled, so the default applies and it answers.

    Disable LLMNR by group policy, alongside NetBIOS.

  • Attention

    LAN Manager authentication level · SQL01

    Set to 3, which still accepts authentication weaker than NTLMv2.

    Set the LAN Manager authentication level to 5, which sends NTLMv2 only and refuses LM and NTLM.

  • Attention

    LSA protection (RunAsPPL) · SQL01

    The LSA process does not run protected.

    Enable LSA protection once third-party drivers and agents have been tested against it.

  • Attention

    WinRM listeners · SQL01

    At least one WinRM listener accepts plain HTTP.

    Prefer an HTTPS listener with a valid certificate.

  • Attention

    Most recent operating system update · SQL01 — KB5040437

    The most recent update on record is KB5040437, installed on 2026-06-12 00:00 UTC — 102 day(s) ago.

    Review the patching process for this server.

  • Attention

    Command line in process creation events · SQL01

    Process creation events do not include the command line.

    Include the command line in event 4688; without it, process auditing rarely names what actually ran.

  • Attention

    PowerShell script block logging · SQL01

    Script block logging is not enabled.

    Enable PowerShell script block logging: it is the single most useful source for detecting what a script did.

  • Attention

    PowerShell v2 engine · SQL01

    The PowerShell v2 engine is still installed.

    Remove PowerShell v2: it supports neither AMSI nor script block logging, and it can be requested deliberately to escape both.

  • Attention

    Legacy TLS/SSL protocol · SQL01 — TLS 1.0

    TLS 1.0 is active server-side.

    Disable this protocol: it is obsolete.

  • Attention

    Legacy TLS/SSL protocol · SQL01 — TLS 1.1

    TLS 1.1 is active server-side.

    Disable this protocol: it is obsolete.

  • Attention

    Cipher suites · SQL01

    2 weak cipher suite(s) remain enabled: TLS_RSA_WITH_3DES_EDE_CBC_SHA, TLS_RSA_WITH_RC4_128_SHA

    Remove the obsolete suites from the cipher order.

  • Attention

    SMB share · CM01 — Sources

    Sources points at E:\Sources and grants write access far too widely: Everyone (Full) — at share level. NTFS permissions were not read: effective access is the stricter of the two, so check them before concluding.

    This share was created by hand: restrict write access to named groups (content administrators) and check the underlying NTFS permissions. For a package source share, the site server computer account needs read access; also secure the channel with SMB signing, as Microsoft recommends.

  • Attention

    Built-in administrator account · CM01 — Administrator

    The built-in account Administrator is enabled.

    Disable it in favour of named accounts, or manage its password with LAPS.

  • Attention

    Minimum password length · CM01

    Local minimum password length is 12 characters.

    Raise the minimum to fourteen characters or more.

  • Attention

    Print Spooler service · CM01

    The Print Spooler service is running on this server.

    A known vector for privilege escalation and coercion. Disable it unless this server prints.

  • Attention

    SMB signing required (client) · CM01

    SMB signing is not required for outbound connections.

    Require SMB signing on outbound connections as well; the server half alone does not stop a relay.

  • Attention

    NetBIOS over TCP/IP · CM01

    NetBIOS over TCP/IP is enabled or left at its default on: Ethernet0

    Disable NetBIOS over TCP/IP to close name-poisoning attacks such as Responder.

  • Attention

    LLMNR · CM01

    LLMNR is not explicitly disabled, so the default applies and it answers.

    Disable LLMNR by group policy, alongside NetBIOS.

  • Attention

    LAN Manager authentication level · CM01

    Set to 3, which still accepts authentication weaker than NTLMv2.

    Set the LAN Manager authentication level to 5, which sends NTLMv2 only and refuses LM and NTLM.

  • Attention

    LSA protection (RunAsPPL) · CM01

    The LSA process does not run protected.

    Enable LSA protection once third-party drivers and agents have been tested against it.

  • Attention

    WinRM listeners · CM01

    At least one WinRM listener accepts plain HTTP.

    Prefer an HTTPS listener with a valid certificate.

  • Attention

    Command line in process creation events · CM01

    Process creation events do not include the command line.

    Include the command line in event 4688; without it, process auditing rarely names what actually ran.

Every machine this site runs on, gathered into one card each: the roles it holds, what its components are saying, how much room is left on its drives and whether the hardening collector has been near it. Errors are dated from the status messages: a component quiet for 30 days no longer counts as a finding.

Site systems

6

site PS1

Machines in trouble

5

Distribution points

3

Distinct roles

9

Free space

625 GB

of 2.9 TB across every drive read

Hardening collected

5 / 6

Free space, tightest machine first

DP-LYON2.8% · 11.0 GB
SQL016.2% · 62.0 GB
DP-NANTES8.5% · 34.0 GB
CM0142% · 210 GB
RPT0158.3% · 70.0 GB

Machines per role

DP3
Storage Object3
MP2
FSP1
Provider1
Reporting1
Site server1
SQL1
SUP1

Collected on 5 of 6 machines.

MP02.corp.local — Connecting to remote server MP02.corp.local failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer.

One card per machine. Those that need attention are already open; click a card to see its components, drives and roles.
CM01.corp.localsite server
DPFSPMPProviderSite serverSUPStorage ObjectComponentSite system
StatusCritical
Components2 in trouble of 7
Errors37 +8
Tightest drive
E:58% used
210 GB / 500 GB
TransportHTTPS
Hardeningcollected

Components to look at

ComponentStatusSite countersLast contact
SMS_DISTRIBUTION_MANAGERCritical37 err. / 5 warn.—
SMS_WSUS_SYNC_MANAGERAttention0 err. / 3 warn.—
5 healthy component(s)
  • SMS_COLLECTION_EVALUATOR
  • SMS_EXECUTIVE
  • SMS_MP_CONTROL_MANAGER
  • SMS_POLICY_PROVIDER
  • SMS_SITE_BACKUP stopped

1 stopped

Drives

DriveFree spaceSize
E:210 GB500 GB
58% used
C:88.0 GB200 GB
56% used

Roles

  • DPSMS Distribution Point
  • FSPSMS Fallback Status Point
  • MPSMS Management Point
  • ProviderSMS Provider
  • Site serverSMS Site Server
  • SUPSMS Software Update Point
  • Storage ObjectStorage Object
  • ComponentSMS Component Server
  • Site systemSMS Site System

SQL01.corp.local
SQLStorage ObjectSite system
StatusAttention
Components—
Errors0
Tightest drive
D:93.8% used
62.0 GB / 1000 GB
Transport—
Hardeningcollected

Components to look at

This machine reports no component at all.

Drives

DriveFree spaceSize
D:62.0 GB1000 GB
93.8% used

Roles

  • SQLSMS SQL Server
  • Storage ObjectStorage Object
  • Site systemSMS Site System

DP-LYON.corp.local
DPComponentSite system
StatusCritical
Components1 healthy
Errors0
Tightest drive
E:97.2% used
11.0 GB / 400 GB
TransportHTTP · PXE
Hardeningcollected

Components to look at

No component in trouble.

1 healthy component(s)
  • SMS_EXECUTIVE

Drives

DriveFree spaceSize
E:11.0 GB400 GB
97.2% used
F:150 GB400 GB
62.5% used

Roles

  • DPSMS Distribution Point
  • ComponentSMS Component Server
  • Site systemSMS Site System

DP-NANTES.corp.local
DPComponentSite system
StatusAttention
Components—
Errors0
Tightest drive
E:91.5% used
34.0 GB / 400 GB
TransportHTTPS · pull
Hardeningcollected

Components to look at

This machine reports no component at all.

Drives

DriveFree spaceSize
E:34.0 GB400 GB
91.5% used

Roles

  • DPSMS Distribution Point
  • ComponentSMS Component Server
  • Site systemSMS Site System

MP02.corp.local
MPSite system
StatusOK
Components2 healthy
Errors0
Tightest driveno drive reported
Transport—
Hardeningnot collected

Components to look at

No component in trouble.

2 healthy component(s)
  • SMS_MP_CONTROL_MANAGER
  • SMS_MP_FILE_DISPATCH_MANAGER

Drives

no drive reported

Roles

  • MPSMS Management Point
  • Site systemSMS Site System

RPT01.corp.local
ReportingStorage ObjectComponentSite system
StatusAttention
Components1 in trouble of 1
Errors0 +2
Tightest drive
C:41.7% used
70.0 GB / 120 GB
Transport—
Hardeningcollected

Components to look at

ComponentStatusSite countersLast contact
SMS_SRS_REPORTING_POINTAttention0 err. / 2 warn.—

Drives

DriveFree spaceSize
C:70.0 GB120 GB
41.7% used

Roles

  • ReportingSMS SRS Reporting Point
  • Storage ObjectStorage Object
  • ComponentSMS Component Server
  • Site systemSMS Site System

Infrastructure1 Critical 4 Attention 4 To verify
CheckStatusDetailRecommendationDoc.
Infrastructure of this siteTo verify6 machine(s) carry this site, holding 9 distinct role(s), 3 of them distribution points.——
Free space on a driveSQL01.corp.local — D:AttentionD: on SQL01.corp.local has 6.2% left — 62.0 GB of 1000 GB.Free space on the content library, or move the library to a larger volume. A distribution point that fills up fails the packages it is asked for without failing itself.—
Free space on a driveDP-LYON.corp.local — E:CriticalE: on DP-LYON.corp.local has 2.8% left — 11.0 GB of 400 GB.Free space on the content library, or move the library to a larger volume. A distribution point that fills up fails the packages it is asked for without failing itself.—
Site system reporting nothingDP-NANTES.corp.localAttentionDP-NANTES.corp.local holds DP, Component, Site system and reports no component at all, so the console shows it as healthy on the strength of silence.Either the machine has stopped talking to the site, or its roles were removed and its record left behind. Both look healthy in the console.↗
Free space on a driveDP-NANTES.corp.local — E:AttentionE: on DP-NANTES.corp.local has 8.5% left — 34.0 GB of 400 GB.Free space on the content library, or move the library to a larger volume. A distribution point that fills up fails the packages it is asked for without failing itself.—
Distribution point behind the site buildDP-NANTES.corp.localAttentionDP-NANTES.corp.local is on 5.00.9058.1000 while the site is on 5.00.9128.1000.Check the distribution point upgrade under Monitoring, then Distribution Point Configuration Status. A distribution point that never takes the upgrade quietly stops supporting new content.—
Site database serverSQL01.corp.localTo verifyThe site database is on SQL01.corp.local.Confirm this server is sized, backed up and patched as a site component rather than as an ordinary database host.—
Hardening coverageTo verifyThe hardening collector has been run on 5 of 6 machines. Nothing is known about the operating system of the others: MP02.corp.localRun the collector on the remaining machines: a distribution point in a branch office has its own local administrators and its own firewall.—
Site systems, in summaryTo verify6 machine(s), 5 of them with something to look at: CM01.corp.local, SQL01.corp.local, DP-LYON.corp.local, DP-NANTES.corp.local, RPT01.corp.local——

The machines the site manages, read as a population: is the client there, is it talking to the infrastructure, is it reporting back, is it healthy, and how much of it has moved to Intune.

Machines known

36

2 superseded

Healthy clients

20

66.7% of clients · active, health OK, policy < 7 d, inventory < 14 d

No client

4

of those discovered

Quiet for a week

4

13.3% · 2 over a month

Client health failing

2

3 never evaluated

Inventory stale

4

13.3%

Co-managed

22

73.3%

Last policy request

today25
this week0
this month2
older2
never1

Last hardware inventory

today3
this week20
this month2
older3
never2

Client versions

site build 5.00.9128.1000

5.00.912826
5.00.90584

Workloads moved to Intune

out of 30 managed machines

Compliance policies22
Resource access0
Device configuration19
Windows Update policies0
Endpoint Protection0
Client apps0
Office Click-to-Run0

Enrolment failures, by the status the client reported

0x8018000a · 20x80180014 · 1
Clients1 Critical 7 Attention 1 OK 3 To verify
CheckStatusDetailRecommendationDoc.
Clients, in summaryTo verify36 machines known to the site, 32 carrying a client, 2 superseded.——
Machines with no clientAttention4 of 34 discovered machines have no client (11.8%). 32 are installed.A discovered machine with no client is one the site cannot manage or report on. Check client push, the boundary groups that machine falls in, and whether it is still alive at all.↗
Superseded recordsOK2 of 36 records are superseded (5.6%).——
Clients the site calls inactiveAttentionThe site calls 3 of 30 managed clients inactive (10%).Inactive is the site’s own verdict, based on heartbeat and policy. Start with the ones that are also quiet.—
Clients that have stopped asking for policyAttention4 of 30 clients (13.3%) have not asked for their policy in over 7 days, 2 of them in over 30.A client that stops asking for policy stops receiving deployments without failing any of them. This is the most reliable sign of a client that is present and dead.—
Clients that never asked for policyAttention1 of 30 clients have never asked for a policy at all.A client that has never asked for policy was installed but never registered. Check its certificate, its management point and the boundary group it falls in.—
Clients no longer reporting inventoryAttention4 of 30 clients (13.3%) have not reported hardware inventory in over 14 days, and 2 never have.A client that asks for policy but reports no inventory skews every report you run without ever failing. Check the WMI repository and the inventory cycle on these machines.↗
Client health evaluationAttention2 of 27 evaluated clients failed their health check (7.4%). 3 were never evaluated.Open Monitoring, then Client Status, for the individual checks. Failures here are usually the WMI repository, the client certificate or the agent service.↗
Clients behind the site buildAttention4 of 30 clients (13.3%) are on a build other than the site’s 5.00.9128.A client behind the site build fails deployments for reasons that never appear in the deployment. Promote the client upgrade.↗
Co-managementTo verify22 of 30 managed clients are co-managed (73.3%), and 22 are enrolled in Intune.Co-management is the path off this site. Every machine not co-managed is one the migration has not started on.↗
Workloads moved to IntuneTo verify2 workload(s) have moved to Intune: compliance, deviceConfiguration. Raw bitmask on a sample device: 11.Each workload switched to Intune is one this site no longer has to carry. The raw bitmask is printed so the reading can be confirmed against the console.↗
MDM enrolment failuresCritical3 of 30 clients (10%) failed to enrol in Intune. Commonest statuses: 0x8018000a (2), 0x80180014 (1)These machines are co-management candidates that cannot enrol, so the migration stops at them. The status code is the fix: look it up before touching the device.↗

The machines to start from

worst 10, most reasons first
ServerOperating systemClientPolicyInventoryWhat is wrong
PC-0202Microsoft Windows NT Workstation 10.05.00.9058.1000119 d129 dsilent for a monthinactiveinventory stale
PC-0201Microsoft Windows NT Workstation 10.05.00.9058.100063 d69 dsilent for a monthinactiveinventory stale
PC-0301Microsoft Windows NT Workstation 10.05.00.9128.1025nevernevernever asked for policyinactivenever inventoried
PC-0102Microsoft Windows NT Workstation 10.05.00.9128.102511 d19 dquietinventory stale
PC-0401Microsoft Windows NT Workstation 10.05.00.9128.1025-1 d44 dhealth check failedinventory stale
PC-0402Microsoft Windows NT Workstation 10.05.00.9128.1025-1 dneverhealth check failednever inventoried
PC-0101Microsoft Windows NT Workstation 10.05.00.9128.10258 d8 dquiet
PC-0502Microsoft Windows NT Workstation 10.05.00.9128.10250 d1 denrolment failed
PC-0501Microsoft Windows NT Workstation 10.05.00.9128.1025-1 d0 denrolment failed
PC-0503Microsoft Windows NT Workstation 10.05.00.9128.1025-1 d0 denrolment failed

Site

PS1

5.00.9128.1000

Site system roles

11

Components

11

Deployments

5

Distribution points

3

Collections

3

Status messages

9

last 72 h

Deployments by failure rate

Contoso CAD 2026 → Engineering laptops60.9% · 39/64
Acme Reader 12 → All Workstations4.3% · 18/420
2026-09 Cumulative Update → All Workstations1% · 4/420
Security baseline → All Workstations0.5% · 2/420

Errors and warnings over the window

21/09 09:0024/09 08:00
ErrorsWarnings

Components reporting the most

SMS_DISTRIBUTION_MANAGER · 5SMS_WSUS_SYNC_MANAGER · 2SMS_MP_CONTROL_MANAGER · 1SMS_COLLECTION_EVALUATOR · 1
Site1 To verify
CheckStatusDetailRecommendationDoc.
Site identity and versionPS1To verifySite PS1 (Primary site - SYNTHETIC) on CM01.corp.local, version 5.00.9128.1000, build 9128.——
Roles and components2 Critical 5 Attention 2 To verify
CheckStatusDetailRecommendationDoc.
Site system roleSMS Distribution Point — DP-LYON.corp.localCriticalConfiguration Manager reports SMS Distribution Point on DP-LYON.corp.local at status 2 (0 healthy, 1 warning, 2 critical).Open Monitoring, then Site Status, for the messages this role has recorded.↗
Site system roleSMS Software Update Point — CM01.corp.localAttentionConfiguration Manager reports SMS Software Update Point on CM01.corp.local at status 1 (0 healthy, 1 warning, 2 critical).Open Monitoring, then Site Status, for the messages this role has recorded.↗
Site system roleStorage Object — SQL01.corp.localAttentionConfiguration Manager reports Storage Object on SQL01.corp.local at status 1 (0 healthy, 1 warning, 2 critical).Open Monitoring, then Site Status, for the messages this role has recorded.↗
Site system roles, in summaryTo verify8 of 11 site system roles are healthy.——
Site componentSMS_DISTRIBUTION_MANAGER — CM01CriticalSMS_DISTRIBUTION_MANAGER on CM01 is at status 2, with 37 error(s) and 5 warning(s) over the summary interval.Open Monitoring, then Component Status, and read this component’s recent messages.↗
Site componentSMS_WSUS_SYNC_MANAGER — CM01AttentionSMS_WSUS_SYNC_MANAGER on CM01 is at status 1, with 0 error(s) and 3 warning(s) over the summary interval.Open Monitoring, then Component Status, and read this component’s recent messages.↗
Site componentSMS_SRS_REPORTING_POINT — RPT01AttentionSMS_SRS_REPORTING_POINT on RPT01 is at status 1, with 0 error(s) and 2 warning(s) over the summary interval.Open Monitoring, then Component Status, and read this component’s recent messages.↗
Component stopped while reporting OKSMS_SITE_BACKUP — CM01AttentionSMS_SITE_BACKUP on CM01 is not running, and therefore reports no recent errors — which is why its status still reads healthy.Restart the component, or confirm deliberately that the site is meant to run without it.—
Site components, in summaryTo verify11 components monitored, 3 of them not healthy.——
Deployments1 Critical 1 Attention 1 To verify
CheckStatusDetailRecommendationDoc.
Deployment failure rateContoso CAD 2026 → Engineering laptopsCritical39 of 64 targets failed (60.9%). Succeeded 22, in progress 1, no answer 2.Open this deployment under Monitoring, then Deployments, and work back from the error codes the clients returned.↗
Targets that never reported2026-09 Cumulative Update → All WorkstationsAttention288 of 420 targets (68.6%) have never reported on this deployment.Targets that never answer are usually a client-health problem rather than a deployment one. Check that the collection’s machines still have a working agent.—
Deployments, in summaryTo verify5 active deployments, 1 of them failing on more than a tenth of their targets.——
Content distribution1 Critical 1 Attention 1 To verify
CheckStatusDetailRecommendationDoc.
Failed distributionPS100001 — DP-LYON.corp.localCriticalPackage PS100001 could not be placed on DP-LYON.corp.local and is no longer being retried (state 3).Redistribute the package to this distribution point, and check the disk space and the content library on it.↗
Distribution being retriedPS100002 — DP-LYON.corp.localAttentionPackage PS100002 is still being retried towards DP-LYON.corp.local.Leave it if the retry is recent; if it has been retrying for days, treat it as a failure.—
Content distribution, in summaryTo verify5 package-to-distribution-point states: 1 failed, 1 retrying, 1 in progress.——
Software updates1 Critical 1 Attention 1 To verify
CheckStatusDetailRecommendationDoc.
Age of the last successful synchronisationCM01.corp.localAttentionLast successful synchronisation 13 day(s) ago, on 2026-09-11 02:04 UTC. Raw state reported: 6702.A catalogue that stops synchronising stops offering new updates without failing. Restore the schedule.—
Automatic deployment rule failingDefender definitionsCriticalDefender definitions last ran on 2026-09-22 01:00 UTC and ended with error 0x87D01101.Re-run the rule by hand and read the error it returns; a rule that has failed silently deploys nothing at all.↗
Automatic deployment rules, in summaryTo verify2 automatic deployment rules, 1 of them ending in error.——
Collections2 OK 1 To verify
CheckStatusDetailRecommendationDoc.
Collections evaluated incrementallyOK3 of 3 collections are evaluated incrementally (guidance caps this around 200).——
Empty collectionsOK0 of 3 collections have no member.——
Collections never re-evaluatedTo verify0 of 3 collections have no evaluation schedule and only change when someone updates them by hand.——
Status messages3 Attention
CheckStatusDetailRecommendationDoc.
Errors and warnings over the windowAttentionOver the last 72 h the site recorded 5 error(s) and 4 warning(s).Open Monitoring, then System Status, then Status Message Queries, for the full text of each message.—
Component reporting repeatedlySMS_DISTRIBUTION_MANAGERAttentionSMS_DISTRIBUTION_MANAGER recorded 4 error(s) over the last 72 h.A component repeating the same error is usually one problem, not many. Start with the oldest occurrence.—
Component reporting repeatedlySMS_WSUS_SYNC_MANAGERAttentionSMS_WSUS_SYNC_MANAGER recorded 1 error(s) over the last 72 h.A component repeating the same error is usually one problem, not many. Start with the oldest occurrence.—

What the site itself exposes: who administers it, how clients reach it, how it installs them, and what an unknown machine can ask it for. Hardening of the server it runs on is the next tab, and it cannot be read from here.

Critical

1

Attention

5

OK

2

To verify

7

Misconfiguration Manager coverage

The 23 preventive measures of Misconfiguration Manager (SpecterOps), and what this report measures of them. The status is the worst of the checks involved, across all machines.

IDMeasureStatusChecked by
PREVENT-1Patch site server with KB15599094OK1 check(s): Client push NTLM update (KB15599094)
PREVENT-2Disable fallback to NTLM—Not collected: the matching read did not run or returned nothing.
PREVENT-3Harden or disable network access accountsTo verify1 check(s): Network Access Account
PREVENT-4Configure Enhanced HTTPTo verify1 check(s): Client communication mode
PREVENT-5Disable automatic site-wide client push installationAttention1 check(s): Automatic client push installation
PREVENT-6Configure a strong PXE boot password—Cannot be measured read-only from the site: check by hand.
PREVENT-7Disable command support in PXE boot configuration—Not collected: the matching read did not run or returned nothing.
PREVENT-8Require PKI certificates for client authenticationTo verify1 check(s): Client communication mode
PREVENT-9Enforce MFA for SMS Provider calls—Cannot be measured read-only from the site: check by hand.
PREVENT-10Enforce the principle of least privilege for accountsCritical11 check(s): Holders of the Full Administrator role, Local Administrators group, Wide directory group in the local administrators
PREVENT-11Disable and uninstall WebClient on site serversAttention5 check(s): WebClient service (WebDAV)
PREVENT-12Require SMB signing on site systemsAttention10 check(s): SMB signing required (server), SMB signing required (client)
PREVENT-13Require LDAP channel binding and signing—Out of scope: a setting of the domain controllers or the directory, not of the site systems.
PREVENT-14Require EPA on AD CS and site databases—Not collected: the matching read did not run or returned nothing.
PREVENT-15Disable and change passwords of legacy NAAs and collection variablesTo verify1 check(s): Network Access Account
PREVENT-16Remove SeMachineAccountPrivilege and set MachineAccountQuota to 0—Not collected: the matching read did not run or returned nothing.
PREVENT-17Remove Extended Rights assignment from accounts that do not require it—Out of scope: a setting of the domain controllers or the directory, not of the site systems.
PREVENT-18Use strong passwords for DBA accounts—Cannot be measured read-only from the site: check by hand.
PREVENT-19Remove unnecessary links to site databases—Cannot be measured read-only from the site: check by hand.
PREVENT-20Block unnecessary connections to site systemsCritical17 check(s): Windows Firewall profile, SMB share
PREVENT-21Restrict PXE boot to authorized VLANs—Cannot be measured read-only from the site: check by hand.
PREVENT-22Do not manage assets in two or more segmented forests, domains, networks—Out of scope: a setting of the domain controllers or the directory, not of the site systems.
PREVENT-23Ensure the client cache directory (ccmcache) is not writable by non-administrative users—Not collected: the matching read did not run or returned nothing.
Administration1 To verify
CheckStatusDetailRecommendationDoc.
Holders of the Full Administrator roleTo verify1 account(s) or group(s) hold Full Administrator: CORP\g-sccm-fulladminsKeep Full Administrator to the few who genuinely need it, and use narrower roles for everyday work.↗
Client push1 Attention 2 OK
CheckStatusDetailRecommendationDoc.
Automatic client push installationAttentionThe site installs the client automatically by push.A documented route to credential relay. Prefer deployment by group policy or by Intune, and disable automatic push.↗
Client push to domain controllersOKDomain controllers are excluded from automatic client push.——
Client push NTLM update (KB15599094)OKBuild 9128: later than 2207, which includes update KB15599094.——
Accounts1 To verify
CheckStatusDetailRecommendationDoc.
Network Access AccountTo verifyThe Network Access Account setting could not be read (Software Distribution component of the site control file).If one is configured, its credentials can be read back from any client by a local administrator. Restrict it to read-only rights, or retire it in favour of Enhanced HTTP or HTTPS.↗
Client communication1 Attention 2 To verify
CheckStatusDetailRecommendationDoc.
Client communication modeTo verifyThe provider did not return a client communication mode for this site.Confirm the site is on HTTPS or on Enhanced HTTP, and not on plain HTTP.↗
Distribution point serving over HTTPDP-LYON.corp.localAttentionDP-LYON.corp.local serves content over plain HTTP.Move this distribution point to HTTPS, or enable Enhanced HTTP on the site.↗
Distribution point transport, in summaryTo verify2 of 3 distribution points serve over HTTPS.——
OS deployment and PXE1 Critical 1 Attention 2 To verify
CheckStatusDetailRecommendationDoc.
PXE-enabled distribution pointsTo verify1 distribution point(s) answer PXE: DP-LYON.corp.localRequire a boot password and restrict which network segments can reach the PXE responder.↗
PXE open to unknown machinesDP-LYON.corp.localAttentionDP-LYON.corp.local answers PXE for machines the site has never heard of.Answering unknown machines lets anyone on the segment start an operating system deployment. Turn it off outside of a build window.↗
Task sequence deployed to a built-in collectionWindows 11 24H2 build → All Unknown ComputersCriticalThe task sequence Windows 11 24H2 build is deployed to All Unknown Computers, which is a built-in collection rather than a chosen population.Deploy the task sequence to a collection built for it, and make it available rather than required.↗
Task sequencesTo verify2 task sequence(s) on this site. Their steps and variables were not opened by this check.Check that no task sequence stores a password in a variable that is not masked.—
Boundaries2 Attention 1 To verify
CheckStatusDetailRecommendationDoc.
Boundary groupsTo verify3 boundary group(s): Lyon, Nantes, Default-Site-Boundary-Group<PS1>Confirm that no boundary group grants content access far beyond the site it is meant to serve.↗
Excessively wide boundaryCorporateAttentionCorporate covers 16 777 216 addresses (10.0.0.0/8).A boundary this wide gives content and site assignment to machines nobody intended. Split it along the network segments it actually covers.—
Boundaries in no groupAttention1 of 4 boundaries belong to no boundary group, so they route nothing.A boundary in no group does nothing. Attach it or remove it, so the boundary list still describes the network.—

Registry keys, local groups, services and protocols on the site server. No REST interface exposes any of this, so it is collected by a read-only script run on that server, and the result is graded here.

Collected on 5 of 6 machines.

MP02.corp.local — Connecting to remote server MP02.corp.local failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer.

Server read

5

machines collected

Collected

22/09/2026

the most recent of them

Critical

13

Attention

56

Shares2 Attention 6 OK 8 To verify
CheckStatusDetailRecommendationDoc.
Non-administrative SMB sharesRPT01OKThis server publishes no share beyond the administrative ones.——
File names suggesting secretsRPT01To verifyThe share content scan was not requested, so no file name was examined.Run the collector with the share scan enabled if you want file names examined. It reads names only, never contents.—
Shares created by Configuration Manager, WSUS or WindowsDP-NANTESOK1 product share(s), checked at both the share and the NTFS level: no broad group can write to them. SCCMContentLib$ (ConfigMgr content)——
Content published by the distribution pointDP-NANTESTo verifyThis server publishes the content library (SCCMContentLib$). By design, distribution point content is readable by every domain user, over SMB as over HTTP: any script, configuration file or package holding a password is exposed there.The fix is not in the share ACLs but in what gets published: no credentials in package, application or task sequence sources (use masked collection variables or a vault, and hunt existing secrets with -ScanShares). To restrict a sensitive package, use package access accounts (HTTP distribution point), the path Microsoft documents. Remove the distribution point role from the site server, keep anonymous access off on DPs, and filter traffic to the DPs (Misconfiguration Manager CRED-6, PREVENT-10 and PREVENT-20).↗
Non-administrative SMB sharesDP-NANTESOKNo hand-made share: this server only publishes administrative shares or shares created by a product.——
File names suggesting secretsDP-NANTESTo verifyThe share content scan was not requested, so no file name was examined.Run the collector with the share scan enabled if you want file names examined. It reads names only, never contents.—
Shares created by Configuration Manager, WSUS or WindowsDP-LYONOK2 product share(s), checked at both the share and the NTFS level: no broad group can write to them. REMINST (WDS / PXE), SCCMContentLib$ (ConfigMgr content)——
Content published by the distribution pointDP-LYONTo verifyThis server publishes the content library (SCCMContentLib$). By design, distribution point content is readable by every domain user, over SMB as over HTTP: any script, configuration file or package holding a password is exposed there.The fix is not in the share ACLs but in what gets published: no credentials in package, application or task sequence sources (use masked collection variables or a vault, and hunt existing secrets with -ScanShares). To restrict a sensitive package, use package access accounts (HTTP distribution point), the path Microsoft documents. Remove the distribution point role from the site server, keep anonymous access off on DPs, and filter traffic to the DPs (Misconfiguration Manager CRED-6, PREVENT-10 and PREVENT-20).↗
SMB shareDP-LYON — TempAttentionTemp points at C:\Temp and grants write access far too widely: Everyone (Change) — at share level. NTFS permissions were not read: effective access is the stricter of the two, so check them before concluding.This share was created by hand: restrict write access to named groups (content administrators) and check the underlying NTFS permissions. For a package source share, the site server computer account needs read access; also secure the channel with SMB signing, as Microsoft recommends.—
File names suggesting secretsDP-LYONTo verifyThe share content scan was not requested, so no file name was examined.Run the collector with the share scan enabled if you want file names examined. It reads names only, never contents.—
Non-administrative SMB sharesSQL01OKThis server publishes no share beyond the administrative ones.——
File names suggesting secretsSQL01To verifyThe share content scan was not requested, so no file name was examined.Run the collector with the share scan enabled if you want file names examined. It reads names only, never contents.—
Shares created by Configuration Manager, WSUS or WindowsCM01OK2 product share(s), checked at both the share and the NTFS level: no broad group can write to them. SCCMContentLib$ (ConfigMgr content), SMS_PS1 (ConfigMgr site)——
Content published by the distribution pointCM01To verifyThis server publishes the content library (SCCMContentLib$). By design, distribution point content is readable by every domain user, over SMB as over HTTP: any script, configuration file or package holding a password is exposed there.The fix is not in the share ACLs but in what gets published: no credentials in package, application or task sequence sources (use masked collection variables or a vault, and hunt existing secrets with -ScanShares). To restrict a sensitive package, use package access accounts (HTTP distribution point), the path Microsoft documents. Remove the distribution point role from the site server, keep anonymous access off on DPs, and filter traffic to the DPs (Misconfiguration Manager CRED-6, PREVENT-10 and PREVENT-20).↗
SMB shareCM01 — SourcesAttentionSources points at E:\Sources and grants write access far too widely: Everyone (Full) — at share level. NTFS permissions were not read: effective access is the stricter of the two, so check them before concluding.This share was created by hand: restrict write access to named groups (content administrators) and check the underlying NTFS permissions. For a package source share, the site server computer account needs read access; also secure the channel with SMB signing, as Microsoft recommends.—
File names suggesting secretsCM01To verifyThe share content scan was not requested, so no file name was examined.Run the collector with the share scan enabled if you want file names examined. It reads names only, never contents.—
Local accounts6 Critical 3 Attention 9 OK 7 To verify
CheckStatusDetailRecommendationDoc.
Local Administrators groupRPT01To verify2 member(s): RPT01\Administrator, CORP\Domain AdminsKeep only what is needed: the Configuration Manager service accounts and the named administrators.—
Wide directory group in the local administratorsRPT01 — CORP\Domain AdminsCriticalCORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.Remove the group and use one dedicated to administering this server.—
Built-in administrator accountRPT01 — AdministratorOKThe built-in account Administrator is disabled.——
Guest accountRPT01 — GuestOKThe guest account Guest is disabled.——
LAPSRPT01OKA LAPS configuration is present on this server (windows).——
Local Administrators groupDP-NANTESTo verify3 member(s): DP-NANTES\Administrator, CORP\Domain Admins, CORP\CM01$Keep only what is needed: the Configuration Manager service accounts and the named administrators.—
Wide directory group in the local administratorsDP-NANTES — CORP\Domain AdminsCriticalCORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.Remove the group and use one dedicated to administering this server.—
Built-in administrator accountDP-NANTES — AdministratorOKThe built-in account Administrator is disabled.——
Guest accountDP-NANTES — GuestOKThe guest account Guest is disabled.——
LAPSDP-NANTESOKA LAPS configuration is present on this server (windows).——
Local Administrators groupDP-LYONTo verify4 member(s): DP-LYON\Administrator, DP-LYON\support, CORP\Domain Admins, CORP\CM01$Keep only what is needed: the Configuration Manager service accounts and the named administrators.—
Wide directory group in the local administratorsDP-LYON — CORP\Domain AdminsCriticalCORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.Remove the group and use one dedicated to administering this server.—
Built-in administrator accountDP-LYON — AdministratorAttentionThe built-in account Administrator is enabled.Disable it in favour of named accounts, or manage its password with LAPS.↗
Guest accountDP-LYON — GuestCriticalThe guest account Guest is enabled.Disable the guest account.—
LAPSDP-LYONTo verifyThis reading could not be taken on the server, so it is reported as unmeasured rather than counted as a pass.Re-run the collector with local administrator rights on the site server, or check this setting by hand.—
Local Administrators groupSQL01To verify4 member(s): SQL01\Administrator, CORP\Domain Admins, CORP\GG-SCCM-Admins, CORP\Domain UsersKeep only what is needed: the Configuration Manager service accounts and the named administrators.—
Wide directory group in the local administratorsSQL01 — CORP\Domain AdminsCriticalCORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.Remove the group and use one dedicated to administering this server.—
Built-in administrator accountSQL01 — AdministratorAttentionThe built-in account Administrator is enabled.Disable it in favour of named accounts, or manage its password with LAPS.↗
Guest accountSQL01 — GuestOKThe guest account Guest is disabled.——
LAPSSQL01To verifyThis reading could not be taken on the server, so it is reported as unmeasured rather than counted as a pass.Re-run the collector with local administrator rights on the site server, or check this setting by hand.—
Local Administrators groupCM01To verify4 member(s): CM01\Administrator, CORP\Domain Admins, CORP\GG-SCCM-Admins, CORP\svc-cm-pushKeep only what is needed: the Configuration Manager service accounts and the named administrators.—
Wide directory group in the local administratorsCM01 — CORP\Domain AdminsCriticalCORP\Domain Admins is a directory group with a very wide membership, and it is a local administrator of the site server.Remove the group and use one dedicated to administering this server.—
Built-in administrator accountCM01 — AdministratorAttentionThe built-in account Administrator is enabled.Disable it in favour of named accounts, or manage its password with LAPS.↗
Guest accountCM01 — GuestOKThe guest account Guest is disabled.——
LAPSCM01OKA LAPS configuration is present on this server (windows).——
Password policy6 Attention 9 OK
CheckStatusDetailRecommendationDoc.
Minimum password lengthRPT01OKLocal minimum password length is 14 characters.——
Password complexityRPT01OKPassword complexity is required locally.——
Account lockout thresholdRPT01OKAccounts lock after 10 failed attempt(s).——
Minimum password lengthDP-NANTESOKLocal minimum password length is 14 characters.——
Password complexityDP-NANTESOKPassword complexity is required locally.——
Account lockout thresholdDP-NANTESOKAccounts lock after 10 failed attempt(s).——
Minimum password lengthDP-LYONAttentionLocal minimum password length is 7 characters.Raise the minimum to fourteen characters or more.—
Password complexityDP-LYONAttentionPassword complexity is not required locally.Require complexity in the local security policy.—
Account lockout thresholdDP-LYONAttentionNo account lockout threshold is set locally.Set a lockout threshold, ten attempts for instance, so a password cannot be guessed at leisure.—
Minimum password lengthSQL01AttentionLocal minimum password length is 8 characters.Raise the minimum to fourteen characters or more.—
Password complexitySQL01OKPassword complexity is required locally.——
Account lockout thresholdSQL01AttentionNo account lockout threshold is set locally.Set a lockout threshold, ten attempts for instance, so a password cannot be guessed at leisure.—
Minimum password lengthCM01AttentionLocal minimum password length is 12 characters.Raise the minimum to fourteen characters or more.—
Password complexityCM01OKPassword complexity is required locally.——
Account lockout thresholdCM01OKAccounts lock after 10 failed attempt(s).——
Services5 Attention 12 OK 6 To verify
CheckStatusDetailRecommendationDoc.
Service under a named accountRPT01 — SQLServerReportingServicesTo verifySQL Server Reporting Services runs as NT SERVICE\SQLServerReportingServices and is currently Running.Confirm this account holds only the rights the service needs.—
WebClient service (WebDAV)RPT01OKThe WebClient service is absent, disabled or stopped.——
Print Spooler serviceRPT01OKThe Print Spooler service is absent, disabled or stopped.——
Unquoted service pathsRPT01OKNo service has an unquoted executable path outside the Windows directory.——
Services running under a named accountDP-NANTESOKNo third-party service runs under a named account.——
WebClient service (WebDAV)DP-NANTESOKThe WebClient service is absent, disabled or stopped.——
Print Spooler serviceDP-NANTESOKThe Print Spooler service is absent, disabled or stopped.——
Unquoted service pathsDP-NANTESOKNo service has an unquoted executable path outside the Windows directory.——
Services running under a named accountDP-LYONOKNo third-party service runs under a named account.——
WebClient service (WebDAV)DP-LYONAttentionThe WebClient service is running on this server.WebDAV makes credential coercion easier. Disable the service unless something needs it.—
Print Spooler serviceDP-LYONAttentionThe Print Spooler service is running on this server.A known vector for privilege escalation and coercion. Disable it unless this server prints.—
Unquoted service pathsDP-LYONOKNo service has an unquoted executable path outside the Windows directory.——
Service under a named accountSQL01 — MSSQLSERVERTo verifySQL Server (MSSQLSERVER) runs as CORP\svc-sql and is currently Running.Confirm this account holds only the rights the service needs.—
Service under a named accountSQL01 — SQLSERVERAGENTTo verifySQL Server Agent (MSSQLSERVER) runs as CORP\svc-sql and is currently Running.Confirm this account holds only the rights the service needs.—
WebClient service (WebDAV)SQL01OKThe WebClient service is absent, disabled or stopped.——
Print Spooler serviceSQL01AttentionThe Print Spooler service is running on this server.A known vector for privilege escalation and coercion. Disable it unless this server prints.—
Unquoted service pathsSQL01Attention1 service(s) have an executable path that contains a space and is not quoted: SqlMonitor : C:\Program Files\Contoso Tools\sqlmon.exe -serviceQuote each executable path so a file dropped earlier in it cannot be started instead.—
Service under a named accountCM01 — SMS_EXECUTIVETo verifySMS_EXECUTIVE runs as LocalSystem and is currently Running.Confirm this account holds only the rights the service needs.—
Service under a named accountCM01 — CcmExecTo verifySMS Agent Host runs as LocalSystem and is currently Running.Confirm this account holds only the rights the service needs.—
Service under a named accountCM01 — BackupAgentTo verifyContoso Backup Agent runs as CORP\svc-backup and is currently Running.Confirm this account holds only the rights the service needs.—
WebClient service (WebDAV)CM01OKThe WebClient service is absent, disabled or stopped.——
Print Spooler serviceCM01AttentionThe Print Spooler service is running on this server.A known vector for privilege escalation and coercion. Disable it unless this server prints.—
Unquoted service pathsCM01OKNo service has an unquoted executable path outside the Windows directory.——
Network protocols1 Critical 11 Attention 14 OK 4 To verify
CheckStatusDetailRecommendationDoc.
SMBv1 protocolRPT01OKSMBv1 is disabled.——
SMB signing required (server)RPT01OKSMB signing is required for inbound connections.——
SMB signing required (client)RPT01OKSMB signing is required for outbound connections.——
NetBIOS over TCP/IPRPT01OKNetBIOS over TCP/IP is disabled on every active IP interface.——
LLMNRRPT01OKLLMNR is disabled by policy.——
mDNSRPT01OKmDNS is disabled.——
SMBv1 protocolDP-NANTESOKSMBv1 is disabled.——
SMB signing required (server)DP-NANTESOKSMB signing is required for inbound connections.——
SMB signing required (client)DP-NANTESOKSMB signing is required for outbound connections.——
NetBIOS over TCP/IPDP-NANTESOKNetBIOS over TCP/IP is disabled on every active IP interface.——
LLMNRDP-NANTESOKLLMNR is disabled by policy.——
mDNSDP-NANTESTo verifymDNS is not explicitly disabled.On versions that support it, consider disabling mDNS too.—
SMBv1 protocolDP-LYONCriticalSMBv1 is enabled on this server.Remove SMBv1: the protocol is obsolete and unauthenticated attacks against it are public.—
SMB signing required (server)DP-LYONAttentionSMB signing is not required for inbound connections.Require SMB signing so an intercepted session cannot be relayed.—
SMB signing required (client)DP-LYONAttentionSMB signing is not required for outbound connections.Require SMB signing on outbound connections as well; the server half alone does not stop a relay.—
NetBIOS over TCP/IPDP-LYONAttentionNetBIOS over TCP/IP is enabled or left at its default on: Ethernet0; Ethernet1Disable NetBIOS over TCP/IP to close name-poisoning attacks such as Responder.—
LLMNRDP-LYONAttentionLLMNR is not explicitly disabled, so the default applies and it answers.Disable LLMNR by group policy, alongside NetBIOS.—
mDNSDP-LYONTo verifymDNS is not explicitly disabled.On versions that support it, consider disabling mDNS too.—
SMBv1 protocolSQL01OKSMBv1 is disabled.——
SMB signing required (server)SQL01AttentionSMB signing is not required for inbound connections.Require SMB signing so an intercepted session cannot be relayed.—
SMB signing required (client)SQL01AttentionSMB signing is not required for outbound connections.Require SMB signing on outbound connections as well; the server half alone does not stop a relay.—
NetBIOS over TCP/IPSQL01AttentionNetBIOS over TCP/IP is enabled or left at its default on: Ethernet0Disable NetBIOS over TCP/IP to close name-poisoning attacks such as Responder.—
LLMNRSQL01AttentionLLMNR is not explicitly disabled, so the default applies and it answers.Disable LLMNR by group policy, alongside NetBIOS.—
mDNSSQL01To verifymDNS is not explicitly disabled.On versions that support it, consider disabling mDNS too.—
SMBv1 protocolCM01OKSMBv1 is disabled.——
SMB signing required (server)CM01OKSMB signing is required for inbound connections.——
SMB signing required (client)CM01AttentionSMB signing is not required for outbound connections.Require SMB signing on outbound connections as well; the server half alone does not stop a relay.—
NetBIOS over TCP/IPCM01AttentionNetBIOS over TCP/IP is enabled or left at its default on: Ethernet0Disable NetBIOS over TCP/IP to close name-poisoning attacks such as Responder.—
LLMNRCM01AttentionLLMNR is not explicitly disabled, so the default applies and it answers.Disable LLMNR by group policy, alongside NetBIOS.—
mDNSCM01To verifymDNS is not explicitly disabled.On versions that support it, consider disabling mDNS too.—
Firewall3 Critical 12 OK
CheckStatusDetailRecommendationDoc.
Windows Firewall profileRPT01 — DomainOKThe Domain profile is enabled.——
Windows Firewall profileRPT01 — PrivateOKThe Private profile is enabled.——
Windows Firewall profileRPT01 — PublicOKThe Public profile is enabled.——
Windows Firewall profileDP-NANTES — DomainOKThe Domain profile is enabled.——
Windows Firewall profileDP-NANTES — PrivateOKThe Private profile is enabled.——
Windows Firewall profileDP-NANTES — PublicOKThe Public profile is enabled.——
Windows Firewall profileDP-LYON — DomainCriticalThe Domain profile is disabled.Turn the firewall back on for this profile.—
Windows Firewall profileDP-LYON — PrivateCriticalThe Private profile is disabled.Turn the firewall back on for this profile.—
Windows Firewall profileDP-LYON — PublicOKThe Public profile is enabled.——
Windows Firewall profileSQL01 — DomainCriticalThe Domain profile is disabled.Turn the firewall back on for this profile.—
Windows Firewall profileSQL01 — PrivateOKThe Private profile is enabled.——
Windows Firewall profileSQL01 — PublicOKThe Public profile is enabled.——
Windows Firewall profileCM01 — DomainOKThe Domain profile is enabled.——
Windows Firewall profileCM01 — PrivateOKThe Private profile is enabled.——
Windows Firewall profileCM01 — PublicOKThe Public profile is enabled.——
NTLM3 Attention 5 OK 7 To verify
CheckStatusDetailRecommendationDoc.
LAN Manager authentication levelRPT01OKSet to 5, which sends NTLMv2 only and refuses LM and NTLM.——
Outgoing NTLM trafficRPT01OKOutgoing NTLM traffic is restricted (value 2).——
Incoming NTLM trafficRPT01OKIncoming NTLM traffic is restricted (value 2).——
LAN Manager authentication levelDP-NANTESOKSet to 5, which sends NTLMv2 only and refuses LM and NTLM.——
Outgoing NTLM trafficDP-NANTESOKOutgoing NTLM traffic is restricted (value 1).——
Incoming NTLM trafficDP-NANTESTo verifyIncoming NTLM traffic is not restricted (value 0).On a server as sensitive as a site server, evaluate this restriction in audit mode.—
LAN Manager authentication levelDP-LYONAttentionSet to 2, which still accepts authentication weaker than NTLMv2.Set the LAN Manager authentication level to 5, which sends NTLMv2 only and refuses LM and NTLM.↗
Outgoing NTLM trafficDP-LYONTo verifyOutgoing NTLM traffic is not restricted (value 0).Consider restricting it, in audit mode first, as part of moving away from NTLM towards Kerberos.—
Incoming NTLM trafficDP-LYONTo verifyIncoming NTLM traffic is not restricted (value 0).On a server as sensitive as a site server, evaluate this restriction in audit mode.—
LAN Manager authentication levelSQL01AttentionSet to 3, which still accepts authentication weaker than NTLMv2.Set the LAN Manager authentication level to 5, which sends NTLMv2 only and refuses LM and NTLM.↗
Outgoing NTLM trafficSQL01To verifyOutgoing NTLM traffic is not restricted (value 0).Consider restricting it, in audit mode first, as part of moving away from NTLM towards Kerberos.—
Incoming NTLM trafficSQL01To verifyIncoming NTLM traffic is not restricted (value 0).On a server as sensitive as a site server, evaluate this restriction in audit mode.—
LAN Manager authentication levelCM01AttentionSet to 3, which still accepts authentication weaker than NTLMv2.Set the LAN Manager authentication level to 5, which sends NTLMv2 only and refuses LM and NTLM.↗
Outgoing NTLM trafficCM01To verifyOutgoing NTLM traffic is not restricted (value 0).Consider restricting it, in audit mode first, as part of moving away from NTLM towards Kerberos.—
Incoming NTLM trafficCM01To verifyIncoming NTLM traffic is not restricted (value 0).On a server as sensitive as a site server, evaluate this restriction in audit mode.—
Credential protection2 Critical 3 Attention 15 OK 5 To verify
CheckStatusDetailRecommendationDoc.
WDigest credential cachingRPT01OKWDigest is disabled or not configured.——
LSA protection (RunAsPPL)RPT01OKThe LSA process runs protected.——
Credential GuardRPT01OKCredential Guard is running.——
AlwaysInstallElevatedRPT01OKNot enabled at machine level.——
Automatic logonRPT01OKAutomatic logon is not configured.——
WDigest credential cachingDP-NANTESOKWDigest is disabled or not configured.——
LSA protection (RunAsPPL)DP-NANTESOKThe LSA process runs protected.——
Credential GuardDP-NANTESTo verifyCredential Guard does not appear to be running.Evaluate enabling it, bearing in mind the hardware prerequisites and agent compatibility.—
AlwaysInstallElevatedDP-NANTESOKNot enabled at machine level.——
Automatic logonDP-NANTESOKAutomatic logon is not configured.——
WDigest credential cachingDP-LYONCriticalWDigest is enabled, so plain-text passwords can sit in memory.Set UseLogonCredential to 0 so credentials stop being cached in clear text.—
LSA protection (RunAsPPL)DP-LYONAttentionThe LSA process does not run protected.Enable LSA protection once third-party drivers and agents have been tested against it.—
Credential GuardDP-LYONTo verifyCredential Guard does not appear to be running.Evaluate enabling it, bearing in mind the hardware prerequisites and agent compatibility.—
AlwaysInstallElevatedDP-LYONOKNot enabled at machine level.——
Automatic logonDP-LYONCriticalAutomatic logon is configured and its password sits in the registry in clear text.Turn off automatic logon on a production server, and change the password immediately if one is stored.—
WDigest credential cachingSQL01To verifyThis reading could not be taken on the server, so it is reported as unmeasured rather than counted as a pass.Re-run the collector with local administrator rights on the site server, or check this setting by hand.—
LSA protection (RunAsPPL)SQL01AttentionThe LSA process does not run protected.Enable LSA protection once third-party drivers and agents have been tested against it.—
Credential GuardSQL01To verifyCredential Guard does not appear to be running.Evaluate enabling it, bearing in mind the hardware prerequisites and agent compatibility.—
AlwaysInstallElevatedSQL01OKNot enabled at machine level.——
Automatic logonSQL01OKAutomatic logon is not configured.——
WDigest credential cachingCM01OKWDigest is disabled or not configured.——
LSA protection (RunAsPPL)CM01AttentionThe LSA process does not run protected.Enable LSA protection once third-party drivers and agents have been tested against it.—
Credential GuardCM01To verifyCredential Guard does not appear to be running.Evaluate enabling it, bearing in mind the hardware prerequisites and agent compatibility.—
AlwaysInstallElevatedCM01OKNot enabled at machine level.——
Automatic logonCM01OKAutomatic logon is not configured.——
Remote Desktop1 Critical 4 OK 4 To verify
CheckStatusDetailRecommendationDoc.
Remote DesktopRPT01OKRemote Desktop connections are refused.——
Remote DesktopDP-NANTESTo verifyRemote Desktop connections are allowed on this server.Restrict Remote Desktop as tightly as possible: firewall, a restricted group, and a bastion or privileged workstation.—
Network Level AuthenticationDP-NANTESOKNetwork Level Authentication is required.——
Remote DesktopDP-LYONTo verifyRemote Desktop connections are allowed on this server.Restrict Remote Desktop as tightly as possible: firewall, a restricted group, and a bastion or privileged workstation.—
Network Level AuthenticationDP-LYONCriticalNetwork Level Authentication is not required, so the logon screen is reachable before anyone authenticates.Require Network Level Authentication, so an unauthenticated caller never reaches the session host.—
Remote DesktopSQL01To verifyRemote Desktop connections are allowed on this server.Restrict Remote Desktop as tightly as possible: firewall, a restricted group, and a bastion or privileged workstation.—
Network Level AuthenticationSQL01OKNetwork Level Authentication is required.——
Remote DesktopCM01To verifyRemote Desktop connections are allowed on this server.Restrict Remote Desktop as tightly as possible: firewall, a restricted group, and a bastion or privileged workstation.—
Network Level AuthenticationCM01OKNetwork Level Authentication is required.——
WinRM5 Attention 5 OK
CheckStatusDetailRecommendationDoc.
WinRM listenersRPT01OKNo plain HTTP WinRM listener is configured.——
WinRM TrustedHostsRPT01OKTrustedHosts is empty.——
WinRM listenersDP-NANTESAttentionAt least one WinRM listener accepts plain HTTP.Prefer an HTTPS listener with a valid certificate.—
WinRM TrustedHostsDP-NANTESOKTrustedHosts is empty.——
WinRM listenersDP-LYONAttentionAt least one WinRM listener accepts plain HTTP.Prefer an HTTPS listener with a valid certificate.—
WinRM TrustedHostsDP-LYONAttentionTrustedHosts is set to the wildcard, so this client will authenticate to any host.Replace the wildcard with an explicit list of trusted servers.—
WinRM listenersSQL01AttentionAt least one WinRM listener accepts plain HTTP.Prefer an HTTPS listener with a valid certificate.—
WinRM TrustedHostsSQL01OKTrustedHosts is empty.——
WinRM listenersCM01AttentionAt least one WinRM listener accepts plain HTTP.Prefer an HTTPS listener with a valid certificate.—
WinRM TrustedHostsCM01OKTrustedHosts is empty.——
Endpoint protection1 Attention 7 OK 7 To verify
CheckStatusDetailRecommendationDoc.
Microsoft Defender AntivirusRPT01OKReal-time protection is on and the signatures are 0 day(s) old.——
Attack surface reduction rulesRPT01OK14 attack surface reduction rule(s) configured.——
AppLockerRPT01OK36 effective AppLocker rule(s).——
Microsoft Defender AntivirusDP-NANTESOKReal-time protection is on and the signatures are 1 day(s) old.——
Attack surface reduction rulesDP-NANTESOK6 attack surface reduction rule(s) configured.——
AppLockerDP-NANTESTo verifyNo effective AppLocker rule was found.Evaluate application control — AppLocker or WDAC — on a server this sensitive.—
Microsoft Defender AntivirusDP-LYONAttentionReal-time protection: true. Antivirus engine: true. Signatures are 14 day(s) old.Make sure real-time protection is on and the signatures current, or confirm an equivalent third-party agent.—
Attack surface reduction rulesDP-LYONTo verifyNo attack surface reduction rule is configured.Enable attack surface reduction rules, starting with the one that blocks credential theft from LSASS.—
AppLockerDP-LYONTo verifyNo effective AppLocker rule was found.Evaluate application control — AppLocker or WDAC — on a server this sensitive.—
Microsoft Defender AntivirusSQL01OKReal-time protection is on and the signatures are 2 day(s) old.——
Attack surface reduction rulesSQL01To verifyNo attack surface reduction rule is configured.Enable attack surface reduction rules, starting with the one that blocks credential theft from LSASS.—
AppLockerSQL01To verifyNo effective AppLocker rule was found.Evaluate application control — AppLocker or WDAC — on a server this sensitive.—
Microsoft Defender AntivirusCM01OKReal-time protection is on and the signatures are 1 day(s) old.——
Attack surface reduction rulesCM01To verifyNo attack surface reduction rule is configured.Enable attack surface reduction rules, starting with the one that blocks credential theft from LSASS.—
AppLockerCM01To verifyNo effective AppLocker rule was found.Evaluate application control — AppLocker or WDAC — on a server this sensitive.—
Operating system updates2 Attention 3 OK
CheckStatusDetailRecommendationDoc.
Most recent operating system updateRPT01 — KB5043050OKThe most recent update on record is KB5043050, installed on 2026-09-12 00:00 UTC — 10 day(s) ago.——
Most recent operating system updateDP-NANTES — KB5043050OKThe most recent update on record is KB5043050, installed on 2026-09-12 00:00 UTC — 10 day(s) ago.——
Most recent operating system updateDP-LYON — KB5036893AttentionThe most recent update on record is KB5036893, installed on 2026-04-10 00:00 UTC — 165 day(s) ago.Review the patching process for this server.—
Most recent operating system updateSQL01 — KB5040437AttentionThe most recent update on record is KB5040437, installed on 2026-06-12 00:00 UTC — 102 day(s) ago.Review the patching process for this server.—
Most recent operating system updateCM01 — KB5043050OKThe most recent update on record is KB5043050, installed on 2026-09-11 00:00 UTC — 11 day(s) ago.——
Auditing3 Attention 2 OK
CheckStatusDetailRecommendationDoc.
Command line in process creation eventsRPT01OKProcess creation events include the command line.——
Command line in process creation eventsDP-NANTESOKProcess creation events include the command line.——
Command line in process creation eventsDP-LYONAttentionProcess creation events do not include the command line.Include the command line in event 4688; without it, process auditing rarely names what actually ran.—
Command line in process creation eventsSQL01AttentionProcess creation events do not include the command line.Include the command line in event 4688; without it, process auditing rarely names what actually ran.—
Command line in process creation eventsCM01AttentionProcess creation events do not include the command line.Include the command line in event 4688; without it, process auditing rarely names what actually ran.—
PowerShell4 Attention 8 OK 8 To verify
CheckStatusDetailRecommendationDoc.
PowerShell script block loggingRPT01OKScript block logging is enabled.——
PowerShell module loggingRPT01OKModule logging is enabled.——
PowerShell transcriptionRPT01OKTranscription is enabled.——
PowerShell v2 engineRPT01OKThe PowerShell v2 engine is removed.——
PowerShell script block loggingDP-NANTESOKScript block logging is enabled.——
PowerShell module loggingDP-NANTESTo verifyModule logging is not enabled.Consider enabling module logging alongside script block logging.—
PowerShell transcriptionDP-NANTESTo verifyTranscription is not enabled.Consider enabling transcription to a protected share.—
PowerShell v2 engineDP-NANTESOKThe PowerShell v2 engine is removed.——
PowerShell script block loggingDP-LYONAttentionScript block logging is not enabled.Enable PowerShell script block logging: it is the single most useful source for detecting what a script did.—
PowerShell module loggingDP-LYONTo verifyModule logging is not enabled.Consider enabling module logging alongside script block logging.—
PowerShell transcriptionDP-LYONTo verifyTranscription is not enabled.Consider enabling transcription to a protected share.—
PowerShell v2 engineDP-LYONAttentionThe PowerShell v2 engine is still installed.Remove PowerShell v2: it supports neither AMSI nor script block logging, and it can be requested deliberately to escape both.—
PowerShell script block loggingSQL01AttentionScript block logging is not enabled.Enable PowerShell script block logging: it is the single most useful source for detecting what a script did.—
PowerShell module loggingSQL01To verifyModule logging is not enabled.Consider enabling module logging alongside script block logging.—
PowerShell transcriptionSQL01To verifyTranscription is not enabled.Consider enabling transcription to a protected share.—
PowerShell v2 engineSQL01AttentionThe PowerShell v2 engine is still installed.Remove PowerShell v2: it supports neither AMSI nor script block logging, and it can be requested deliberately to escape both.—
PowerShell script block loggingCM01OKScript block logging is enabled.——
PowerShell module loggingCM01To verifyModule logging is not enabled.Consider enabling module logging alongside script block logging.—
PowerShell transcriptionCM01To verifyTranscription is not enabled.Consider enabling transcription to a protected share.—
PowerShell v2 engineCM01OKThe PowerShell v2 engine is removed.——
System1 Attention 11 OK 8 To verify
CheckStatusDetailRecommendationDoc.
User Account ControlRPT01OKUser Account Control is enabled.——
Anonymous enumeration of SAM accountsRPT01OKAnonymous enumeration of SAM accounts is refused.——
System drive encryptionRPT01OKThe system drive is encrypted with BitLocker.——
Time synchronisation sourceRPT01 — DC01.corp.localTo verifyCurrent source: DC01.corp.localReliable time is a prerequisite for Kerberos, whose default tolerance is five minutes.—
User Account ControlDP-NANTESOKUser Account Control is enabled.——
Anonymous enumeration of SAM accountsDP-NANTESOKAnonymous enumeration of SAM accounts is refused.——
System drive encryptionDP-NANTESOKThe system drive is encrypted with BitLocker.——
Time synchronisation sourceDP-NANTES — DC01.corp.localTo verifyCurrent source: DC01.corp.localReliable time is a prerequisite for Kerberos, whose default tolerance is five minutes.—
User Account ControlDP-LYONOKUser Account Control is enabled.——
Anonymous enumeration of SAM accountsDP-LYONAttentionAnonymous enumeration of SAM accounts is not explicitly refused.Refuse anonymous enumeration of SAM accounts and shares.—
System drive encryptionDP-LYONTo verifyThe system drive is not encrypted with BitLocker.Worth enabling mainly where the machine could be physically taken.—
Time synchronisation sourceDP-LYON — Local CMOS ClockTo verifyCurrent source: Local CMOS ClockReliable time is a prerequisite for Kerberos, whose default tolerance is five minutes.—
User Account ControlSQL01OKUser Account Control is enabled.——
Anonymous enumeration of SAM accountsSQL01OKAnonymous enumeration of SAM accounts is refused.——
System drive encryptionSQL01To verifyThe system drive is not encrypted with BitLocker.Worth enabling mainly where the machine could be physically taken.—
Time synchronisation sourceSQL01 — DC01.corp.localTo verifyCurrent source: DC01.corp.localReliable time is a prerequisite for Kerberos, whose default tolerance is five minutes.—
User Account ControlCM01OKUser Account Control is enabled.——
Anonymous enumeration of SAM accountsCM01OKAnonymous enumeration of SAM accounts is refused.——
System drive encryptionCM01To verifyThe system drive is not encrypted with BitLocker.Worth enabling mainly where the machine could be physically taken.—
Time synchronisation sourceCM01 — DC01.corp.localTo verifyCurrent source: DC01.corp.localReliable time is a prerequisite for Kerberos, whose default tolerance is five minutes.—
TLS7 Attention 20 OK 3 To verify
CheckStatusDetailRecommendationDoc.
Legacy TLS/SSL protocolRPT01 — SSL 2.0OKSSL 2.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolRPT01 — SSL 3.0OKSSL 3.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolRPT01 — TLS 1.0OKTLS 1.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolRPT01 — TLS 1.1OKTLS 1.1 is explicitly disabled server-side.——
TLS 1.2RPT01 — TLS 1.2OKTLS 1.2 is active, or at least not explicitly disabled.——
Cipher suitesRPT01OKNo obviously weak cipher suite is enabled.——
Legacy TLS/SSL protocolDP-NANTES — SSL 2.0OKSSL 2.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolDP-NANTES — SSL 3.0OKSSL 3.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolDP-NANTES — TLS 1.0OKTLS 1.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolDP-NANTES — TLS 1.1OKTLS 1.1 is explicitly disabled server-side.——
TLS 1.2DP-NANTES — TLS 1.2OKTLS 1.2 is active, or at least not explicitly disabled.——
Cipher suitesDP-NANTESOKNo obviously weak cipher suite is enabled.——
Legacy TLS/SSL protocolDP-LYON — SSL 2.0To verifySSL 2.0 is not configured either way, so the operating system default decides.Disable this protocol explicitly unless something still needs it.—
Legacy TLS/SSL protocolDP-LYON — SSL 3.0AttentionSSL 3.0 is active server-side.Disable this protocol: it is obsolete.—
Legacy TLS/SSL protocolDP-LYON — TLS 1.0AttentionTLS 1.0 is active server-side.Disable this protocol: it is obsolete.—
Legacy TLS/SSL protocolDP-LYON — TLS 1.1AttentionTLS 1.1 is active server-side.Disable this protocol: it is obsolete.—
TLS 1.2DP-LYON — TLS 1.2OKTLS 1.2 is active, or at least not explicitly disabled.——
Cipher suitesDP-LYONAttention1 weak cipher suite(s) remain enabled: TLS_RSA_WITH_3DES_EDE_CBC_SHARemove the obsolete suites from the cipher order.—
Legacy TLS/SSL protocolSQL01 — SSL 2.0OKSSL 2.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolSQL01 — SSL 3.0OKSSL 3.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolSQL01 — TLS 1.0AttentionTLS 1.0 is active server-side.Disable this protocol: it is obsolete.—
Legacy TLS/SSL protocolSQL01 — TLS 1.1AttentionTLS 1.1 is active server-side.Disable this protocol: it is obsolete.—
TLS 1.2SQL01 — TLS 1.2OKTLS 1.2 is active, or at least not explicitly disabled.——
Cipher suitesSQL01Attention2 weak cipher suite(s) remain enabled: TLS_RSA_WITH_3DES_EDE_CBC_SHA, TLS_RSA_WITH_RC4_128_SHARemove the obsolete suites from the cipher order.—
Legacy TLS/SSL protocolCM01 — SSL 2.0OKSSL 2.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolCM01 — SSL 3.0OKSSL 3.0 is explicitly disabled server-side.——
Legacy TLS/SSL protocolCM01 — TLS 1.0To verifyTLS 1.0 is not configured either way, so the operating system default decides.Disable this protocol explicitly unless something still needs it.—
Legacy TLS/SSL protocolCM01 — TLS 1.1To verifyTLS 1.1 is not configured either way, so the operating system default decides.Disable this protocol explicitly unless something still needs it.—
TLS 1.2CM01 — TLS 1.2OKTLS 1.2 is active, or at least not explicitly disabled.——
Cipher suitesCM01OKNo obviously weak cipher suite is enabled.——
Active Directory5 OK
CheckStatusDetailRecommendationDoc.
Unconstrained Kerberos delegationRPT01 — RPT01OKThe computer account is not trusted for unconstrained delegation.——
Unconstrained Kerberos delegationDP-NANTES — DP-NANTESOKThe computer account is not trusted for unconstrained delegation.——
Unconstrained Kerberos delegationDP-LYON — DP-LYONOKThe computer account is not trusted for unconstrained delegation.——
Unconstrained Kerberos delegationSQL01 — SQL01OKThe computer account is not trusted for unconstrained delegation.——
Unconstrained Kerberos delegationCM01 — CM01OKThe computer account is not trusted for unconstrained delegation.——

The Configuration Manager logs of every site system, read over the last 7 days, and the status messages of the last 30 days. Four views: an analysis (what the errors probably have in common and what to do), a chronology, every distinct error file by file, and the status messages component by component.

Times shown in the time zone of the machine that produced the report (UTC+02:00). Hover a date for UTC.

Logs read on 6 machine(s) of 6.

SQL01.corp.local: no Configuration Manager log changed in the last 7 days was found.

Machines read

6 / 6

15 log files

Problems to handle

7

families of errors, section 1

Errors

127

9 distinct messages

Warnings

97

10 distinct messages

Active < 24 h

19

messages seen in the last 24 h

Last error

10-05 16:11

just now

1. Analysis

Messages are grouped by probable cause. A family last seen more than 30 days ago is filed as “To verify”, not as an alert. The groupings are leads, not verdicts: read the sample messages.

CriticalNot enough disk space62 occurrence(s) · CM01, DP-LYON · last 10-05 16:11 (just now)

What to do: A component could not write for lack of space. Check the volume of the inboxes, the content library (SCCMContentLib) and SQL; free or extend it before anything else: a full disk stalls the whole site.

From 2026-09-29 11:40 to 2026-10-05 16:11 · Logs to open (CMTrace): distmgr.logsmsdpprov.log

MachineLogMessage (latest occurrence)CountLast
CM01distmgr.logFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.342026-10-05 16:11just now
DP-LYONsmsdpprov.logFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.282026-10-05 16:05just now
CriticalAccess to the site SQL database17 occurrence(s) · CM01, RPT01 · last 10-05 14:35 (just now)

What to do: The component could not reach or query the site database. Check that SQL is running, network connectivity to the instance, the SPNs/Kerberos of the SQL service account, room for the data and log files, and the site server computer account’s rights on the database.

From 2026-09-29 16:40 to 2026-10-05 14:35 · Logs to open (CMTrace): smsdbmon.logsrsrp.log

MachineLogMessage (latest occurrence)CountLast
RPT01srsrp.logLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.132026-10-05 14:35just now
CM01smsdbmon.logSQL error: [40001][1205][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 87) was deadlocked on lock resources with another process.42026-10-04 10:35just now
AttentionContent distribution51 occurrence(s) · CM01, DP-LYON, DP-NANTES · last 10-05 15:41 (just now)

What to do: Read distmgr.log and PkgXferMgr.log on the site server, then smsdpprov.log on the distribution point. Frequent causes: package source unreachable, room on the DP, computer account rights on the source share, the DP’s IIS/WebDAV.

From 2026-09-29 12:37 to 2026-10-05 15:41 · Logs to open (CMTrace): distmgr.logsmsdpmon.logsmsdpusage.log

MachineLogMessage (latest occurrence)CountLast
CM01distmgr.logDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.92026-10-05 15:23just now
CM01distmgr.logWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).222026-10-05 15:41just now
DP-LYONsmsdpusage.logWarning: content library free space below 5% on drive E:.122026-10-05 15:35just now
DP-LYONsmsdpmon.logContent validation for package PS100002 timed out after 3600 seconds, will retry.62026-10-05 08:35just now
DP-NANTESsmsdpmon.logConnection to the management point timed out, retrying in 60 seconds.22026-10-03 14:35just now
AttentionSoftware update point and WSUS23 occurrence(s) · CM01 · last 10-05 13:35 (just now)

What to do: Read WCM.log (SUP configuration and WSUS subscription) then wsyncmgr.log (synchronisation). Check that the IIS WsusPool is running and not recycling (private memory), that WSUS answers on its port (8530/8531) and that the proxy is right for the upstream sync.

From 2026-09-29 10:04 to 2026-10-05 13:35 · Logs to open (CMTrace): ruleengine.logwcm.logwsyncmgr.log

MachineLogMessage (latest occurrence)CountLast
CM01ruleengine.logFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101112026-10-04 14:35just now
CM01wsyncmgr.logSync failed. Will retry in 60 minutes.72026-10-05 13:35just now
CM01wcm.logTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.52026-10-05 10:35just now
AttentionNetwork, name resolution or proxy7 occurrence(s) · CM01 · last 10-05 13:35 (just now)

What to do: The target did not answer. Test from the server concerned: DNS resolution (Resolve-DnsName), ports (Test-NetConnection -Port 445/135/443/80/1433), firewalls, and the proxy set on the site system when the traffic goes out to the Internet.

From 2026-09-29 15:16 to 2026-10-05 13:35 · Logs to open (CMTrace): wsyncmgr.log

MachineLogMessage (latest occurrence)CountLast
CM01wsyncmgr.logSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer72026-10-05 13:35just now
AttentionCertificate, TLS or HTTPS15 occurrence(s) · MP02 · last 10-05 12:35 (just now)

What to do: A secure handshake failed. Check certificate validity and chain (expiry, trusted root, reachable revocation list), the machines’ clocks, TLS 1.2 enabled on client and server (.NET SchUseStrongCrypto), and the HTTPS binding in IIS.

From 2026-09-30 22:52 to 2026-10-05 12:35 · Logs to open (CMTrace): MP_Location.log

MachineLogMessage (latest occurrence)CountLast
MP02MP_Location.logMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.152026-10-05 12:35just now
AttentionAccess denied6 occurrence(s) · CM01 · last 10-04 18:35 (just now)

What to do: An account lacks the rights it needs. Find which account in the message (site server computer account, network access account, site system installation account) and check its membership of the target’s local Administrators group and its share and folder rights.

From 2026-09-29 11:04 to 2026-10-04 18:35 · Logs to open (CMTrace): smsbkup.log

MachineLogMessage (latest occurrence)CountLast
CM01smsbkup.logError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)62026-10-04 18:35just now
To verifyOther messages13 occurrence(s) · RPT01 · last 10-05 14:35 (just now)

What to do: Messages with no known signature: read them in their log with CMTrace, starting with the oldest occurrence of a series.

From 2026-09-30 01:39 to 2026-10-05 14:35 · Logs to open (CMTrace): srsrp.log

MachineLogMessage (latest occurrence)CountLast
RPT01srsrp.logRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.132026-10-05 14:35just now
To verifyCollection evaluation18 occurrence(s) · CM01 · last 10-05 14:35 (just now)

What to do: Read colleval.log: failing or slow evaluations usually come from an invalid WQL query or too many incremental collections. The Collection Evaluation Viewer (site tools) shows the durations.

From 2026-09-29 08:19 to 2026-10-05 14:35 · Logs to open (CMTrace): colleval.log

MachineLogMessage (latest occurrence)CountLast
CM01colleval.logCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.182026-10-05 14:35just now
To verifyManagement point12 occurrence(s) · CM01, MP02 · last 10-05 11:35 (just now)

What to do: Read mpcontrol.log: it says whether the management point answers over HTTP/HTTPS. Check IIS (CCM pools), the ISAPI extension, BITS, and the management point’s access to the site database. A quick test: https://<MP>/sms_mp/.sms_aut?mplist.

From 2026-10-01 05:22 to 2026-10-05 11:35 · Logs to open (CMTrace): ccmisapi.logmpcontrol.log

MachineLogMessage (latest occurrence)CountLast
MP02ccmisapi.logRequest timed out after 30 seconds for /ccm_system/request.92026-10-05 11:35just now
CM01mpcontrol.logHttp test request failed, status code is 500, 'Internal Server Error'. Retrying in 5 minutes.32026-10-04 00:35just now

2. Chronology

Event feed, newest first

206 lines; consecutive repeats of one message are folded (×N)
Monday 2026-10-05
16:10 → 16:11CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
16:05:12DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
15:41:12CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
15:35:12DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
15:23:12CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
14:35:12CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
14:35:12RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
14:35:12RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
14:19:43CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
13:35:12CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
13:35:12CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
13:10:52RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
12:52:38CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
12:35:12MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
11:35:12MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
11:11:36DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
10:51:18RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
10:35:12CM01wcm.logSMS_WSUS_CONFIGURATION_MANAGERTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.
10:32:46DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
09:06:30RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
08:35:12DP-LYONsmsdpmon.logSMS_DP_MONITORContent validation for package PS100002 timed out after 3600 seconds, will retry.
08:15:40DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
08:07:30CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
08:04:27MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
06:21 → 06:57CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100). ×2
03:26:26RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
02:42:24RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
02:11:32CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
02:01:46RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
Sunday 2026-10-04
23:35:45DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
22:34:05RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
21:48:37CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
20:52:53MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
20:32:17DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
18:35:12CM01smsbkup.logSMS_SITE_BACKUPError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)
18:27:53RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
17:19:08MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
16:41:02CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
16:07:34CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
14:52:38MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
14:35:12CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
13:26:25MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
13:20:51CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
11:57:38DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
10:35:12CM01smsdbmon.logSMS_DATABASE_NOTIFICATION_MONITORSQL error: [40001][1205][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 87) was deadlocked on lock resources with another process.
08:59:18CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
08:51:03DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
08:41:18CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
08:00:18DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
06:46:54DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
05:57:32CM01wcm.logSMS_WSUS_CONFIGURATION_MANAGERTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.
05:42 → 05:43CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101 ×2
03:58:58CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
03:42:03RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
01:55:27CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
00:58:10CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
00:52:20CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
00:35:12CM01mpcontrol.logSMS_MP_CONTROL_MANAGERHttp test request failed, status code is 500, 'Internal Server Error'. Retrying in 5 minutes.
00:16:45DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
00:07:20CM01smsbkup.logSMS_SITE_BACKUPError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)
Saturday 2026-10-03
23:15:09DP-LYONsmsdpmon.logSMS_DP_MONITORContent validation for package PS100002 timed out after 3600 seconds, will retry.
22:06:53CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
21:20:25DP-LYONsmsdpmon.logSMS_DP_MONITORContent validation for package PS100002 timed out after 3600 seconds, will retry.
21:04:46CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
20:55:00CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
20:10:27CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
19:53:00CM01mpcontrol.logSMS_MP_CONTROL_MANAGERHttp test request failed, status code is 500, 'Internal Server Error'. Retrying in 5 minutes.
19:31:58RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
19:30:34CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
19:14:38MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
19:05:52CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
18:37:11CM01wcm.logSMS_WSUS_CONFIGURATION_MANAGERTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.
18:34:01CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
17:55:24CM01smsdbmon.logSMS_DATABASE_NOTIFICATION_MONITORSQL error: [40001][1205][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 87) was deadlocked on lock resources with another process.
17:41:35CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
17:06:28CM01mpcontrol.logSMS_MP_CONTROL_MANAGERHttp test request failed, status code is 500, 'Internal Server Error'. Retrying in 5 minutes.
14:55:18CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
14:35:12DP-NANTESsmsdpmon.logSMS_DP_MONITORConnection to the management point timed out, retrying in 60 seconds.
14:25:33CM01smsbkup.logSMS_SITE_BACKUPError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)
14:01:27DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
14:00:46CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
13:56:51CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
10:46:28CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
10:39:20MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
10:19:05DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
08:56:12CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
08:46:23MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
08:12 → 08:29CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
07:42:29DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
06:54:22DP-NANTESsmsdpmon.logSMS_DP_MONITORConnection to the management point timed out, retrying in 60 seconds.
05:32 → 05:42CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100). ×2
02:52 → 04:39MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation. ×2
01:21:22DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
00:53:54CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
00:01:41DP-LYONsmsdpmon.logSMS_DP_MONITORContent validation for package PS100002 timed out after 3600 seconds, will retry.
Friday 2026-10-02
23:37:49CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
23:18:05CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
23:12:36DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
23:09:08CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
23:04:10RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
20:38:06CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
20:22:09DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
20:14:10CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
19:55:53MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
18:11:22CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
16:12 → 17:57CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101 ×2
15:41:05CM01wcm.logSMS_WSUS_CONFIGURATION_MANAGERTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.
15:10:37MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
13:42:23CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
13:36:28DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
13:09:16MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
11:26:01CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
10:27:36CM01smsdbmon.logSMS_DATABASE_NOTIFICATION_MONITORSQL error: [40001][1205][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 87) was deadlocked on lock resources with another process.
09:44:30MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
08:29:33CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
08:04:37CM01smsbkup.logSMS_SITE_BACKUPError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)
07:46:52MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
07:43:25MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
06:58:35CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
06:49:15CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
06:44:11CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
06:18:34CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
05:46:24CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
04:32:11CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
04:27:00CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
03:34 → 03:42DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk. ×2
03:05:58CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
01:50:54CM01wcm.logSMS_WSUS_CONFIGURATION_MANAGERTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.
01:48:10CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
Thursday 2026-10-01
22:44:29DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
22:29:26CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
21:02 → 21:37RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds. ×2
20:50:26CM01smsdbmon.logSMS_DATABASE_NOTIFICATION_MONITORSQL error: [40001][1205][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 87) was deadlocked on lock resources with another process.
19:06:15MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
15:52 → 17:03CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
13:56:29CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
13:10:54CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
12:58:12RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
12:45:59DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
10:31:12DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
10:02:30CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
09:59:38CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
09:52:26CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
09:52:16CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
09:48:46RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
09:47:00CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
09:38:39CM01smsbkup.logSMS_SITE_BACKUPError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)
09:15:05DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
07:45 → 09:11CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
07:24:45MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
07:19:54DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
06:17:05CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
06:13:05MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
05:58:38CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
05:22:19MP02ccmisapi.logCcmIsapiRequest timed out after 30 seconds for /ccm_system/request.
05:19:56DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
03:35:35RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
03:25:45RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
03:04:22CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
02:52:15CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
02:03:42MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
01:24:52CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
01:15:29DP-LYONsmsdpmon.logSMS_DP_MONITORContent validation for package PS100002 timed out after 3600 seconds, will retry.
Wednesday 2026-09-30
23:13 → 23:40CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
22:52:40MP02MP_Location.logMP_LocationManagerMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.
21:48:49RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
21:03 → 21:44DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk. ×2
20:16:48DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
20:12:01RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
19:59:18CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
18:44:20DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
17:11:58CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
13:59 → 15:23CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
13:46:46CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
12:48:09RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
10:56:45CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
10:32:42CM01ruleengine.logSMS_RULE_ENGINEFailed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101
10:31:22CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
04:03 → 07:18DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk. ×2
03:18:43DP-LYONsmsdpmon.logSMS_DP_MONITORContent validation for package PS100002 timed out after 3600 seconds, will retry.
02:34:47DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
01:39:11RPT01srsrp.logSMS_SRS_REPORTING_POINTRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.
01:31:44DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
00:18:00CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
Tuesday 2026-09-29
23:54:14RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
23:45:08CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
23:06:02RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
22:41:30DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
22:11 → 22:26CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk. ×2
22:05:38CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
22:04:51CM01distmgr.logSMS_DISTRIBUTION_MANAGERFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.
20:01:13CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
19:55:20CM01distmgr.logSMS_DISTRIBUTION_MANAGERDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.
18:33:22DP-LYONsmsdpusage.logSMS_DP_USAGEWarning: content library free space below 5% on drive E:.
17:25:13DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
16:40:17RPT01srsrp.logSMS_SRS_REPORTING_POINTLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.
15:16:01CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
15:15:38DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
15:04:10CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
13:25 → 14:24CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold. ×3
12:37:23CM01distmgr.logSMS_DISTRIBUTION_MANAGERWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).
11:40:20DP-LYONsmsdpprov.logSMS_DP_PROVIDERFailed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.
11:04:21CM01smsbkup.logSMS_SITE_BACKUPError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)
10:37:17CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.
10:04:26CM01wsyncmgr.logSMS_WSUS_SYNC_MANAGERSync failed. Will retry in 60 minutes.
08:19:18CM01colleval.logSMS_COLLECTION_EVALUATORCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.

3. Every error, log by log

MachineLogMessage (latest occurrence)CountFirstLastProbable cause
CM01distmgr.logDistribution Manager: content to the DPsFailed to copy content PS100001 to \\DP-LYON.corp.local\SMS_DP$\. Error = 0x80070070 There is not enough space on the disk.SMS_DISTRIBUTION_MANAGER342026-09-29 22:04just now2026-10-05 16:11just nowNot enough disk space
DP-LYONsmsdpprov.logDistribution point provider (on the DP)Failed to write file E:\SCCMContentLib\FileLib\4A1F\4A1F7C2E. Error 0x80070070 not enough space on the disk.SMS_DP_PROVIDER282026-09-29 11:40just now2026-10-05 16:05just nowNot enough disk space
CM01distmgr.logDistribution Manager: content to the DPsDP-LYON.corp.local: failed to create the content library folder for package PS100001, error 112.SMS_DISTRIBUTION_MANAGER92026-09-29 19:55just now2026-10-05 15:23just nowContent distribution
RPT01srsrp.logReporting Services pointLogin failed for user 'CORP\svc-cm-reporting'. Reason: The password of the account has expired. SQL Server error 18487.SMS_SRS_REPORTING_POINT132026-09-29 16:40just now2026-10-05 14:35just nowAccess to the site SQL database
CM01wsyncmgr.logSoftware update synchronisationSync failed: WebException: The remote server returned an error: (407) Proxy Authentication Required. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServerSMS_WSUS_SYNC_MANAGER72026-09-29 15:16just now2026-10-05 13:35just nowNetwork, name resolution or proxy
MP02MP_Location.logManagement point: client request processingMP LM: Failed to get the certificate for the site signing. Error 0x80092013, the revocation function was unable to check revocation.MP_LocationManager152026-09-30 22:52just now2026-10-05 12:35just nowCertificate, TLS or HTTPS
CM01smsbkup.logSite backupError: Backup destination \\NAS01\CMBackup is not accessible. Access is denied. (0x80070005)SMS_SITE_BACKUP62026-09-29 11:04just now2026-10-04 18:35just nowAccess denied
CM01ruleengine.logAutomatic deployment rules (ADR)Failed to download content for update {3f2a9c1e-8b47-4d2e-9a61-2c5b7e0d4f18}. Error = 0x87D01101SMS_RULE_ENGINE112026-09-30 10:32just now2026-10-04 14:35just nowSoftware update point and WSUS
CM01smsdbmon.logDatabase monitor: SQL triggers to the componentsSQL error: [40001][1205][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 87) was deadlocked on lock resources with another process.SMS_DATABASE_NOTIFICATION_MONITOR42026-10-01 20:50just now2026-10-04 10:35just nowAccess to the site SQL database
CM01distmgr.logDistribution Manager: content to the DPsWill retry package PS100002 to DP-LYON.corp.local in 60 minutes (retry 4 of 100).SMS_DISTRIBUTION_MANAGER222026-09-29 12:37just now2026-10-05 15:41just nowContent distribution
DP-LYONsmsdpusage.logWarning: content library free space below 5% on drive E:.SMS_DP_USAGE122026-09-29 18:33just now2026-10-05 15:35just nowContent distribution
RPT01srsrp.logReporting Services pointRetrying the data source check for report folder ConfigMgr_PS1 in 900 seconds.SMS_SRS_REPORTING_POINT132026-09-30 01:39just now2026-10-05 14:35just nowOther messages
CM01colleval.logCollection evaluationCollection PS100021 took 412 seconds to evaluate, longer than its 300-second warning threshold.SMS_COLLECTION_EVALUATOR182026-09-29 08:19just now2026-10-05 14:35just nowCollection evaluation
CM01wsyncmgr.logSoftware update synchronisationSync failed. Will retry in 60 minutes.SMS_WSUS_SYNC_MANAGER72026-09-29 10:04just now2026-10-05 13:35just nowSoftware update point and WSUS
MP02ccmisapi.logManagement point ISAPI extensionRequest timed out after 30 seconds for /ccm_system/request.CcmIsapi92026-10-01 05:22just now2026-10-05 11:35just nowManagement point
CM01wcm.logSUP configuration and WSUS subscriptionTimed out waiting for the WSUS server CM01.corp.local to answer on port 8530, retrying.SMS_WSUS_CONFIGURATION_MANAGER52026-10-02 01:50just now2026-10-05 10:35just nowSoftware update point and WSUS
DP-LYONsmsdpmon.logDP content validationContent validation for package PS100002 timed out after 3600 seconds, will retry.SMS_DP_MONITOR62026-09-30 03:18just now2026-10-05 08:35just nowContent distribution
CM01mpcontrol.logMP Control Manager: registration and HTTP availabilityHttp test request failed, status code is 500, 'Internal Server Error'. Retrying in 5 minutes.SMS_MP_CONTROL_MANAGER32026-10-03 17:06just now2026-10-04 00:35just nowManagement point
DP-NANTESsmsdpmon.logDP content validationConnection to the management point timed out, retrying in 60 seconds.SMS_DP_MONITOR22026-10-03 06:54just now2026-10-03 14:35just nowContent distribution

4. Status messages by component (last 30 days)

The status message history could not be read (or -HistoryDays 0): components are not dated and their status is the component summarizer’s.
What was read, and how
MachineFiles readErrorsWarningsFolders
CM01.corp.local87155E:\Program Files\Microsoft Configuration Manager\Logs
C:\Windows\CCM\Logs
SQL01.corp.local000
DP-LYON.corp.local32818E:\SMS_DP$\sms\logs
DP-NANTES.corp.local102D:\SMS_DP$\sms\logs
MP02.corp.local2159C:\Windows\CCM\Logs
RPT01.corp.local11313E:\Program Files\SMS_SRSRP\Logs

Read-only: every .log / .lo_ file changed in the window is opened with read/write sharing (never locked) and only its end is read. CMTrace format: the severity is the one the component wrote. SMS format (no severity): a line is classed as error or warning by its keywords (error, failed, 0x8…, warning, retry…), phrases like “Error = 0” being set aside.