Migrating 100+ PCs with ProfWiz: Best Practices

Migrating 100+ PCs with ProfWiz: Best Practices

📅 June 16, 2025 ✍️ ProfWiz Team 📂 ProfWiz Guide

Planning a Large-Scale ProfWiz Migration

Migrating a single workstation with ProfWiz is straightforward. Migrating 100, 500, or 5,000 workstations requires a completely different approach — one built on automation, staging, and centralized monitoring. This guide shares the best practices that enterprise IT teams use to run ProfWiz at scale without business disruption.

Phase 1 — Inventory and Mapping

Migrating 100+ PCs with ProfWiz: Best Practices illustration

Before touching a single workstation, build a complete inventory:

  • Export all computer accounts from Active Directory using PowerShell: Get-ADComputer -Filter * | Select-Object Name,OperatingSystem
  • Export all user accounts and their current domain associations
  • Create a mapping spreadsheet: source account → target account, machine name, migration wave
  • Identify machines with non-standard profile locations (redirected folders, roaming profiles)

A clean mapping file is the foundation of every successful bulk migration. Errors here propagate to hundreds of machines.

Phase 2 — Pilot Group (10 Machines)

Never roll out to all machines at once. Select a pilot group of 10 workstations representing different hardware types, OS versions, and user roles. Run ProfWiz on these machines first and collect feedback from the users for one full week before proceeding.

During the pilot, pay attention to:

  • Applications that break after migration (particularly those using Windows credential manager)
  • Mapped drive reconnection behavior
  • Outlook profile re-authentication
  • VPN client behavior

Phase 3 — Scripted Deployment

ProfWiz's command-line interface makes it ideal for scripted bulk deployment. A typical deployment script:

@echo off
SET DOMAIN=NEWDOMAIN
SET LOGPATH=\fileserver\migration-logs\%COMPUTERNAME%.log

:: Read user mapping from CSV
FOR /F "tokens=1,2 delims=," %%A IN (\fileserver\migration\mapping.csv) DO (
    IF "%%A"=="%USERNAME%" (
        ProfWiz.exe /domain:%DOMAIN% /user:%%B /Silent /Log:%LOGPATH%
    )
)

Deploy this script via Group Policy as a startup script or via SCCM as a task sequence step. The script reads the mapping CSV to match each machine's current user to their target domain account.

Phase 4 — Wave-Based Rollout

Divide your workstation fleet into waves of 50–100 machines. Deploy each wave on a Monday morning so the full week is available for issue resolution before the weekend. Wave structure:

  • Wave 1: IT department machines (self-supporting users)
  • Wave 2: Back-office staff (low business criticality)
  • Wave 3: Operations and customer-facing staff
  • Wave 4: Executives and specialized workstations

Centralized Log Collection

Direct all ProfWiz logs to a central network share using the /Log parameter. Use a PowerShell script to parse logs and generate a migration status dashboard showing:

  • Total machines processed
  • Success count
  • Failure count with error codes
  • Pending machines

Review the dashboard daily during the migration period.

Handling Exceptions

Some machines will not migrate cleanly on the first attempt. Common exceptions:

  • Machines offline during the migration window — requeue them for the next wave
  • Corrupt profile registry entries — repair with regedit before re-running ProfWiz
  • Non-standard profile paths — specify the path explicitly using ProfWiz's /ProfileDir parameter
  • Encrypted files — BitLocker-encrypted drives must be unlocked before migration

Post-Migration Validation

After each wave, run a validation script that:

  • Confirms the domain profile is active (net user %username% /domain)
  • Verifies the profile folder is accessible
  • Checks that key applications launch without prompting for credentials

Communication Plan

Users should be told what to expect. Send a brief email before their machine's migration wave explaining that their PC will restart and they should log in with domain credentials. Include a contact for issues. Users who understand what is happening are far less likely to panic or log tickets unnecessarily.

Conclusion

Migrating 100 or more PCs with ProfWiz is entirely achievable with the right preparation. Invest time in your mapping spreadsheet, validate with a pilot group, automate with scripting, and deploy in controlled waves. With this approach, even an enterprise-wide migration can complete smoothly with minimal helpdesk impact.

Related ProfWiz Guides