# Centro de Experiencia Digital network The managed Wi-Fi network is **Centro de Experiencia Digital**, on the ASUS GT-AX11000 Pro. It replaces Aula Flexible and Sala de Desarrollo for the CED PCs. Configuration is scoped to: ```text OU=Centro de Experiencia Digital,OU=Laboratorio,DC=lci,DC=lasalle,DC=mx ``` The rollout targets AF-02 through AF-06, AF-08 through AF-11, and SD-01 through SD-30: 39 domain computers. LCI-77 uses a local Wi-Fi profile and remains outside the domain. Its Ethernet connection is retained. ## Router configuration | Network | Result | | --- | --- | | Centro de Experiencia Digital | VLAN 53, 192.168.54.0/24, gateway 192.168.54.1, WPA2/WPA3-Personal, AES, 2.4/5 GHz | | Sala de Desarrollo | Disabled, configuration retained for recovery | | Sala Inmersiva | Existing SSID, key, VLAN 54 and 192.168.55.0/24 retained | | Invitados CED | Retained | | Esports CED | Retained with its pre-existing enable/disable state | | NewMatrix | Existing main network retained | The previous Aula Flexible shared key is retained privately. The old 20 Mbps download / 5 Mbps upload cap is removed from the CED network. DHCP provides the domain DNS server at 192.168.54.211. AP isolation is off for management between the CED PCs. Existing separation of the other guest networks is retained. Router configuration changes restart shared radios and can interrupt all Wi-Fi connections briefly, including unchanged SSIDs. SGU-DC02 itself is connected by Wi-Fi, despite LCI-77 having Ethernet. Prepare a server reconnection task before applying router changes. Radio/DFS readiness can take several minutes; do not repeat Apply while waiting for recovery. ## Group Policy and future computers `Set-SguCedWifiPolicy.ps1` publishes a native computer WLAN policy in **CED - Wi-Fi de salas**. The profile remains a read-only Group Policy profile; it is not a manually imported all-user profile. The GPO is linked only to the CED OU and disables user settings. The Personal shared key is stored in the native AD WLAN policy object. Its ACL permits the CED computer reader group and direct CED computer SIDs, plus the administrative/system identities needed to maintain it. The key is not stored in SYSVOL scripts or in this repository. Exported profiles containing the key must remain in an administrator-only private directory. On the tested Windows clients, the native CSE left the Personal key unprotected and connection attempts failed. `Connect-SguCedWifi.ps1` uses the documented Native Wi-Fi `WlanSetProfile` API to protect that key on the client while keeping the Group Policy profile flag. It then connects and requires a successful WLAN event for both the expected profile name and SSID. No location privacy setting is changed. Successful live connections are left running. The computer startup policy installs **CED WiFi policy connection**, a SYSTEM task that runs at startup and every 15 minutes. The task requires the native Group Policy profile. Its code directory permits writes only by SYSTEM and local administrators. **CED WiFi OU readers refresh** on SGU-DC02 updates the reader group and direct policy ACLs every 15 minutes, removing computers that leave the OU. No domain administrator password is stored in these tasks. New domain computers in the OU receive policy automatically after reader refresh and normal Group Policy processing. They still need an initial path to a domain controller, such as Ethernet or an existing Wi-Fi profile, to join the domain and receive their first policy. A cached Personal profile can reconnect without RADIUS or a certificate authority. Domain DNS and management services still depend on their servers being available. `Set-SguCedDnsPolicy.ps1` creates **CED - DNS de dominio**, linked only to the same OU. Its NRPT rule directs the internal domain namespace to 192.168.54.211. This avoids public Ethernet DNS competing with Wi-Fi domain DNS on multihomed PCs. Public namespaces retain their normal resolution settings. The managed Wi-Fi adapter also has 192.168.54.1 as a secondary resolver for public names if the domain DNS server is unavailable. Internal names continue to use the NRPT domain rule; public fallback does not provide domain services. ## Windows Admin Center `Set-SguCedWacCertificate.ps1` provisions a non-exportable RSA 3072-bit server certificate for `sgu-dc02.lci.lasalle.mx` and `sgu-dc02`, binds it to the WAC frontend, and distributes its public trust through **CED - Confianza de administracion** in the CED OU. It backs up the previous WAC settings before changing the binding. It does not install a certificate authority. LCI-77 trusts the public certificate in the current user's Root store. This does not join it to the domain. Keep the WAC private key on SGU-DC02. Renew the certificate and update the trust policy before expiry. `Sync-SguWacDomainConnections.ps1 -ComputerOuDn ` limits inventory additions to this OU. Verification queries actual OS instances through WAC; having a saved connection alone is not proof of management connectivity. Existing unrelated WAC inventory entries are not deleted. Authentication and certificate validation remain enabled. ## Configuration Manager The existing collection **LCI00014** is named **Centro de Experiencia Digital**. Its query uses the exact CED canonical OU. Periodic and incremental evaluation are enabled, preserving the collection ID and existing client-setting deployments. AD system discovery remains enabled, including its existing incremental polling. `Set-SguCedConfigMgrCollection.ps1` reproduces this configuration. `Set-SguCedClientSource.ps1` prepares the complete Microsoft-signed client media in `C:\ProgramData\LCI-Admin\ClientSource`, shared as `CEDClient$` with encrypted SMB. CED computers have read access, including direct computer permissions for machines whose existing Kerberos tickets predate reader-group membership. The administrative `SMS_LCI` share is not opened to client computers. Use `/source` alone for this source, plus the installation properties `SMSSITECODE=LCI SMSMP=sgu-dc02.lci.lasalle.mx`. Adding `/mp` gives management-point and distribution-point discovery priority and previously left these installs waiting. The native startup policy also installs a SYSTEM enrollment task for future CED computers. It validates current OU membership and the Microsoft signature, skips an existing client or running setup, and retries every 30 minutes. For an existing computer migration, prepare DNS/policy and migrate Wi-Fi first. Verify the new connection before starting the client installer. Changing Wi-Fi during source download can fail the installation and require a retry. ```powershell # Run on SGU-DC02 with authorized administrative credentials supplied in memory. .\scripts\Set-SguCedClientSource.ps1 .\scripts\Set-SguCedWifiPolicy.ps1 -ProfilePath .\scripts\Sync-SguCedWifiReaders.ps1 -InstallRefreshTask .\scripts\Set-SguCedDnsPolicy.ps1 .\scripts\Set-SguCedWacCertificate.ps1 .\scripts\Set-SguCedConfigMgrCollection.ps1 .\scripts\Set-SguCedNotificationFirewall.ps1 $credential = Get-Credential .\scripts\Invoke-SguCedPreparation.ps1 -InventoryPath -Credential $credential -MigrateWifi .\scripts\Test-SguCedManagedNodes.ps1 -Credential $credential .\scripts\Invoke-SguCedPreparation.ps1 -InventoryPath -Credential $credential -InstallClient ``` Inventory JSON is an array of `Name`, `IP`, and `WinRM` properties. Preparation validates the AD scope and actual remote hostname, domain, and secure channel before changing anything. It prefers current DNS over a stale DHCP inventory address. Existing DNS settings are backed up on each client. ## Rollout validation — October 1, 2026 After the final router radio restart, the live client validation returned: | Check | Result | | --- | --- | | CED computers in scope | 39 | | Reachable over authenticated WinRM | 39 | | Live CED SSID and matching successful policy profile event | 39 | | CcmExec running and site LCI assigned | 39 | | WAC public certificate trusted in the machine Root store | 39 | | WAC returned actual OS instances over validated HTTPS | 39 | ConfigMgr also reported 39 CED resources with `Client=1` and the expected OU attribute. SD-06 was initially unavailable; it was prepared, migrated, installed, and validated after being made available. The client installer logs on SD-06, SD-09, and the SD-27 pilot returned exit code 0. LCI-77 successfully reconnected with its local profile while remaining outside the domain. The router UI showed the new SSID with WPA2/WPA3-Personal and Sala de Desarrollo disabled. Private per-machine validation JSON and the router screenshot are stored outside Git in the administrator's private CED network directory. No passwords, shared keys, private certificates, or original clear-key WLAN exports are committed. ## Verification and recovery `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, and the notification host process. It initially allowed source subnet `192.168.54.0/24`; it now also allows `192.168.55.0/24` for the requested Sala Inmersiva management access described below. 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. ### CED and Sala Inmersiva inter-network access At the administrator's subsequent request on October 1, the router's Guest Network Pro **Access Intranet** settings were changed to allow the CED (VLAN 53, `192.168.54.0/24`) and Sala Inmersiva (VLAN 54, `192.168.55.0/24`) networks to communicate. From the CED profile, only Sala Inmersiva was newly selected. After applying and reloading the router, the Sala Inmersiva profile also showed CED selected: the setting is reciprocal. Its pre-existing Main Network selection was preserved. Esports CED and Invitados CED were not selected for this new connection. No SSID, password, subnet, or Wi-Fi GPO scope was changed. Applying the router configuration briefly restarted wireless connections; LCI-77 reconnected using its existing CED profile. Authenticated WinRM from SGU-DC02 reached SD-17 (`192.168.55.19`) and SD-21 (`192.168.55.20`), with both reporting live SSID **Sala Inmersiva**. Both clients could reach the management point's HTTP endpoint and, after extending the scoped notification firewall rule, TCP 10123. A separate client-to-client test confirmed TCP 2701 from AF-02 on CED to SD-17 on Sala Inmersiva and in the reverse direction. AF-02 could also reach SD-17's WinRM port. These are service reachability checks, not proof that every Windows service accepts connections from every peer. Use DNS names or IP addresses in management tools across these subnets. Router routing alone does not make every computer appear automatically in Windows Explorer's Network view. Windows firewall rules, authentication, and enabled management services still apply. New Windows clients still need discovery and client enrollment; Wi-Fi profile deployment remains limited to the CED OU. 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. Disable the CED GPO links and remove the CED maintenance/enrollment tasks when rolling back the managed configuration. Use each client's `CED-dns-before.json` to restore DNS. For WAC, restore the saved frontend settings and certificate binding before removing the public trust policy. Do not remove unrelated GPOs, profiles, certificates, or guest networks. The existing Configuration Manager 2103 / Windows Server 2025 support limitation is not changed by this network repair. ## References - [Microsoft native WLAN Group Policy protocol](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gpwl/481e4e64-5e95-4ada-aae8-ec93ed69559a) - [Native Wi-Fi profile storage and key protection](https://learn.microsoft.com/en-us/windows/win32/api/wlanapi/nf-wlanapi-wlansetprofile) - [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)