fix(proxmox): template VM 310 sysprep-uit, VM 300 nu mai e de clonat
VM 300 `Win11-Template` nu a fost sysprep-uit: poarta numele ROACENTRAL si SID-ul de masina al VM 201 (S-1-5-21-1850128657-3079265004-705332634). Clonele lui mostenesc acea identitate, iar NTLM intre doua masini cu acelasi SID de masina esueaza — de aici imposibilitatea accesarii share-urilor SMB intre VM 303 si VM 201, in ambele sensuri. VM 300 nu poate fi reparat in loc: e template read-only, iar VM 303 e linked clone din el. Solutia: clona completa 300 -> 310, sysprep acolo, conversie in template. Verificat pe o clona de proba: nume si SID noi la fiecare pornire. - clone-vm300.sh: SOURCE_VMID 300 -> 310 - README-uri: VM 310 marcat ca template de clonare, VM 300 ca "nu clona" - vm302-oracle-test: corectat exemplul care clona in VM 303 (deja ocupat) - docs/handoff-smb-vm303-roacentral.md: probele, capcanele de sysprep, stare Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MoFGxftQw92PX4Sdkn94pv
This commit is contained in:
@@ -439,7 +439,8 @@ ssh root@10.0.20.201 "qm snapshot 302 pre-test --description 'Before ROA test'"
|
||||
|------|------|----|--------------|
|
||||
| **109** | **standby-dr** | **Windows Server** | **`vm109-windows-dr/`** |
|
||||
| **201** | **roacentral** | **Windows 11** | **`vm201-windows/`** |
|
||||
| 300 | Win11-Template | Windows 11 | `cluster/README.md` |
|
||||
| **310** | **Win11-Template-Sysprep** | **Windows 11 (template de clonare)** | **`cluster/README.md`** |
|
||||
| 300 | Win11-Template | Windows 11 | ⛔ nesysprep-uit, nu clona — `docs/handoff-smb-vm303-roacentral.md` |
|
||||
| **302** | **oracle-test-302** | **Windows 11 + Oracle 21c (test ROA)** | **`vm302-oracle-test/`** |
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user