Snap deploy (3329) and Windows 7
This is the final outcome of my testing re Snap deploy version 3329. If anyone has had a different (more positive) result from this please let me know as I'm wanting to do a windows 7 rollout very shortly.
From the managed console:
* Works for for XP including universal deploy and other prep tools like SID changer changing name/domain etc
* Works for Win 7 for deployment only no universal deploy no prep tools like SID changer changing name/domain etc (options just never appear)
Standalone:
* Win 7 works fine, but no universal deploy (this is by design)
* XP untested but no universal deploy (this is by design)
Noted that Acronis drive image home should work with the same images(?) and does support universal restore but not SID changer etc, this could be handled by Microsoft sysprep(?)
I am having similar problems with Snap Deploy 3329.
When I create an image of a Windows 7 computer, I can re-deploy the image, but when the computer reboots it reports that Windows is corrupt and cannot boot. Windows 7 attempts to repair itself, but then reports it cannot and the computer shuts down.
The image is being deployed to the exact same hardware.
Dear Daniel!
Thank you for finding time to report about the issue, I will be glad to help you with it.
Unfortunately due to the lack of investigation information we can only guess regarding what caused the issue. So I would appreciate if you could kindly provide us with the following information:
- The sequence of steps you performed so that we could reproduce the issue
- The exact BSOD message
- Acronis Info from the source machine
- Logs from the folder C:\Documents and Settings\All Users\Application Data\Acronis.
Please contact us with the information gathered, we will review and find a solution.
Should you have any additional questions or have any difficulties with gathering the information - simply leave a comment here, we will definitely help you!
Thank you in advance for cooperation!
Using Acronis Snap Deploy 3 Build 3329:
1. I boot a Dell Optiplex GX780 installed with Windows 7 Professional using Acronis PXE.
2. I start the Snap Deploy Agent and deploy the Windows 7 Image to exactly the same hardware (an identical Optiplex GX780).
3. The image deploys, the server reports no errors.
4. When the target computer restarts after deployment, Windows 7 reports that the operating system cannot boot and it will attempt a repair. After several minutes, it reports that it cannot repair the operating system, and will now shut the computer down.
5. No BSOD.
6. Which computer do you want the log files from? The Snap Deploy Server or the image source computer?
7. Please find attached information from the AcronisInfo tool.
Hello Daniel,
Thank you for the information provided. I have analyzed it and found that everything is fine, except the fact that Acronis report was not created.
6. Which computer do you want the log files from? The Snap Deploy Server or the image source computer?
The logs should be collected from PC where OS Deploy Server component is installed.
This issue can be caused by incorrect partition recognizing. We are aware of some cases when the product marks wrong partition as active, and Windows fails to boot. To determine this, let's collect Acronis report two times:
1. From source system (as I mentioned, it was not created from AcronisInfo tool):
In order to create Acronis Report file, please download Acronis Report utility, run it and create a report. The default name of this file is "report.txt" and it is saved on your desktop.
Please attach the file to your answer in this thread.
2. Report from the deployed system. Since your system is not bootable, let's create the report file according to the instructions below:
Here are the instructions on how to obtain Acronis report:
- Download Acronis Report 51 utility;
- Run Acronis Report utility and select the flash drive option;
- Connect your flash drive and proceed with creating the bootable media;
- Boot the computer under consideration from flash drive and wait for report creation process to complete;
- Attach the report.txt file from the flash drive to your answer in this thread.
We are looking forward to hearing back from you at your earliest convenience.
Thank you.
Hello,
I'm having the same issues as reported. I created a baselined image on a Dell Vostro 220 running Windows 7 Pro. All workstations have the same hardware.
I used build 3329 boot media, and select standalone util. I go through the prompts and select where I have my master image stored on 1 of our servers. I know about not being able to join or change SID from reading the first post.When restoring partition is completed, the workstation restarts. Upon booting to Windows I receive "bootMgr"is missing.
Press ctrl+alt+del to restart.
I have the same problem with Win 7 Professional. Can create the images, no problem. All deployments finish with a reboot and that the image is corrupt and is trying to repair. I let it finish and reboot and everything seems fine. Status bar on laptop never shows anything, but manager console does. Build 3329. Dell D830 Latitude laptops.
I wonder if it could be the boot manager that is integrated in Windows 7. It's probably not being recognized.
Hi Alexander,
Here are the reports you requested. One is labeled "Source" and the other "target." "sourcerpt.txt" is from the computer that I created the image from; 'targetrpt.txt' is from the computer I am trying to deploy the image to (which will not boot after I deploy the image).
Thanks,
Dan
Hello all,
Luis, message that appears in your case is different. That's clear for me that it's related to Windows loader corruption. Please try to restore it manually as it's described in this article.
Deb, what is the exact error message you receive?
Daniel, thank you very much for the report files! I have checked them and here's what I found:
- Source system drive contains the following error on system partition:
Disk 1 Partition 2 FS: NTFS File system error: 24 (MFT bitmap corrupted)
- Restored system has 2 drives, and for some reason the system has been deployed to the second drive, that drive marked as Active. The cause is that your first drive is marked as Active too! Probably this consumes the system and you're not able to repair it because of this fact (I have marked Active in bold so you can check it):
1- d(0) MBR 478M 512K -1 p(1) CCCC 478M 478M 457M FAT32 0B FAT32 A----v 2- d(1) MBR 149G 11M -1 p(1) --DD 100M 100M 76M NTFS 07 NTFS, HPFS System Rese A----v -2 p(2) --EE 149G 149G 138G NTFS 07 NTFS, HPFS ........... -----v
In this case, I would suggest you to remove second drive from the system and try deploying with only one drive plugged. Please let me know the results. Regards,
Hi Alexander,
Thanks for looking at the logs and reports.
Both the target computer and the source computer have only one (1) hard disk drive. There are two (2) partitions on the source drive (and therefore 2 partitions in the image being deployed).
Windows 7 creates a "recovery" system partition when it is installed, roughly 100MB in size.
I will try deploying only the OS partition in the image and see if that helps. If that does not work, I will re-image the source computer and select only the OS partition as part of the image. I will post back with my results.
Hello Daniel,
Thank you very much for the clarification.
I will wait for the results from you.
If you feel that we're not answering this thread as fast as you wish - please PM me so I can get back to it as soon as I can.
Best regards,
I've imaged only the OS partition, and numerous times have been unsuccessful on a 100% completed deployment. I've spend 70% of the work day re-imaging and deploying the same image with no WIN results.
I've even tried the article that was referred to me on fixing the MBR and FIXBOOT options.
I will run those reports on my source and deployed system in the morning.
UPdate: I was able to successfully deploy a Windows 7 image. Upon Windows 7 boot up I come across "this copy of Windows is not Genuine"... Keep in mind that both the source and target are the same hardware and manufacturer.
Hello Rex!
Thank you for bringing this question up, let me clarify the situation.
You are correct: at the moment we can deploy Windows 7 only as it is, without changing the SID and other settings due to we haven't updated Acronis Snap Deploy to support this OS - thus it's not recognized and recovered "as is". Currently we are working on updating the product to support Win7. Also you can see the list of supported operating systems here.
Yet Acronis Universal Deploy does support Windows 7 OS, and there should be no issues with using it, so I would appreciate if you could kindly give me additional details regarding this question: does Acronis Universal Deploy simply disappear or it gives you an error, etc.?
It is perfectly right that home version of the Acronis products doesn't provide you with the same functionality of changing SID, domain/name as Acronis Snap Deploy does but that's the design of the product - it was created more for protection than for deployment. I also would advise you to take a look at the backup compatibility table here, as far as the ability to recover the image of Acronis Snap Deploy with the help of home program depends on the version of the product you have.
I would appreciate if you could kindly let me know whether there is still something confusing, I will be glad to clarify!
Also feel free to share your concerns and ideas with us - we do appreciate it and will do our best to improve the products to suit your needs!
Thank you!
When can we expect to see an update for Snap and deploy so we can change SID and joining domain on win7 machines?
Win7 have been out for a while now and I need to roll out some computerlabs.
Hello Luis and Gulbrandsen!
Dear Luis, thank you for keeping us updated! I would appreciate if you could kindly specify how you finally managed to successfully recover the Windows 7 image?
I regret to inform you that unfortunately we are not responsible for fixing "This copy of Windows is not Genuine" inconvenience: Windows 7 assigns its license to some particular hardware and may identify that it differs from the original one after deployment. In order to fix it you need to contact Microsoft Support, they will definitely help you!
Dear Gulbrandsen, thank you for your question. I have contacted Development team. We were notified that the next build is currently in production and we should have it released soon, but unfortunately there are still no time frames available. But you can subscribe for our newsletters and as soon as we have the newer version available for download you will be notified about it!
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
Yana,
We have a technet subscription for Windows 7 Enterprise edition with a large amount of activiation keys. AFter the 1st failed attempt I imaged a completely new source workstationg with Windows 7 Enterprise edition. Deployment was successful, when workstation restarted I received "boot manager is missing" I executed the repair options and went into the command prompt and entered bootrec.exe commands. I had restarted the workstation and received the same message so I ran the repair option again but this time! I let windows repair the boot manager and all is well now.
Yana,
Is there an ETA on the next build of Snap Deploy? I am having problems like everyone else. I can not get Win7 to work with Snap Deploy bld 3329. I am unable to make any changes to the default template with success. Can not rename, new sid, or join domain.
Hello,
I am trying to convince my boss to buy SnapDeploy3 with Universal Deploy to deploy WinXP Pro to 3 sets of hardware computers. We have have about 30 workstations. I downloaded the trial version which comes with 5 licences. I went through the guide but it does not seem to give a clear explanation about what i am trying to achieve from AcronisSnapDeploy3. I need to create a master image, and i need to be able to deploy that image to workstations on the network. Can anyone help with a simple step by step guide about what components to install and on which machine to install it on (server or on any workstation)? i tried installing it on the server but it requires a reboot which is not ideal in our case. will it work if i install it on a workstation and deploy image to other workstations and what do i have to do to achive a succesfull image deploy, please can any one help? I can not bear the idea of using Norton Ghost.
Very much appreciated
Noureddine
Noureddine,
Configure a image on a master computer, make sure you have the appropriate licensing from MS. Once you have successfully configured a master computer, use the Acronis boot media and boot into the Image creator.
You will go through the steps on creating the image and saving it either on a Server, shared folder, or ext hard drive.
Now! when deploying the computers you don't necessarily need to use the management console.You can use the boot media and select the stand alone utility and go through the prompts. As far as licensing is concerned. I purchased licenses but I assume if you use the OS deploy which I did not use.
Hello all!
Thank you for your comments and feedback, we really appreciate that!
Luis, thank you for describing the issue. I cannot be sure, but from your description it looks like you have installed Windows 7 with the 100 Mb system partition, but imaged and deployed without it. In this case the system may refuse to boot and will ask to repair it. I appreciate you let us know that currently all it fine and you managed to fix the machine, thank you!
Dear Brad, I regret to inform you that unfortunately there is no ETA on the next build of the Acronis Snap Deploy 3. Anyway I will request it right now and forward your comment to our Management team so that they could take an action on it.
I would like to mention that actually we had improved the latest build so there is an opportunity to change SID in the latest build of Acronis Snap Deploy 3, feel free to check release notes. Unfortunately due to the lack of information I cannot tell for sure, but this issue usually occurs in case the OS in not identified in the image. This happens in case you haven't included into the image 100 Mb system partition.
I would appreciate if you could kidnly give me a bit more details regarding how you imaged your Windows 7 and what exact settings are not available for changing?
Noureddine, thank you for your question and many thanks to Luis for kind assistance.
I will be glad to guide you shortly through the process of imaging and deploying. The easiest way to do it is the following:
- Install Management Console, OS Deploy Server and PXE Server onto any suitable machine
(it can be either server or workstation - doesn't matter). These thre are necessary for imaging and deployment process
It would be better if that could be the machine you are not going to image or deploy, otherwise you will have to reboot it into the Acronis Bootable Rescue Media CD you can create by means of the product (Tools -> Create Bootable Rescue Media) - Configure PXE to contain Master Image Creator (for imaging) and Agent (for Deployment) (see chapter 3.7 in the User's Guide)
- Reboot the target machine we are going to take an image from and get into BIOS
- Set the machine to boot from the NIC. Reboot
- Your machine will boot directly to the PXE Server. Choose it to boot into the Master Image Creator, get back to the Management Console and follow the steps of the Wizard to take an image from the machine.
- Set your target machines to boot from PXE server.
In order to boot them to the Agent for deployment you can choose Configure PXE and at the step where you choose what components to upload there tick the option of autobooting at the bootom of the page and choose to do it into the Agent. - Create the template you will use for deployment (chapter 9 in the User's Guide)
- Boot your machines from PXE.
They will appear in the list of available machines ready for deployment. - Choose the template created and start the deployment.
You can also create the Acronis Bootable Rescue Media CD with all the components needed to perform the same actions.
Please let me know in case somethins is confusing - I will be glad to clarify! Feel free to contact us immediately in case you have any additional questions - we will surely help.
Thank you!
same problem here.
Hardware: two identical Dell E6500 Laptops.
(I even tried just changing the harddisk in the same Laptop after creating the Image.)
Software: Win7 Ultimate 64bit (german)
Snap deploy b3329
standalone Backup with cd..no errors.
standalone deploy with cd...no errors.
bootup the OS: BSOD and instant reboot
Win7 repair...does nothing
Win7 repair from CD...does something but does not help...still BSOD at bootup.
This is ridiculous, especially as Acronis claims compatibility here:
http://kb.acronis.com/content/2870
“Acronis Snap Deploy 3 supports deployment of images of Windows 7 32 bit and Windows 7 64 bit, both with and without Acronis Universal Deploy. Installation of Acronis Snap Deploy 3 components on Windows 7 32/64 bit is not guaranteed.”
Would you mind to hurry up a bit...Win7 is RTM quite a long time and I got about 30 Laptops to setup and an other 30 to upgrade.
I would even pay for a working SnapDeploy4 again...
And yes...Win7 requires 2 partitions...only is 100mb by default, the other got the rest of the hard disk space.
Hello Walter!
Welcome on Acronis Forum and thank you for finding time to report about the issue!
I sincerely regret that you faced this issue and that you had a bad experience, but I would like to assure you that currently we have no reported issues of BSOD after correct deployment onto the target machine. Thus I assume that the cause of the issue is not in the product, but in some glitch of the process.
Unfortunately due to the lack of information it is impossible to identify the reason, and I would appreciate if you could kindly speicfy the following:
- BSOD error message (should the machine continue to reboot, press F8 and choose to Disable automatic restart on system failure)
- exact sequence of steps which lead to the issue
- whether you have deployed the imahe including 100Mb system partition
- Acronis Info
We will also need Deployment and Agent logs, you can obtain them by following the below steps:
- Launch Acronis Snap Deploy Management Console;
Select the Manage Deployment option;
Specify the credentials for connecting to the machine with Acronis OS Deploy Server and click OK;
Click on the Show operations log button on the icon bar;
Select the date you need the log from and click on the Save log entry to file (diskette icon) button;
Specify the path and the filename for the log file and click Save; - Acronis Snap Deploy Agent logs
Please kindly gather the information and submit a web request. I would also appreciate if you could kindly let me know the case number so that I could make sure your request is handled in a proper way.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
1. Will look into at if I got time next week. Got a lot of thinks to do right now.
2. how exact do you want the steps? I created the image...with the DVD only to an external USB hard drive...and deployed it the same way...works with Winxp...so there are no problems with the steps. I used the same hardware as with WinXP so there are no problems in the hardware.
3. yes I did backup and deploy also the 100mb system partition.
4. no use als I cant boot up the machine.
1. not possible as I do it offline not over a server but from an USB drive.
2. there are no logs.
and BTW I am not your paid beta tester...I am a paying user...can you understand that Yana? I dont get paid to play around with faulty software but to run things...your software worked and works well with winXP. If it does not with win7 I will have to find something that works. And as it looks like I am not the only one who got Problems with your Win7 support I dont see the point in doing the work your company should have done 6 months ago.
Just dont take it personal Yana...ok?
Hello Rex (Quote1)!
Thank you for bringing this question up, let me clarify the situation.
You are correct: at the moment we can deploy Windows 7 only as it is, without changing the SID and other settings due to we haven't updated Acronis Snap Deploy to support this OS - thus it's not recognized and recovered "as is". Currently we are working on updating the product to support Win7!. Also you can see the list of supported operating systems here.
Yet Acronis Universal Deploy does support Windows 7 OS, and there should be no issues with using it, so I would appreciate if you could kindly give me additional details regarding this question: does Acronis Universal Deploy simply disappear or it gives you an error, etc.?
It is perfectly right that home version of the Acronis products doesn't provide you with the same functionality of changing SID, domain/name as Acronis Snap Deploy does but that's the design of the product - it was created more for protection than for deployment. I also would advise you to take a look at the backup compatibility table here, as far as the ability to recover the image of Acronis Snap Deploy with the help of home program depends on the version of the product you have.
I would appreciate if you could kindly let me know whether there is still something confusing, I will be glad to clarify!
Also feel free to share your concerns and ideas with us - we do appreciate it and will do our best to improve the products to suit your needs!
Thank you!
When can we expect to see an update for Snap and deploy so we can change SID and joining domain on win7 machines?
Win7 have been out for a while now and I need to roll out some computerlabs.
Hello Walter (Quote 2!
Welcome on Acronis Forum and thank you for finding time to report about the issue!
I sincerely regret that you faced this issue and that you had a bad experience, but I would like to assure you that currently we have no reported issues of BSOD after correct deployment onto the target machine. Thus I assume that the cause of the issue is not in the product, but in some glitch of the process.
Unfortunately due to the lack of information it is impossible to identify the reason, and I would appreciate if you could kindly speicfy the following:
- BSOD error message (should the machine continue to reboot, press F8 and choose to Disable automatic restart on system failure)
- exact sequence of steps which lead to the issue
- whether you have deployed the imahe including 100Mb system partition
- Acronis Info
We will also need Deployment and Agent logs, you can obtain them by following the below steps:
- Launch Acronis Snap Deploy Management Console;
Select the Manage Deployment option;
Specify the credentials for connecting to the machine with Acronis OS Deploy Server and click OK;
Click on the Show operations log button on the icon bar;
Select the date you need the log from and click on the Save log entry to file (diskette icon) button;
Specify the path and the filename for the log file and click Save;- Acronis Snap Deploy Agent logs
Please kindly gather the information and submit a web request. I would also appreciate if you could kindly let me know the case number so that I could make sure your request is handled in a proper way.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
Just checked your latest build and it still says Build # 3329 which you confirmed earlier in quote 1 (in my post) that win7 SID change etc are not supported.
Last quote you says its now supported but there are no newer build on your update page.. Its useless for our Schools if it can't change SIDS and rejoin domain.
-edit-
I have the excactly same problem as Walter Richtarsch and lots of others here btw.
Dear Walter and Gulbrandsen!
Thank you for your comment and attention.
Walter, thank you for your reply and for details specified.
I completely understand your concern and would like to assure you that we do work with Windows 7 and will we find out what exactly went wrong in your case.
Thank you for specifying that you are using the Bootable Media CD, it will make the investigation process easier: instead of all the logs support will need just Acronis Linux Report.
We will definitely wait for news from you, thank you for finding time.
Dear Guldrandsen! I regret that I confused you - please, accept my sincere apologies. I meant that we have updated the current build, so it now supports SID change (check the Release Notes).
We will be glad to help you with the issue you faced, but in order to be sure in the case of it, we will need some diagnostic information, mentioned in this comment.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
No need to thank me Yana...I did not find time and I don't think I will in future.
I am more likely to invest my time in building an answer file and using sysprep. YES this means no money for you.
and for the rest of you (Gulbrandsen Kristoffer for example)
http://blog.brianleejackson.com/sysprep-a-windows-7-machine-%E2%80%93-s…
and also read the comments.
I tried to upgrade now and and it looks like it have fixed the boot problem but it still stand forever when it tries to change SID and rejoining domain.
I have also started to use WDS and building sysprep files.
Its free and it automatically get them into domain and newsid on the computers. WDS also supports multicast now.
http://technet.microsoft.com/en-us/solutionaccelerators/dd407791.aspx MDT 2010 is a really good thing if you want to deploy win7. You can also make upgrade seamless. IT automatically take backup of the old documents and put it in again after a clean install if you set it up right.
It is a little more work to set up with answer files but can be worth it as long as Acronis doesn't support WIN7 fully.
For those of you having issues deploying Win 7:
We were having some of the issues noted above. However, during out trial and errors, we found a solution. Win7 creates two partitions with you install it. You need to select both partition when creating the image. Then, you need to select both partitions when deploying. By doing this, we are now able to successfully deploy Win7. It also changes the SIDS now.
Matt
Major issues with Snap Deploy 3.0 Build 3329
I got Windows 7 on 10 Netbooks since Acronis listed that Windows 7 is fine.
I have Win 7 64bit Home Prem... I image the configured Netbook using the latest build 3329 from which I created the bootable media and burned it on to a CD.
When trying to install the Snap Deploy Agent. I get stock on the blue screen Processing, Please wait and it never loads the Agent... So I tried the Stand Alone Utility which worked fine the 1st time, but when accessing the user accounts all the icons were not there and default options on resolutions and IE were changed as well. I went and re-imaged the Netbook again just to make sure something didn't go wrong...
2nd time I push the new image didn't even work I just got a message that deployment was done successfully like 2 seconds after started it. Computer would not boot to Windows and it would just hang on the blank (Black) screen....
I went back to the original image I used the 1st time using Stand Alone and it took the same amount of time like 1st time about 45 minutes, but this time the image that worked had issues with start up and could not find the boot so it asked to be repaired...
I tried to repair it using Win 7 and after 30 mins of attempting to repair it failed again... So I am stock with the comp that doesn't work at all and an image that worked at one point with Stand alone...
So issues:
1. Snap Deploy Agent won't load pass the blue Screen Processing, Please Wait (Shows 2 Screens and Tower in the back)
2. Image created using build 3329 is not working for some reason in Stand Alone
3. Stand Alone will not work with new image created it done in 3 seconds stating that its successful, but it actually corrupts the original windows.
I am using Dell 11Z (Inspiron 1110) it has 1HD with 3 Partitions 1. Recovery 2. OS 3. FAT16 (Boot strap)
@ Matt Schmitt
Beens there done that....it does not work. EOD
I will wait and see if Acronis get this worked out soon...there are too many useres having problems so I wont even consider it could be an error on my part. And it works with WinXP so they clearly did not do their homework with win7.
shame on Acronis.
Hope this helps someone.
I have found that when imaging Win7 using Snap Deploy 3 build 3329 there is a BIOS setting that you have to double check on the machine that is used to make the image as well as the machine(s) your deploying to if your using SATA drives.
On modern PCs there are 3 ways of communicating with the SATA drive -- IDE, RAID, or AHCI. You need to switch this to IDE in the BIOS or the image will not work. This needs to be switched on all machines, when making the image and when deploying that image. If your set on AHCI the image creation process wont fail but the image wort work when deploying it either.
Check your BIOS settings.
I checked the BIOS settings on the Lenovo T410 I am having these issues with and only has the ACHI or compatibility modes. When I changed it from ACHI to compatibility it would not recognize a HDD. I rebooted and as soon as Windows 7 started to load it BSOD 0x7B, a storage BSOD of course. Switched the setting back to ACHI and the unit booted properly; however, the issues are still yet to be resolved... explorer errors as well as control panel with error with boot paths.
Does the new version just released support changing SIDs in 7 now?
Anyone test it with 7 yet?
I have been facing this same problem for months but I'm usually able to get the image to work. It almost seems like the boot disc sees the OS partition as D: for some reason. Usually when I push an image, reboot the computer and get the "bootmgr is missing" error, I pop in a Windows 7 disc and run the repair utilities. This has fixed it 100% of the time (about 10 times).
The new build is changing SIDs for windows; however, as mentioned by Jody Wood doing the repair (or command line using bootrec /fixboot and bootrec /rebuildbcd cmds) fixes the partition/boot issue. However, the T410 is working fine without having to do that. We are experiencing this issue with other Lenovo models. I will return 4 months from now to check for a reply :/
Does the new version just released support changing SIDs in 7 now?
Anyone test it with 7 yet?
Does the new version just released support changing SIDs in 7 now?
Anyone test it with 7 yet?
the version just released is build 3470. Changing SIDS in XP but not in W7. In W7 template (image chosen is a W7 in the template), the changing SID option, simply do not appear.
The new build is changing SIDs for windows; however, as mentioned by Jody Wood doing the repair (or command line using bootrec /fixboot and bootrec /rebuildbcd cmds) fixes the partition/boot issue. However, the T410 is working fine without having to do that. We are experiencing this issue with other Lenovo models. I will return 4 months from now to check for a reply :/
Has not been 4 months yet but I will reply with the same issue. My problems lie with a Lenovo product made in the past 2 years. T400, X301, T510, W701ds, T400s, T410, T410s. I work with all this equipment and have the issue of Boot MGR missing or just a blinking cursor once the image has been deployed. No errors on the server. *IF* we remove the Lenovo recovery partition then and ONLY THEN do we not see these errors. Can Snap Deploy not be given the option to actually set the active partition? we have the choice to set which partition we want to assign the image too but not which one we want to be active. If I am wrong please correct me as this is causing MORE work than just rebuilding each machine from scratch.
It took over 1 year for the NIC issues to be resolved, I do not think my company can keep using Acronis if the rest of these problems are not fixed in a more timely manner.
Hope this helps someone.
I have found that when imaging Win7 using Snap Deploy 3 build 3329 there is a BIOS setting that you have to double check on the machine that is used to make the image as well as the machine(s) your deploying to if your using SATA drives.
On modern PCs there are 3 ways of communicating with the SATA drive -- IDE, RAID, or AHCI. You need to switch this to IDE in the BIOS or the image will not work. This needs to be switched on all machines, when making the image and when deploying that image. If your set on AHCI the image creation process wont fail but the image wort work when deploying it either.
Check your BIOS settings.
I have noted this as well, however if the image is made in AHCI mode, it seems to deploy fine in that mode. Just make sure to match the BIOS drive mode with the image. XP is typically IDE mode and Win7 is typically AHCI.