Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

Issue: Unable to boot machine after imaging - Corrupt MBR

$
0
0

Issue

Some computers, most notably Lenovo machines, after being imaged will not boot. The only solution is to repair the MBR.. On Lenovo machines, this most commonly presents itself as a blank screen with just a blinking cursor on reboot.

 

Cause

This is caused by the computer manufacturer using a custom or unique MBR in the original image. Imaging tools (ImageW, Symantec) fail to capture and deploy the MBR correctly and the machine doesn't boot.

 

Resolution

There is a known resolution to this if using ImageW. ImageW has an option to re-write a default MBR (/t). To add this option to your script:

  1. Right click on the OSD script in the console and select Advanced Edit
  2. Locate the line containing the imaging command
  3. Add a /t to the command line
  4. Save and close the script

 

Note: In LANDesk Management Suite 9.6 you will want to make the change under OS installation > Deploy Image > Command-line parameters in the associated provisioning template.

 

 

The command line, after modifying should resemble the following:

REMEXEC21=h:\osd\imaging\2.0\imagew.exe /r /o /t /d:0 /f:"i:\image.tbi" /rb:0

Note: This will only work with ImageW 2.x


Viewing all articles
Browse latest Browse all 1803

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>