Deploy only reserved partition and C drive

Hello!

You can set how to utilize the free space on the target drives and set the number of deployed volumes in Deployment settings  when creating a deployment template

Thanks for the reply. The option to replace the volume is only available if I select only one volume either C drive or Reserved partition as you can see in the following link. Check the second pic in the below link.

https://www.acronis.com/en-us/support/documentation/ASD5/index.html#135…

Obviously deploying either of the volumes won't make the deployed system bootable so I'll have to select both the volumes but when I do that the replace volumes option under target disk layout is not available. So what's the solution in that case ?

Thanks 

In this case, you will need to perform the deployment twice for C partition and reserved one if the drives' layout on target machines coincide with the source disk layout.

Otherwise, you will need another Acronis solution (Acronis Backup 12.5 Workstation) that allows to back up the C drive with the reserved partition and restore them to C partitions on target PCs:

https://www.acronis.com/en-us/support/documentation/AcronisBackup_12.5/index.html#33487.html

Please use a trial version of Acronis Backup 12.5 to be sure it suits your needs.

Thanks alot Maria. I'll go through both the solutions that you provided before deciding on how to take this ahead.

Thanks again for the quick responses :)

Hello,

Just an update on the above solutions. After trying the first solution of performing the deployment twice ( In my case its thrice since I am installing Windows 10), the installation process goes smoothly until I face this error. Please check the attached image. 

The same process goes smoothly if I deploy the entire disk and not just the reserved partition and C drive.

Any idea where am I going wrong ?

Hello,

sorry for the delayed reply. Have you tried to deploy the whole drive with all volumes? Was this the deployment successful? If you receive the same error when deploying the whole drive, then please contact Acronis Support Team for further investigation.

Hello,

As mentioned in the previous post, I've had no issues booting up the sysprepped Windows 10 system after deploying the whole drive.

The above error comes up only after deploying specific partitions like Recovery Partition (450mb), EFI Partition (100mb) & C drive while keeping the D & E drives containing data as it is.

Also I had a chat with an Acronis support executive named Vijay with Case no.03724801. He suggested that I take the image of those partitions using the standalone utility which I did but deploying that image also ended up with the above error.

Any idea?

Hello exus69,

You mentioned that the image in question was prepared with the Sysprep. I'd also try deployment without Sysprep, but with Acronis Universal Deploy applied https://www.acronis.com/support/documentation/ASD5/index.html#13448.html 
With the results of this test, please raise a support ticket, so that our engineers can conduct more in-depth investigation and find the root cause of the issue. Let us know the ticket ID, so that we can keep an eye on the investigation process. 

Hello,

I would prefer the sysprep way because many times the target systems are of different configurations.

Thanks

exus69 wrote:

Hello,

I would prefer the sysprep way because many times the target systems are of different configurations.

Thanks

That's exactly why  Acronis Universal Deploy is there.  It basically does the sysprep and hardware prep for different types of hardware on the fly during deployment, without having to do it before or after the image.

Keep in mind that there is a sysprep limit.  In our office, we take a base image of a system that has never been sysprepped, then deploy it to unique hardware with Snap Deploy Universal Deployment and never have to worry about hitting that limit. 

But, if you take an image of a machine that has been sysprepped, deploy it, image that, deploy it and image and deploy it again, then you'll hit the Windows sysprep limit and have to start over with a new image at some point.

Regardless of your preferred method, it is best to update your base system image in an non-sysprep status, so you can continue to apply updates, patches, application changes, etc.  Once you have your image, then sysprep it (if you plan to keep this method) and take a new image of that (offline with rescue media before the OS boots up again) and deploy that.  When it's time to update your image, revert back to the one that did not have sysprep applied and rinse/repeat.

Ultimately though, you don't have to worry about sysprep if you use universal deploy in Snap Deploy.