Fix CED ConfigMgr notification connectivity and verify online status

This commit is contained in:
alexrg committed 2026-10-01 10:30:18 -06:00
1 parent 46c0be732a
commit 11d49dc245
3 files changed
+80 -3

No files matched your search

+28
View File
@@ -127,6 +127,7 @@ during source download can fail the installation and require a retry.
.\scripts\Set-SguCedDnsPolicy.ps1
.\scripts\Set-SguCedWacCertificate.ps1
.\scripts\Set-SguCedConfigMgrCollection.ps1
.\scripts\Set-SguCedNotificationFirewall.ps1
$credential = Get-Credential
.\scripts\Invoke-SguCedPreparation.ps1 -InventoryPath <private inventory JSON> -Credential $credential -MigrateWifi
@@ -168,9 +169,34 @@ keys, private certificates, or original clear-key WLAN exports are committed.
`Test-SguCedManagedNodes.ps1` checks live SSID, the successful profile event,
reachable WinRM, CcmExec, assigned site, and WAC root trust. Also verify the WAC
OS endpoint, ConfigMgr server-side client registration, and collection membership.
The validation script also reads `CNIsOnline` from the local site provider and
returns it as `NotificationOnline`. A null value means provider data is unavailable;
it must not be interpreted as an offline client.
An installation wizard success screen or a scheduled installation request does
not establish that installation completed.
### Configuration Manager gray X icons
The green check and gray X indicate the client notification connection. They are
separate from `Client=Yes`, recent client activity, and client health. On October 1,
AF-02 through AF-06 and AF-10 remained reachable with CcmExec running, but their
notification logs repeatedly reported `Failed to find a access point ... 8000000a`.
Restarting CcmExec restored management-point discovery. The server was listening
on TCP 10123, but connections timed out until the missing inbound firewall rule
was added. `Set-SguCedNotificationFirewall.ps1` reproduces that rule for only
SGU-DC02's CED address, the Domain firewall profile, the notification host process,
and source subnet `192.168.54.0/24`.
After correcting the port, restart CcmExec only on affected clients when needed,
then check their notification keep-alive logs and server-side `CNIsOnline`.
Allow time for status reports and refresh the console. Do not reinstall the
client solely because its notification icon is gray.
The follow-up validation reported all 39 CED devices reachable and
`NotificationOnline=True`, including all six affected AF clients. The server log
confirmed 39 online notification sessions (6 TCP and 33 HTTP). No operating-system
restart or client reinstallation was needed.
To recover the previous Wi-Fi, first provision an existing known-good profile
and reconnection task on SGU-DC02 and affected PCs. Then restore Aula Flexible on
VLAN 53, or re-enable the preserved Sala de Desarrollo network, as appropriate.
@@ -190,3 +216,5 @@ is not changed by this network repair.
- [Computer startup script protocol](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gpscr/ff1fd13e-1e18-4160-9b50-0263e108e5e1)
- [Configuration Manager client source selection](https://learn.microsoft.com/en-us/intune/configmgr/core/servers/deploy/configure/boundary-groups-distribution-points)
- [Domain DNS policy cmdlet](https://learn.microsoft.com/en-us/powershell/module/dnsclient/add-dnsclientnrptrule)
- [Configuration Manager client monitoring](https://learn.microsoft.com/en-us/intune/configmgr/core/clients/manage/monitor-clients)
- [Configuration Manager connection ports](https://learn.microsoft.com/en-us/intune/configmgr/core/plan-design/hierarchy/ports)