Pc's wont boot after deployment
Hi,
we've have a few pc's (optiplex 745/780) which wont boot after being deployed with a kbox image (made from a optiplex 990).
the OS in Windows 7. All Drivers are availble for the machines.
i also use some tasks for partitioning and for BCD fixes.
***it looks like there is a problem with the bcd script, will test and report
am i doing something wrong ?
we've have a few pc's (optiplex 745/780) which wont boot after being deployed with a kbox image (made from a optiplex 990).
the OS in Windows 7. All Drivers are availble for the machines.
i also use some tasks for partitioning and for BCD fixes.
***
bcdedit /store D:\boot\bcd /set {bootmgr} device partition=C:
bcdedit /store D:\boot\bcd /set {default} device partition=D:
bcdedit /store D:\boot\bcd /set {default} OSdevice partition=D:am i doing something wrong ?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
petrybosch
13 years ago
partition C: is the windows 100mb system partition.
partition D: contains the actual installation.
partition D: contains the actual installation.
Posted by:
petrybosch
13 years ago
the problem only seems to occur with the optiplex 780 machines.
we've manually installed windows 7 x64 on them without any problems.
After the manual installation we created an image from that machine.
The image was then deployed to another 780. imaging went fine without any problems.
but after the reboot the machines hang either while loading pxe (1st boot device).
or hang with a blinking - (with hdd as 1st boot device).
im confused...
i'll going to try a bios update, installed version: A04, current version A10
we've manually installed windows 7 x64 on them without any problems.
After the manual installation we created an image from that machine.
The image was then deployed to another 780. imaging went fine without any problems.
but after the reboot the machines hang either while loading pxe (1st boot device).
or hang with a blinking - (with hdd as 1st boot device).
im confused...
Posted by:
petrybosch
13 years ago
Solved !
the Harddrive is by default connected to SATA0 (on the motherboard), i changed it to SATA3.
only on sata3 the harddrive is recognized in the bios (while ahci is enabled).
the Harddrive is by default connected to SATA0 (on the motherboard), i changed it to SATA3.
only on sata3 the harddrive is recognized in the bios (while ahci is enabled).
Posted by:
petrybosch
13 years ago
today it looked like the problem wasnt fixed after all.
after an image deploy i only see BOOTMGR missing, there has been no changes made to the image or its scripts.
now im trying to deploy the image again with the disk operation on ATA (instead of ahci).
in the compatibility list is says that he will use "gendisk" for the HDD... sound like a missing driver ?
after an image deploy i only see BOOTMGR missing, there has been no changes made to the image or its scripts.
now im trying to deploy the image again with the disk operation on ATA (instead of ahci).
in the compatibility list is says that he will use "gendisk" for the HDD... sound like a missing driver ?
Comments:
-
did you ever come up with a fix for this? We are currently having this issue where I work as well. I am trying to develop a win7 64bit image for our 780s and get BOOTMGR missing when I bring the image down to another 780. - Strangeronfire 11 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.