Dr Migrate (DMC) VMware Scan and Upload Procedure

Purpose

Use this procedure to run a Dr Migrate Collector (DMC) scan against one or more VMware vCenters, review the scan results, export the encrypted package, preserve the required key information, and upload the scan to Dr Migrate for analysis. 

Requirements

  • Access to the organization's Dr Migrate instance. 
  • A Windows jump box/VM that can reach the VMware environment and target guest VMs. 
  • DMC package downloaded from Dr Migrate. 
  • DMC license key from the download/license-generation process. 
  • vCenter hostname(s) or address(es) and credentials with sufficient permissions. 
  • Guest OS credentials for Windows systems when guest-level discovery is required. 
  • Adequate local disk space for scan output and logs. Dr Migrate documentation calls for at least 20 GB for a VMware scan; broader guidance recommends sizing temporary storage to the number of VMs being scanned. 
  • An approved secure location to record the DMC-generated ZIP password and encryption/decryption key. 

Procedure

  1. Download and launch DMC
    • Navigate to the Dr. Migrate Customer Portal: Dr. Migrate Customer Portal 
    • Sign in using your@okstate.edu account. 
    • Configure Microsoft Authenticator if prompted. 
    • Select Download DMC. 
    • Accept the End User License Agreement (EULA). 
    • Download the DMC client. 
    • Copy and save the unique license key displayed in the portal. Each user receives their own download and license key. 
      • Example: Download DMC and license key information in the Dr Migrate customer portal.
         
  2. Enter the DMC license key
    • Enter the license key provided/generated for the DMC download. This key authorizes the collector; do not confuse it with the scan-output encryption/decryption information recorded later. 
      • Example: Enter the DMC license key to validate the collector before continuing. 
         
  3. Confirm the output directory
    • Review the output path before scanning. The documented default is C:\temp. Change it if required and make sure the location has sufficient free space. Scan results, logs, and metadata are written here. 
       
  4. Select VMware as the scan target
    • Choose the VMware scan option. Use VMware mode for vCenter-managed VMs when hypervisor metadata and historical performance data are required. Do not scan the same server in both VMware and Physical modes, because duplicate records can be created. 
      • Note: If you are scanning a physical server or Non-VMware hypervisor, select Non-VMware & Physical instead of VMware. See Hyper-V instructions for more help.
      • Example: Select VMware for vCenter-managed VMs, or Non-VMware & Physical for physical Windows servers. 
         
  5. Add the target vCenter(s)
    • Click Add vCenter and enter the vCenter host, username, and password. Add all vCenters that are in scope before continuing. 
       
  6. Validate vCenter access 
    • Click Next and allow DMC to validate the configured vCenters. Review the Status/connection report for permissions and connectivity. Resolve access failures before continuing. A vCenter health-check failure by itself is documented as non-critical, but permissions and connectivity still need to support the scan. 
       
  7. Add guest operating-system credentials 
    • Add Windows credentials as appropriate. Windows credentials must be able to access the guest OS with local administrator rights. Add multiple credential sets if the environment spans different domains/workgroups. 
       
  8. Validate guest credentials
    • Continue to the credential validation stage. DMC tests the supplied credentials against a subset of servers. Review and correct failed credentials before starting the full scan when possible. 
       
  9. Review scan settings
    • Confirm the output path, concurrency, timeouts, and resource thresholds. Unless there is a specific reason to change them, keep the documented defaults and proceed. 
      • Example: Review the output path, concurrent server setting, and scan thresholds before running discovery. 
         
  10. Run the scan
    • Click Run Scan. Monitor the Console Output and progress indicators until the scan completes. The total duration depends on the number of servers, concurrency, connectivity, and credential success. 
      • Operational note from the walkthrough: If DMC is actively using an account for vCenter or guest access, do not change that account's password while the scan is running. A password change can invalidate the credentials being used and cause scan failures. Wait until the scan is complete before resetting the password. 
         
  11. Review the scan summary
    • Review Full, Partial, and Failed results. Partial results generally indicate that hypervisor data was collected but guest-level collection was incomplete. Use the error summary and offline troubleshooting report to identify credential or connectivity problems. 
       
  12. Finalize the scan
    • When the scan is complete and the results have been reviewed, click Finalize Scan to return to the scan-selection/results screen. 
       
  13. Export the completed scan
    • Select the completed scan and choose Export Selected Scans. Give the export a descriptive friendly name. DMC packages the selected scan data into an encrypted ZIP. 
       
  14. RECORD THE ENCRYPTION INFORMATION BEFORE CLOSING DMC
    • Record both values displayed by DMC: the ZIP Password and the Encryption/Decryption Key. Store them securely. Do not rely on being able to recover them later, and do not paste the actual key into this procedure or an unsecured ticket/chat. 
       
  15. Upload the scan to Dr Migrate
    • In Dr Migrate, click Connect, then accept the connection prompt. Next, go to Import > SQL Advanced Analytics Upload. Select or drag in the encrypted DMC ZIP package, enter the required Encryption Key, and choose Upload DMC Output. 
       
  16. Verify ingestion
    • After upload, allow Dr Migrate to decrypt and process the scan data. Confirm that the environment appears in Dr Migrate and that expected VM sizing, software inventory, and utilization data are available before considering the collection complete. 
       
  17. Email the Encryption Key
    • After the upload is complete, send an email to it.cis@okstate.edu with: 
      • Environment name scanned
      • ZIP file name upload
      • Date upload
      • Dr. Migrate Import/Decryption Key

Post-Run Checklist

☐ Scan completed and the summary was reviewed. 
☐ Any critical failed/partial scan issues were documented or remediated. 
☐ Encrypted scan ZIP was exported and retained in the approved location. 
☐ ZIP Password was recorded securely. 
☐ Encryption/Decryption Key was recorded securely. 
☐ Encrypted output was uploaded successfully to Dr Migrate. 
☐ Dr Migrate ingestion/processing was confirmed. 
☐ Any password that was intentionally held unchanged during the scan can now be reset, if required. 

Common Issues/Notes

Issue 

Action 

DMC.exe is blocked 

Right-click DMC.exe > Properties > Unblock > Apply > OK. 

Antivirus blocks DMC 

Dr Migrate documentation recommends excluding/trusting DMC.exe, DMC-CLI.exe, and 7zip.exe or the DMC installation directory, according to local security policy. 

vCenter connection fails 

Check host reachability, HTTPS/443 access, credentials, and permissions. 

Guest scan is partial 

Verify Windows guest credentials, local administrative rights, network reachability, and required guest protocols. 

Password changed during scan 

Expect credential-related failures; restore/replace valid credentials and rerun the affected scope if needed. 

Encryption key unavailable 

Do not guess. Follow the Dr Migrate workflow to generate/re-establish the required key and rerun collection if necessary. 

Duplicate servers appear 

Confirm the same machines were not scanned once in VMware mode and again in Physical mode. 

Key Terminology

Item 

Purpose / Handling 

DMC License Key 

Used to launch/authorize DMC. Obtained during the DMC download/license-generation process. 

ZIP Password 

Generated/displayed during export. Protects the encrypted ZIP package and should be recorded securely. 

Encryption / Decryption Key 

Required to decrypt/import the encrypted DMC results into Dr Migrate. Record it immediately and store it securely. Dr Migrate documentation uses both “Encryption Key” and “Decryption Key” terminology in different workflow screens/pages. 

References

Print Article