357 lines
21 KiB
Markdown
357 lines
21 KiB
Markdown
# 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 <CED OU>` 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 <private clear-key WLAN XML>
|
|
.\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 <private inventory JSON> -Credential $credential -MigrateWifi
|
|
.\scripts\Test-SguCedManagedNodes.ps1 -Credential $credential
|
|
.\scripts\Invoke-SguCedPreparation.ps1 -InventoryPath <private inventory JSON> -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.
|
|
|
|
#### Workgroup RDP validation: SI-04
|
|
|
|
The initial AF/SD management tests did not establish short-name resolution for
|
|
workgroup computers in Sala Inmersiva. SI-04 was subsequently checked before
|
|
domain enrollment. It had no AD computer object or domain DNS record, and the
|
|
router answered its short name only when explicitly queried at `192.168.55.1`.
|
|
On October 1 its DHCP address was `192.168.55.138`.
|
|
|
|
From LCI-77 with live SSID **Centro de Experiencia Digital**, TCP 3389 to that
|
|
address succeeded. An actual RDP connection negotiation returned a 19-byte reply
|
|
with negotiation response type 2 and selected protocol 2 (HYBRID/NLA). This
|
|
validates the RDP endpoint across the VLANs, not an authenticated desktop session.
|
|
This initial test did not enroll SI-04 or create a domain DNS record. Before
|
|
enrollment, an authenticated RDP login still requires an authorized local SI-04
|
|
account.
|
|
|
|
#### Workgroup names available from CED
|
|
|
|
The subsequent DNS repair publishes A records in the existing secure AD DNS
|
|
zone `lci.lasalle.mx`, without creating AD computer objects. The router's Sala
|
|
Inmersiva client list identified six additional Windows workgroup names:
|
|
`SI-02`, `SI-04`, `SI-05`, `SI-06`, `SI-07`, and `SI-08`. Each address was verified
|
|
with a direct DNS query to `192.168.55.1` before publication. SI-04 currently
|
|
resolves to `192.168.55.138`.
|
|
|
|
SI-03 was subsequently added after a direct router DNS query returned
|
|
`192.168.55.120`. Its A record and manifest entry bring the approved list to
|
|
seven computers, SI-02 through SI-08. The Windows application resolver on LCI-77
|
|
successfully resolved **SI-03** while connected to CED. SI-01 did not have a router
|
|
DNS answer during this follow-up and was not assigned a guessed address.
|
|
|
|
On SGU-DC02, task **LCI - Sala Inmersiva workgroup DNS** runs
|
|
`scripts/Sync-SguSalaWorkgroupDns.ps1` as SYSTEM every five minutes, using the
|
|
protected folder `C:\ProgramData\LCI-Admin\Sala-DNS`. No credentials are stored.
|
|
Its `manifest.json` contains the approved names and their last published
|
|
addresses. Only router answers in `192.168.55.0/24` are accepted. The sync refuses
|
|
to overwrite records changed by another administrator and stops managing a name
|
|
once it has an AD computer object. New names require explicit approval and an
|
|
entry in this manifest; arbitrary guest/IoT clients are not imported.
|
|
|
|
Records have a five-minute TTL. A failed router query preserves the last record
|
|
and reports an error in `last-result.json` and the task result; the TTL does not
|
|
expire the server record. Review these errors if an address becomes stale.
|
|
The first two SYSTEM runs completed successfully with all six records current.
|
|
The zone continues to allow secure dynamic updates only.
|
|
|
|
Domain clients use their domain suffix and existing **CED - DNS de dominio** GPO.
|
|
The workgroup administrator PC LCI-77 additionally needed the Wi-Fi connection
|
|
suffix `lci.lasalle.mx` and an NRPT rule for that namespace pointing to
|
|
`192.168.54.211`; `scripts/Set-SguCedAdminDns.ps1` reproduces this local setup.
|
|
The prior suffix is saved in `LCI77-Sala-DNS-before.json` in the protected private
|
|
folder. The rule applies only to this DNS namespace; existing Tailscale rules
|
|
remain intact. The adapter suffix persists across Wi-Fi profile changes.
|
|
|
|
Validation used Windows' application resolver (`System.Net.Dns.GetHostAddresses`),
|
|
not just an explicit DNS-server query. All six short names resolved on LCI-77
|
|
while its live SSID was **Centro de Experiencia Digital**. AF-02, at
|
|
`192.168.54.130`, also resolved SI-04 correctly. A TCP connection opened using
|
|
the name **SI-04** from LCI-77 reached port 3389 and received a successful RDP
|
|
HYBRID/NLA negotiation response. This verifies name resolution and the RDP
|
|
endpoint across networks; it does not assert an authenticated desktop session.
|
|
|
|
To undo this DNS repair, disable the sync task first. Remove only manifest-owned
|
|
A records that still match their last published IP and have no AD computer object.
|
|
On LCI-77, restore the saved Wi-Fi suffix and remove only the NRPT rule with the
|
|
comment `CED domain DNS for local administrator Wi-Fi`. Keep the domain GPO and
|
|
unrelated DNS rules. These DNS changes require no router apply or radio restart.
|
|
|
|
#### Sala Inmersiva to SGU-DC02 name resolution
|
|
|
|
The reverse direction needed an additional change: Sala's original router DNS
|
|
at `192.168.55.1` returned NXDOMAIN for both `SGU-DC02` and its FQDN. Guest Network
|
|
Pro now assigns **192.168.54.211** as Sala Inmersiva's DHCP DNS server. This change
|
|
keeps its SSID, authentication, VLAN 54, and gateway `192.168.55.1`. Applying it
|
|
briefly restarted the radios; a temporary reconnection task protected SGU-DC02
|
|
and was removed after verifying server access. CED, Invitados CED, and Esports CED
|
|
were visible again after a fresh wireless scan. LCI-77 returned to CED after testing.
|
|
|
|
Workgroup clients with no domain suffix also need an answer to the bare server
|
|
name. `scripts/Set-SguCedShortNameDns.ps1` creates the narrowly scoped AD-integrated
|
|
DNS zone `sgu-dc02`, with an apex A record for `192.168.54.211` and dynamic updates
|
|
disabled. The regular `sgu-dc02.lci.lasalle.mx` record is unchanged. No root zone,
|
|
domain membership, hosts-file entry, or WINS service is created.
|
|
|
|
To preserve bare SI names for clients receiving the new DNS setting,
|
|
`scripts/Sync-SguSalaShortNames.ps1` similarly maintains the seven approved SI
|
|
labels. The existing five-minute Sala DNS task invokes this helper after updating
|
|
the regular domain records. The helper mirrors each FQDN A record into its
|
|
corresponding bare-name zone and refuses to overwrite records that differ from
|
|
its protected `short-names-owned.json`. It logs to `short-names-result.json`.
|
|
All eight bare-name answers were verified, and the SYSTEM task returned exit 0.
|
|
GlobalNames support remains disabled as before this change.
|
|
|
|
LCI-77 temporarily connected to live SSID **Sala Inmersiva**, received
|
|
`192.168.55.201` with DNS `192.168.54.211`, and successfully queried the bare
|
|
`SGU-DC02`, its FQDN, SI-03's FQDN, and a public Internet name. This verifies the
|
|
new DHCP setting and DNS access across the VLANs. SI-03 itself was not remotely
|
|
reconfigured: its WinRM ports were unavailable, so its user was asked to reconnect
|
|
Wi-Fi and verify the short name. Existing clients may keep their previous DHCP
|
|
DNS settings until reconnection or lease renewal.
|
|
|
|
Internal DNS now depends on SGU-DC02 in Sala as it already does in CED. Personal
|
|
Wi-Fi authentication still does not require RADIUS or domain membership. To roll
|
|
back this follow-up, restore Sala's DNS selection to **Default**, disable the
|
|
short-name helper invocation, and remove only the eight owned bare-name zones
|
|
after comparing their A records with `short-names-owned.json`. Keep the existing
|
|
secure domain zone and the original approved-name synchronization task.
|
|
|
|
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)
|