W
warden976
Guest
Hi All,
We currently have a custom Windows 7 build that we use WinPE and ImageX to deploy our custom wim to PC. This all works fine, until we try to re-apply the wim without first wiping the partitions, or "moving" the current Windows folder out of the way. If we re-apply the wim the PC boots up but just sits at "starting services" constantly and doesn't boot. We've left the machine for HOURS too, so it's not just taking a little longer.
For testing we've also tried this with unmodified "straight of the install DVD" windows 7 enterprise and professional install.wim's (re-installing the same version, not alternating) and get the same result, (ie the PC just sitting at "starting services").
If we first rename the Windows folder to Windows.old it goes straight on and boots up, but ImageX pumps out errors while re-applying the image.
we're using diskpart to set the windows target volume to C:\, and then using imagex /apply [pathtowim] 1 c:, followed by bcdboot c:\windows /s s:. This works on a formatted volume or a volume with the previous Windows folder moved out of the way.
This is on physical and virtual machines so we're thinking it can't be drivers (also as build works the first time).
We're also rebuilding straight away, so WSUS not had chance to patch the machine.
Is this possible to re-apply using imagex? If so, what are we missing?
Thanks
Continue reading...
We currently have a custom Windows 7 build that we use WinPE and ImageX to deploy our custom wim to PC. This all works fine, until we try to re-apply the wim without first wiping the partitions, or "moving" the current Windows folder out of the way. If we re-apply the wim the PC boots up but just sits at "starting services" constantly and doesn't boot. We've left the machine for HOURS too, so it's not just taking a little longer.
For testing we've also tried this with unmodified "straight of the install DVD" windows 7 enterprise and professional install.wim's (re-installing the same version, not alternating) and get the same result, (ie the PC just sitting at "starting services").
If we first rename the Windows folder to Windows.old it goes straight on and boots up, but ImageX pumps out errors while re-applying the image.
we're using diskpart to set the windows target volume to C:\, and then using imagex /apply [pathtowim] 1 c:, followed by bcdboot c:\windows /s s:. This works on a formatted volume or a volume with the previous Windows folder moved out of the way.
This is on physical and virtual machines so we're thinking it can't be drivers (also as build works the first time).
We're also rebuilding straight away, so WSUS not had chance to patch the machine.
Is this possible to re-apply using imagex? If so, what are we missing?
Thanks
Continue reading...