Keep CED workstation Wi-Fi available before sign-in and package release 0.6.22

This commit is contained in:
alexrg committed 2026-10-14 15:48:44 -06:00
1 parent 2cca02db35
commit bfa520dec8
9 files changed
+386 -57

No files matched your search

+43 -22
View File
@@ -8,9 +8,10 @@ Configuration is scoped to:
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.
The current Wi-Fi policy targets member workstations with names beginning
`AF-`, `SD-`, or `SI-` in this OU: 47 enabled domain computers on October 14,
2026. Its WMI filter excludes servers and `APPS-` Ethernet workstations.
LCI-77 uses a local profile and remains outside the domain.
## Router configuration
@@ -37,9 +38,12 @@ 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.
**CED - Wi-Fi de salas**. The GPO is enforced on the CED OU, disables user
settings, and filters for AF, SD, and SI member workstations. The native
**Centro de Experiencia Digital** profile remains a read-only Group Policy
profile. An additional **CED - Equipo** all-user profile caches the same network
credentials in Windows' protected machine profile store. This cache is available
before any user signs in and survives sign-out.
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
@@ -47,34 +51,51 @@ 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.
On some Windows clients the native CSE left the Personal key unprotected;
others did not have the CED profile at all. `Repair-SguCedWifi.ps1` uses the
documented Native Wi-Fi API to repair local key protection and prepare the cached
all-user profile. Initial provisioning can read the existing restricted AD WLAN
object using the computer account; no administrator password is stored on the
client. The cached profile subsequently works without an AD connection.
The helper combines native interface state with WLAN service events when Windows
denies querying the current SSID. It does not change location privacy consent.
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.
task triggered by boot, computer policy completion, sign-out, and successful
Wi-Fi connection events. It replaces the previous 15-minute reconnection loop.
WLAN AutoConfig performs normal automatic connections. The repair helper exits
after reconciling the cached profile; there is no client polling interval.
Its code directory permits writes only by SYSTEM and local administrators.
**CED WiFi OU readers refresh** on SGU-DC02 still updates the reader group and
direct policy ACLs every 15 minutes, restricted to AF, SD, and SI computers.
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.
and receive their first policy. Existing disconnected computers likewise need
one initial connection to fetch the correction. The cached Personal profile
does not require user credentials, RADIUS, or a certificate authority. Domain
DNS and management services still depend on their servers being available.
CED profiles use automatic connection with automatic switching disabled.
Other saved all-user Wi-Fi profiles are retained and changed to manual
connection. The sign-in network selector stays available and the policy allows
creating an all-user emergency profile. A manually selected alternate connection
is preserved by routine repair; explicit `-PreferCedNow` requests migration and
attempts to restore the previous profile if CED does not connect. Emergency
connectivity does not itself provide a route to the domain controller.
`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
On CED, the managed Wi-Fi adapter uses 192.168.54.211 and 192.168.54.1 as its
resolvers. On a manually chosen alternate Wi-Fi, the helper restores DHCP DNS
instead of leaving CED's resolver addresses pinned. Internal names continue
to use the NRPT domain rule; public fallback does not provide domain services.
The seven pre-existing SI DNS records originally created for workgroup hosts
also permit their respective domain computer accounts to update their own
records securely after a subnet change. Secure-only zone updates are preserved.
## Windows Admin Center