If the failed Windows server still has intact drives, they can be attached to a new Windows server. Windows automatically recognises NTFS partitions — data can then be transferred directly.
Important — follow this order: Install the operating system on the new server completely before letting us know the old drives can be connected. If the drives are attached before the OS installation, the installer may detect the wrong disks and irreversibly overwrite the old data.
| Phase | What happens |
|---|---|
| 1. Detect the drive | Windows detects the new drive automatically or via Disk Management |
| 2. Assign drive letters | Assign drive letters to the old drive's partitions |
| 3. Fix permissions | Take ownership of locked system folders from the old installation |
| 4. Transfer data | Copy files, IIS config, and databases to the new server |
Open Disk Management via Start → Run → diskmgmt.msc. The new drive appears in the lower list. If it shows as Offline, right-click it and select Online.
Replace 1 with the actual disk number from the output.
Right-click a partition on the new drive and select Change Drive Letter and Paths → Add. Assign a free letter — e.g. D: or E:.
takeown /r works recursively and may take a few minutes on large directories.
Attach the copied database files in SQL Server Management Studio (SSMS): Databases → Right-click → Attach and select the .mdf file. Or via T-SQL:
Only copy SQL Server database files directly if both servers run the same or a newer SQL Server version. For older target versions use a backup/restore approach instead.
iisreset /startAssign the imported certificate in IIS: IIS → Website → Bindings → HTTPS → Select certificate.