Split Windows client bootstrap profiles

This commit is contained in:
2026-09-09 11:04:01 -06:00
parent 0b510082d4
commit 74235ec6f8
10 changed files with 168 additions and 25 deletions
+11 -1
View File
@@ -111,7 +111,13 @@ ports remain private even though the VM owns a public IP.
Never disable the built-in Microsoft password Credential Provider. It is the
supported recovery path if a third-party provider fails to load.
For a clean machine, the supported entry points are the release packages:
For a clean machine, choose the release package that matches the workstation:
- `sgu-windows10-legacy-client-bootstrap-VERSION.zip` for Windows 10;
- `sgu-windows11-client-bootstrap-VERSION.zip` for Windows 11, including the
modern Azure P2S/pre-logon flow.
Both use the same direct-lab entry point:
```bat
Start-SguServerBootstrap.cmd 192.168.50.10
@@ -123,6 +129,10 @@ omite y ese adaptador todavía usa una dirección `169.254.x.x`, el enrolador la
solicita de forma interactiva. En equipos con dos NIC selecciona el adaptador
sin puerta de enlace y conserva el `Default Switch` para Internet.
El manifiesto identifica el perfil `Windows10Legacy` o `Windows11Modern` y el
bootstrap valida el build antes de hacer cambios. Las correcciones comunes se
mantienen en ambos; Windows 11 conserva además sus puntos de entrada modernos.
Linux clients are enrolled through their native PAM/SSSD stack instead of the
Windows Credential Provider: