Require CDC cleanup before Windows CMC reinstall in CDS MCP workflow
- 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:
@@ -68,8 +68,10 @@ This file is for workflow guidance only. Do not add specific run examples here.
|
||||
## CMC Preparation Rule
|
||||
- For Linux sources, use the Linux SSH credential path and the Linux install/uninstall reference.
|
||||
- For Windows sources, use SSH to the guest with `ATVM_WINDOWS_TARGET_USER` and `ATVM_WINDOWS_TARGET_PASSWORD`.
|
||||
- For both Linux and Windows, clean stale CDC project state for that machine before reinstalling CMC unless the operator explicitly wants to reuse the existing registration.
|
||||
- For Windows sources, check whether CMC is already installed before install.
|
||||
- If Windows CMC is already present, uninstall first and then reinstall using the Windows PowerShell installer command.
|
||||
- After reinstall on Windows, confirm the host reconnects in the CDC project as expected before creating local or remote migration sessions.
|
||||
- Do not treat VMware guest operations as the default Windows execution path.
|
||||
|
||||
## Post-Migration Validation and Cleanup Pattern
|
||||
|
||||
Reference in New Issue
Block a user