Upgrade from Snap Deploy 3.0 to 4.0 - Couple issues

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 2

I have Snap Deploy 4 running on a 2008r2 Server. Version 3 ran flawlessly, but since I upgraded to version 4 earlier this week, it is yet to function remotely like 3 did.

1) None of my templates were saved during the update, I have had to recreate these. The way the naming works is very annoying in this version. I created a template for a Lenovo T500, and in the template, it has a generic name and is set to join the domain. Doing one computer at a time, I found the "Individual Settings" and gave that computer a unique name, and also specific that it join the domain, as well as change the security ID. The computer is getting the image, being assigned the unique name, but it is NOT restarting once the image is complete. Because of this, I feel like some Snap Deploy process is not running. The computer is not being joined to the domain, and I am not seeing the usual Security ID change popup I am used to. Obviously this is a huge annoyance and involves more hands-on time for me.

2) We have several Lenovo T420 laptops now. In version 3, these would not PXE boot into the Snap Deploy server, so I had been doing them with the standalone version. I upgraded to 4 because I knew the NIC was supported on these machines. Templates are created the same way. The Deployment fails immediately and the log shows the following error code:

Host '10.1.153.108' has failed the deployment.
Additional info: --------------------
Error code: 1
Module: 52
LineInfo: 9C5A16066A60D4FF
Fields: $module : "C:\Program Files (x86)\Common Files\Acronis\Agent\osd_server.dll"
Message: Host '10.1.153.108' has failed the deployment.
--------------------
Error code: 6
Module: 51
LineInfo: A6EF0BE19DB526A4
Message: Failed to map BIOS disk '2'.

Do, 07/05/2012 - 19:07
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Beiträge: 0
Kommentare: 27

Hello Brandon,

Thank for using Acronis software.

First of all, I apologize in Acronis name if you are disappointed with the way that Acronis Snap Deploy 4 differs to Acronis Snap Deploy 3. In Acronis we always want to improve our products to provide the best experience for all our users. I took note of your feedback because we consider it very important for us in order to make us better.

About deployment issue, there are several reason that could explain that:

1- One reason is that the disk specified in the template is not present in the target system or is not detected. In such case:

  • Check that the drive specified in the deployment template is present in the target system.
  • Make sure that you are using the latest build of the product.
  • If the drive is still not detected, gather the following information and contact our Support team:
  • Acronis Linux Report from the target machine;
  • Acronis Report from the target machine;
  • Provide relevant deployment template from \Documents and Settings\All Users\Application Data\Acronis\DeployServer\Configs\ folder on the machine where Acronis OS Deploy Server is installed

2- Another reason could be that master image has several partitions, and some partitions do not have enough free space and this image is deployed to a target disk of smaller capacity. In such case, change the deployment template and deploy the master image without the service partition.

3- Another cause could be that the mass storage controller is in IDE mode instead of AHCI/SATA (or vice versa) and there are two or more hard disks on the machine. Then try try switching to AHCI/SATA if the mode is IDE (and viceversa)

If there is anything else i can do for you, please let me know.

Thank you, have a good day.

Fr, 07/13/2012 - 21:02
  • Anmelden, um Kommentare verfassen zu können
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.