Cannot image Lenovo ThinkPad T410

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 0

I am posting here, as it seems like your forum moderators provide much more meaningful support than your support department. I have submitted three requests for help weeks ago, and the ONLY response I received was emails asking if the problem had been resolved to my satisfaction. The answer to that question would be an emphatic NO.

We have SnapDeploy 3, build 3329. Our bootable media is the same build number. We are able to successfully deploy other machine types, but have not been able to deploy Lenovo T410 systems. I have tried deploying via PXE boot, bootable media with the network connection version of SnapDeploy and SnapDeploy Standalone.

In all three scenarios, the client computer waits without incident for the initiation of the imaging process. As soon as the process is started, the client reports success and reboots (even though the option is set to shut down).

When using SnapDeploy booted from local media and connected to the deployment server, at the moment of failure, the server logs two entries: "Client failed to deploy" and "Client removed from session." Example log entries from an attempt are attached.

The laptop BIOS has been configured for SATA Compatibility mode (not AHCI). Still does not work, same exact behavior.

Please provide a solution, not an apology. I await your response.

Attachment Size
logexample.txt 552 bytes
Fri, 10/08/2010 - 21:30
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Evan!

Welcome to our Forum, we're glad to greet you here. I'm sorry for the inconvenience you've faced with support and product, and will be glad to help you.

Unfortunately due to the lack of information it is hard to identify the exact cause of the issue. It can be either the lack of free licenses or the network connectivity issues, or bootable components glitch. In order to solve the issue we need to localise the cause.

I've checked our cases base for your open requests in order to review the details of the problem, but unfortunately couldn't find any. I assume you were using an alternative e-mail address for submitting the cases. Could you please specify me it's numbers? 

Meanwhile in order to localise the issue, let's update the bootable components of the product - I will send you the instructions in a minute - and see whether the issue persists.

Should it remain, please gather

  1. OS Deploy Server logs
  2. Deployment Agent logs
  3. Wireshark

After that please kindly submit a support request with the information attached and let us know it's number: we will make sure it's 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!

Tue, 10/19/2010 - 11:42