Skip to main content

Pls..... guide and help me!!!

Thread needs solution

Hi Everyone!!

I work in a company where we sell new laptops of every brand and models. We prepare 1 new laptop, install windows, drivers and applications and then create a disk image of that laptop. Later we use Acronis Rescue Media (Linux based) to install windows (including drivers and applications) in every new laptop of same model and specification from Acronis disk image. For eg. we have Acronis disk image of Dell 3543 model with 4 Gb RAM and 500 Gb hard drive and we use that image to install windows in all 3543 model with 500 Gb hard drive. But some customers want to customize their new laptops while buying. Some customers want 8 Gb RAM instead of 4 and some people want 1 TB of Hard drive instead of 500 Gb.

We have been using Acronis True Image (ATI) 2013 build 5587 to restore the image in all new laptops. Restoring image to a new laptop with exact same capacity of hard drive has never been a problem. Restoring image to a new laptop with different capacity of hard drive, e.g. from 500 to 1 Tb has also never been a problem with ATI 2013 which I used to use as it automatically increases the size of each partitions in new hard drive. For eg. Acronis image of 500 Gb hard drive with 4 partitions (C: 100 Gb and 3 other equal sized partitions) to 1 Tb (C: 200 Gb and 3 other equal sized partitions).

But my company provided me Acronis True Image 2016 earlier and now Acronis True Image 2017. When I use ATI 2016 or 2017, it doesn't create the partition in the new 1 Tb hard drive like ATI 2013 used to create. Instead it creates partition like this:  C: drive and 3 partitions same as 500 Gb hard drive and remaining 465 Gb as logical without assigning a drive letter.

Why ATI 2016 and ATI 2017 are not creating the partitions in 1 Tb hard drive from disk image of 500 Gb hard drive which ATI 2013 used to create??  Please guide and help me!!!

0 Users found this helpful

Singh_np, welcome to these user forums.

There have been a number of changes introduced since ATIH 2013 which have been prompted by the introduction of UEFI, Secure Boot, GPT etc as common options in many new computer systems, and this is reflected in changes to the Acronis Rescue Media too.

Please see the ATIH 2017 User Guide: Recovering your system to a new disk under bootable media which explains the process as it works with this latest version of the Rescue Media, in particular with the handling of hidden system or manufacturer partitions during a restore operation.

Please also bear in mind that Acronis True Image is a Home user product that is not really intended for use in a business environment as you have described.

Thank you Steve Smith for your prompt reply.

Sorry, i forgot to mention earlier in my post that we mostly use BIOS system and Hard Drive in Basic mode to install the Windows in new laptops though the laptop also supports UEFI and GPT.

It is in BIOS system that ATI 2016 and ATI 2017 does not create the required partitons. Does this mean that the newer ATIH are not able to handle the partitions properly in BIOS system and hard drive in basic mode??

I'll go through ATIH 2017 User Guide: Recovering your system to a new disk under bootable media and will let you know if it helped to resolve my problem.

 

Please see forum post: 128057: [Tutorial] How to recover an entire disk backup which was written for a restore on a system with BIOS / MBR as a help for another user.   The Summary panel shown on page 5 of the tutorial document will show you what partition sizes will be used for the restore operation.  If these are not shown correctly, then you would need to follow the process in the User Guide pages I gave the link for earlier, to do any resizing of partitions.

Singh_np

Question, you say you are using an image taken from a 500GB GPT format disk and restoring to a 1TB MBR format disk? 

Thanks for the picture, the question is again is the source disk a GPT format disk?  You are attempting to restore that image to an MBR format disk?  If yes it won't work.  Application will not convert a GPT format disk to MBR format. 

Ditto to Enchantec's last post.

2 things...

1) On your new systems, format your new disk as MBR/Legacy first - just in case

2) boot your recovery media in legacy mode to make certain that the restore is in legacy mode as well.  Just like there are Windows installer limitations whether the disk is formatted GPT or legacy, or the USB is booted legacy or UEFI, the same holds true for Acronis rescue media.  

Please look at the screenshots from this post for futher clarification... https://forum.acronis.com/forum/121829#comment-378318