Drive assignments changed by deployment

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 1

Whole story:

I have a system with all the needed settings and components installed. I need to replicate this system across 6+ machines. The systems are Advantech win 7/32 touch panels - all are identical.

Using snap deploy I made an image accidentally only imaging the primary C:

Deployment yielded a bootmgr missing error.

Checked image an found I missed the G: reserved portion of the hdd - created new image

Deployment yielded a system that starts to boot then errors to windows "failed to start" and windows tries unsuccessfully to fix the MBR

if I exit to prompt I can see all structure is in the wrong drive letters. What was C: pri, G: reserved is now C: reserved D: pri with all windows files. I suspect it's trying to boot from C:. Why did Acronis cause the deployment to reconfigure the drive letter assignments?

Any suggestions would be helpful.

ven 03/07/2015 - 12:28
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 1

Update: I think I found the solution.

From another post mentioning IDE vs AHCI and drive letters being mislabeled - in this post the imaged PC was switched to AHCI prior to imaging. I decided to try switching the target machine BIOS from IDE (factory setting) to AHCI.

In the end :
- imaged machine uses default IDE
- target BIOS switched to AHCI

The target machine booted.

ven 03/07/2015 - 12:52