Document Windows SSH-based CMC workflow for CDS MCP

- update the CDS MCP CMC install reference to prefer SSH plus PowerShell for Windows guest execution instead of VMware guest operations
- document the Windows install-state check and uninstall-then-reinstall pattern so it matches the Linux CMC preparation flow
- update the VMware MigrateOps guide to treat Windows CMC preparation as an SSH-based workflow using ATVM_WINDOWS_TARGET_* credentials
- update the CDS MCP README and AGENTS guidance so the Windows guest execution default is explicit
This commit is contained in:
2026-03-26 08:47:53 -04:00
parent c0004c1dff
commit b19d6a912e
4 changed files with 19 additions and 1 deletions

View File

@@ -16,11 +16,19 @@ curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -rgc "$CMC_GCSTAGE_RE
## Skidamarink Install (Windows)
Source `/home/aw/code/cds/.env.credentials.local` first so `CMC_GCSTAGE_REGISTRATION_CODE` is present in the PowerShell environment, and use `ATVM_WINDOWS_TARGET_USER` plus `ATVM_WINDOWS_TARGET_PASSWORD` for Windows guest access unless the operator explicitly overrides them.
Prefer SSH to the Windows guest and execute the PowerShell command there instead of relying on VMware guest operations.
```powershell
iex "& { $(irm https://get.cirrusdata.cloud/install-cmc-win) } -rgc $env:CMC_GCSTAGE_REGISTRATION_CODE -gce portal.gcstage.cloud.nonprod.cirrusdata.com:443 -pkg-mode PRE_RELEASE"
```
## Windows Reinstall Pattern
- 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.
- Use the same registration code and endpoint defaults as the Linux flow.
- Prefer direct SSH + PowerShell execution for both the install and uninstall commands.
## Uninstall (Linux)
```bash
curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -uninstall