updates

Author: Jenny-Anne

documentation/modules/proc_adding-source-provider.adoc

@@ -44,10 +44,8 @@ endif::[]
 ifdef::hyperv[]
 = Adding a Microsoft Hyper-V source provider
 
-// SME REVIEW NEEDED: Should we add Prerequisites for SMB share setup and VM export process?
-
 [role="_abstract"]
-You can add a Microsoft Hyper-V source provider by using the {ocp} web console. Hyper-V virtual machines are exported to an SMB share for migration.
+You can add a Microsoft Hyper-V source provider by using the {ocp} web console. The provider uses WinRM to connect to the Hyper-V host and reads VM disk files from a configured SMB share.
 
 [NOTE]
 ====
@@ -286,8 +284,8 @@ If you have Administrator privileges, you can see all projects, otherwise, you c
 .. *Provider details*
 
 * *Provider resource name*: Name of the source provider.
-// SME REVIEW NEEDED: Does the UI safely escape backslashes, or should we recommend only forward-slash format?
-* *URL*: Path to the SMB share containing the Hyper-V exported VMs. For example, `//192.168.122.115/VMShare` or `\\192.168.122.115\VMShare`.
+* *URL*: The Hyper-V host address for WinRM connectivity, for example, `192.168.122.115` or `hyperv-host.example.com`.
+* *SMB share path*: Path to the SMB share that contains the VM disk files, for example, `//192.168.122.115/VMShare`.
 +
 The SMB share must be accessible from both the Hyper-V host and the {ocp-short} cluster.
 

documentation/modules/proc_creating-plan-wizard-hyperv.adoc

@@ -100,9 +100,7 @@ If you choose an existing map, be sure it has the same source provider and the s
 You can create an ownerless storage map, which you and others can use for additional migration plans, in the *Storage maps* section of the UI.
 ====
 +
-// SME REVIEW NEEDED: Does the wizard auto-detect CSV/local paths? Should users verify auto-generated mappings?
-
-** *Source storage*: Select from the list.
+** *Source storage*: Select the SMB share from the list.
 ** *Target storage*: Select from the list.
 +
 If needed, click *Add mapping* to add another mapping.

documentation/modules/proc_migrating-vms-cli-hyperv.adoc

@@ -47,9 +47,8 @@ where:
 `ownerReferences`::
 Optional section for the provider's `name` and `uid`.
 +
-// SME REVIEW NEEDED: Do unquoted backslashes break YAML parsing? Should we recommend only forward-slash format?
 `<smb_server_path>`::
-The SMB share path in `//server/share` or `\\server\share` format (for example, `//192.168.122.115/VMShare`).
+The SMB share path in `//server/share` format, for example, `//192.168.122.115/VMShare`. Use forward slashes to avoid YAML parsing issues with unquoted backslashes.
 +
 `<smb_username>`::
 The username for the SMB share (for example, `Administrator` or `DOMAIN\username`).

documentation/modules/ref_compatibility-guidelines.adoc

@@ -16,8 +16,6 @@ You must install compatible software versions. The table that follows lists the
 |{project-version} |{ocp-y-version} |{ocp-y-version} |6.5 or later |4.4 SP1 or later|16.1 or later|Windows Server 2019 or later
 |===
 
-// SME REVIEW NEEDED: Confirm supported Windows Server versions for Hyper-V - 2016, 2019, 2022, 2025?
-
 [NOTE]
 ====
 Migration from {rhv-full} 4.3

documentation/modules/ref_hyperv-prerequisites.adoc

@@ -6,30 +6,22 @@
 [id="ref_hyperv-prerequisites_{context}"]
 = Microsoft Hyper-V prerequisites
 
-// SME REVIEW NEEDED: This file needs technical details verified and added:
-// - How are VMs exported to the SMB share? (manual/automatic)
-// - Does MTV connect via WinRM or only SMB? Why no WinRM credentials in UI?
-// - What are the specific WinRM configuration commands and settings?
-// - What service account permissions are required? (Local Admin, Hyper-V Admin, or specific privileges)
-// - What are the specific SMB share permissions and configuration details?
-// - Are there additional network requirements or firewall rules beyond ports 5986 and 445?
-// - What are the scope/limitations? (Clustered Hyper-V? CSV? Gen1 vs Gen2 VMs? SCVMM?)
-
 [role="_abstract"]
-To migrate virtual machines from Microsoft Hyper-V to {virt}, you must configure an SMB share for VM exports, enable WinRM on the Hyper-V host, and ensure network connectivity. Review these requirements before creating a provider.
+To migrate virtual machines from Microsoft Hyper-V to {virt}, you must configure WinRM on the Hyper-V host, expose VM disk files on an SMB share, and ensure network connectivity. Review these requirements before creating a provider.
 
 [NOTE]
 ====
 {project-short} supports only cold migration from Microsoft Hyper-V. Warm migration is not available.
 ====
 
