anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Require CDC cleanup before Windows CMC reinstall in CDS MCP workflow

Browse Source 
- update the Windows CMC install reference to require CDC project cleanup before reinstall when stale host state may exist
- update the VMware MigrateOps guide so the cleanup-first CMC preparation rule applies to both Linux and Windows sources
- document that Windows reinstall must be followed by a fresh CDC reconnect check before creating migration sessions
- update CDS MCP AGENTS guidance so Windows sources do not skip the standard CDC cleanup plus reinstall sequence
This commit is contained in:
anthony.wen
2026-03-26 10:14:11 -04:00
parent b19d6a912e
commit 68cd428733
3 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cdsmcp/docs/cmc-install-reference.md
View File

@@ -23,9 +23,11 @@ iex "& { $(irm https://get.cirrusdata.cloud/install-cmc-win) } -rgc $env:CMC_GCS
```
## Windows Reinstall Pattern
- Before install or reinstall, clean stale CDC project state for that machine when applicable instead of blindly reusing an existing registration.
- Before install or reinstall, connect over SSH with `ATVM_WINDOWS_TARGET_USER` and `ATVM_WINDOWS_TARGET_PASSWORD`.
- Check whether CMC is already installed before deciding on the next action.
- If CMC is already installed, uninstall first, then run the Windows install command again.
- After cleanup/reinstall, verify the host shows up as a fresh connected system in the CDC project before creating migrations.
- Use the same registration code and endpoint defaults as the Linux flow.
- Prefer direct SSH + PowerShell execution for both the install and uninstall commands.