Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
998 Views

Can't install Windows 7 using redirect CD-ROM

Hello!

I have a PC. Configuration = Intel DQ57TM motherboard with latest BIOS, Core i5 660 and no CD/DVD drive.

From laptop I connect using Intel vPro AMT to a PC. Run Intel Manageability Terminal Tool for disk redirect - mount ISO from laptop drive with Windows 7.

Then I do a remote reboot to redirect CD:

.

Computer sucsessfully rebooted, I connect using VNC, installation begin. But when I choose a disk I got an error:

setup was unable to create a new system partition or locate an existing system partition

I read Windows installer logs and as I see - if we use redirect cd option in Intel AMT then we have no bootable HDD in BIOS. We have only bootable CD device. And Windows do not want to install on PC with no bootable HDD. Very strange solution from Intel - why they remove bootable HDD from BIOS to change boot order?

Maybe where is a workaround? I can't use RIS and PXE now.

0 Kudos
2 Replies
Jacob_G_Intel
Employee
82 Views

Hmm. I just tried this from a DQ45CB and Win7 is installing now. Maybe I havn't waited long enough yet; at what point during the install do you see the failure? Or could it be specific to a DQ57TM? Also, I used RIL instead of commander: /docs/DOC-5943 http://communities.intel.com/docs/DOC-5943. Maybe that'll help?

Anyhow, I'll let my install finish and see what happens. Let me know if you find anything or have more details about the failure.

BTW - You can make the remote install faster by:

Extract Win7 ISO files to a shared drive

Build a WinPE ISO /docs/DOC-5095 http://communities.intel.com/docs/DOC-5095

Use the linked UCRD to boot WinPE over IDEr /docs/DOC-5552 http://communities.intel.com/docs/DOC-5552 (this step is optional).

In WinPE, map the share and run setup

This way, most of the install files arew copied with in band network drivers (via WinPE) which are generally faster than using IDE Redirection.

idata
Community Manager
82 Views

This sounds like a BIOS problem I encountered once where the BIOS replaced the 1st boot device when it received IDEr request from remote instead of simply adding another boot device to the top of the bootable devices list.

Reply