-The following prerequisites apply to Microsoft Hyper-V migrations:
+== Prerequisites
 
 * You must use a xref:ref_compatibility-guidelines_{context}[compatible version] of Windows Server with Hyper-V.
 * You must configure Windows Remote Management (WinRM) on the Hyper-V host for HTTPS communication.
 * An SMB share must be available and accessible from both the Hyper-V host and the {ocp-short} cluster.
-* The service account used for authentication must have appropriate permissions to access the SMB share and manage Hyper-V virtual machines.
-* The target namespace must have network connectivity to the SMB share and the Hyper-V WinRM endpoint. NetworkPolicies that block egress connections from the target namespace prevent migration from succeeding.
+* VM disk files (VHD or VHDX) must be exposed on the SMB share before migration. {project-short} does not export VMs automatically.
+* The service account must be a member of the Hyper-V Administrators group and have read access to the SMB share. Local Administrator is the simplest option.
+* The target namespace must have network connectivity to both the SMB share and the Hyper-V WinRM endpoint. NetworkPolicies that block egress connections from the target namespace prevent migration from succeeding.
 * The VM operating system must be certified and supported for use as a link:https://access.redhat.com/articles/973163#ocpvirt[guest operating system with {virt}] _and_ for link:https://access.redhat.com/articles/1351473[conversion to KVM with `virt-v2v`].
 * A default `MigController` instance must be present. This instance is required for the Storage Migration option in the {ocp} web console in certain {ocp-name} versions. For steps to create the default `MigController` instance, see link:https://access.redhat.com/solutions/7136894[Storage Migration Option Missing for Virtual Machines in OpenShift 4.20 Despite Availability in 4.18].
 
@@ -42,16 +34,67 @@ The following network ports must be accessible for Microsoft Hyper-V migrations:
 .Network ports
 |===
 |Port |Protocol |Description
-|5986 |TCP |WinRM HTTPS (default)
+|5986 |TCP |WinRM HTTPS
 |445 |TCP |SMB file sharing
 |===
 
+[id="ref_hyperv-winrm-configuration_{context}"]
+== WinRM configuration
+
+{project-short} connects to the Hyper-V host by using WinRM to discover VM metadata (disks, NICs, and other properties). You must configure WinRM for HTTPS communication on the Hyper-V host before creating the provider.
+
+Quick configuration::
+Run the following command on the Windows host to configure WinRM with HTTPS:
++
+[source,terminal]
+----
+winrm quickconfig -transport:https
+----
+
+Manual configuration::
+Alternatively, configure WinRM manually by running the following PowerShell commands on the Windows host:
++
+[source,terminal]
+----
+Enable-PSRemoting -Force
+
+New-SelfSignedCertificate -DnsName "<hostname>" -CertStoreLocation Cert:\LocalMachine\My
+
+winrm create winrm/config/Listener?Address=*+Transport=HTTPS '@{Hostname="<hostname>";CertificateThumbprint="<thumbprint>"}'
+
+Set-Item WSMan:\localhost\Service\Auth\Basic -Value $true
+
+New-NetFirewallRule -Name "WinRM-HTTPS" -DisplayName "WinRM HTTPS" -Protocol TCP -LocalPort 5986 -Action Allow
+----
++
+Replace `<hostname>` with your Hyper-V host FQDN and `<thumbprint>` with the certificate thumbprint from the `New-SelfSignedCertificate` command output.
+
 [id="ref_hyperv-smb-share_{context}"]
 == SMB share requirements
 
-The SMB share must be configured with the following requirements:
+The SMB share provides access to VM disk files during migration. {project-short} reads VM disk files from the SMB share by using the SMB CSI driver.
+
+* The share must be accessible by using the Linux SMB path format (`//server/share`).
+* The service account credentials must have read access to the SMB share. Write access is not required.
+* VM disk files (VHD or VHDX) must be accessible at the share path before migration begins.
+* The share must have sufficient storage space to hold the VM disk files.
+
+[id="ref_hyperv-credentials_{context}"]
+== Credential requirements
+
+The provider credentials are used for both WinRM connectivity and SMB share access by default. Dedicated SMB credentials can be specified in the CLI if the SMB share uses different authentication.
+
+* The service account must be a member of the Hyper-V Administrators group at minimum.
+* The service account must have read access to the SMB share.
+* Local Administrator is the simplest option as it provides all necessary permissions.
+
+[id="ref_hyperv-scope-limitations_{context}"]
+== Scope and limitations
 
-* The share must be accessible using either Windows UNC path format (`\\server\share`) or Linux SMB path format (`//server/share`).
-* The service account credentials must have read and write access to the SMB share.
-* The share must have sufficient storage space to hold the exported Hyper-V virtual machine files.
-* The Hyper-V host must be able to export virtual machines to the share.
+* Generation 1 and Generation 2 VMs are both supported.
+* VHD and VHDX disk formats are both supported and automatically detected by file extension.
+* Cold migration only. Warm migration is not available.
+* VMs with checkpoints (snapshots) are flagged and may not migrate successfully.
+* System Center Virtual Machine Manager (SCVMM) integration is not supported.
+* Clustered Hyper-V environments are not supported.
+* Cluster Shared Volumes (CSV) are not explicitly handled. Only disks located on the SMB share are usable.