Hey all,
ZCM 11.2.3a MU1
We currently mostly run Windows XP for all our workstations, and in turn, it was easier for us to use the ATA/IDE controller method to deploy my winXP image (hardware independent with image addons for drivers)
Now, I've been testing my Win7 image recently using the ZCM imaging engine and I've run into a hiccup, I was hoping someone could help shed some light on this and what they've possibly done to get it running again.
Scenario 1:
BIOS settings are set to ATA, Windows XP was imaged and is current image. I then img the hard drive using img rp 10.x.x.x win7baseimage which works fine. I can then go to the device manager and find the devices that were not picked up, etc, to help build an addon driver image.
If I decide at this point that I'd like to work with AHCI, I go into the BIOS, I set my controller settings to AHCI, go back to the imaging prompt and once again I image using: img rp 10.x.x.x win7baseimage
Once the machine completes its install, I reboot the machine and am now left with a non-functional boot sector. (i.e. no bootable device found). I've tried recovering the MBR having used this method against another laptop that was imaged using AHCI:
dd if=/dev/sda of=mbr7.img bs=446 count=1 to create the file and then dd if=/mbr.bin of=/dev/sda bs=446 count =1 which is supposed to overwrite the MBR and potentially have it working.
This will result in a non-bootable drive and I've yet to figure out how to make it boot, other than running a manual Windows 7 installation using the install disc and manually building my workstation. Once I do this, I can image again. So I know it has something to do with the way the MBR works.
Scenario 2:
BIOS settings were set to ATA and had Windows XP as the current image. I immediately change the controller settings to AHCI, I then image the hard drive using the previous command to image my HDD and it works fine. I re-image a second time to test, it still works great.
Has anyone else run into this scenario and if so, what are you recommended steps? I have a feeling as if my MBR is all messed up, but I'm unsure how to fix the situation.
Any help would be greatly appreciated.
Thank you
ZCM 11.2.3a MU1
We currently mostly run Windows XP for all our workstations, and in turn, it was easier for us to use the ATA/IDE controller method to deploy my winXP image (hardware independent with image addons for drivers)
Now, I've been testing my Win7 image recently using the ZCM imaging engine and I've run into a hiccup, I was hoping someone could help shed some light on this and what they've possibly done to get it running again.
Scenario 1:
BIOS settings are set to ATA, Windows XP was imaged and is current image. I then img the hard drive using img rp 10.x.x.x win7baseimage which works fine. I can then go to the device manager and find the devices that were not picked up, etc, to help build an addon driver image.
If I decide at this point that I'd like to work with AHCI, I go into the BIOS, I set my controller settings to AHCI, go back to the imaging prompt and once again I image using: img rp 10.x.x.x win7baseimage
Once the machine completes its install, I reboot the machine and am now left with a non-functional boot sector. (i.e. no bootable device found). I've tried recovering the MBR having used this method against another laptop that was imaged using AHCI:
dd if=/dev/sda of=mbr7.img bs=446 count=1 to create the file and then dd if=/mbr.bin of=/dev/sda bs=446 count =1 which is supposed to overwrite the MBR and potentially have it working.
This will result in a non-bootable drive and I've yet to figure out how to make it boot, other than running a manual Windows 7 installation using the install disc and manually building my workstation. Once I do this, I can image again. So I know it has something to do with the way the MBR works.
Scenario 2:
BIOS settings were set to ATA and had Windows XP as the current image. I immediately change the controller settings to AHCI, I then image the hard drive using the previous command to image my HDD and it works fine. I re-image a second time to test, it still works great.
Has anyone else run into this scenario and if so, what are you recommended steps? I have a feeling as if my MBR is all messed up, but I'm unsure how to fix the situation.
Any help would be greatly appreciated.
Thank you