Issues with updating / re-deploying images
I am stuck and I need some guidance/direction. I've read through countless posts, articles, and support forums that I feel I need to reach out in this format to see if I am the only one having this issue.
For starters, I am somewhat of a rookie at this process. Most of what I've learned is self taught and from the jump start training program. Our environment is 61 Dell E5400 Laptops (identical), 30 HP Touchsmarts (identical), and a Kace K2000 device. The hardware I am imaging is our road equipment. The hardware gets imaged, shipped out to events, returns to the office, gets imaged again, gets shipped out to events. It is possible that this hardware gets imaged 1 -2 times per month. We were sold on the K2000 on for the purpose of having the computers being booted to the network and have the image applied for the next event (ie anyone could plug in a laptop, turn it on and the K2000 would do the rest).
Since my issue is the same for both the Dell and HP hardware, I will continue using the laptops as my example.
Here is where I am stuck - updating the current image and re-deploying the new updated image.
Here is what I have been doing - using a typical naming convention I have two images captured one called the master (E5400 v2 Master) - this is a Non-syspreped image. I also have another imager called E5400 v2 (SYSPREP) - this is the image that is pushed out to my road laptops.
I have one laptop designated as a Golden Image - I've deployed the E5400 v2 (MASTER) to this machine and started applying all Windows Updates (including SP1), updated driver hardware (as needed), added some additional programs, etc. I then captured this image as E5400 v3 (MASTER).
After the K2000 successfully captures the image, I go through the sysprep process and shutdown. Upon reboot, I capture the image to the K2000 as E5400 v3 (SYSPREP). I then deploy the sysprep image to another machine. Upon the startup process I receive an error "Windows setup could not configure windows to run on this computer's hardware." It then prompts for a reboot and that following error is "Windows could not complete the installation. To install Windows on this computer, restart the installation."
As I stated, I've chased down nurmerous threads and posts all with the same results. I've escalated my issue to Dell Kace and I am currently waiting for a response. I am willing to provide any additional details that someone thinks is relevant to this issue. Based on what I've read this is a common issue but most of the posts have not been related to the K2000 appliance.
Anxiously awaiting any suggestions.
Dave
For starters, I am somewhat of a rookie at this process. Most of what I've learned is self taught and from the jump start training program. Our environment is 61 Dell E5400 Laptops (identical), 30 HP Touchsmarts (identical), and a Kace K2000 device. The hardware I am imaging is our road equipment. The hardware gets imaged, shipped out to events, returns to the office, gets imaged again, gets shipped out to events. It is possible that this hardware gets imaged 1 -2 times per month. We were sold on the K2000 on for the purpose of having the computers being booted to the network and have the image applied for the next event (ie anyone could plug in a laptop, turn it on and the K2000 would do the rest).
Since my issue is the same for both the Dell and HP hardware, I will continue using the laptops as my example.
Here is where I am stuck - updating the current image and re-deploying the new updated image.
Here is what I have been doing - using a typical naming convention I have two images captured one called the master (E5400 v2 Master) - this is a Non-syspreped image. I also have another imager called E5400 v2 (SYSPREP) - this is the image that is pushed out to my road laptops.
I have one laptop designated as a Golden Image - I've deployed the E5400 v2 (MASTER) to this machine and started applying all Windows Updates (including SP1), updated driver hardware (as needed), added some additional programs, etc. I then captured this image as E5400 v3 (MASTER).
After the K2000 successfully captures the image, I go through the sysprep process and shutdown. Upon reboot, I capture the image to the K2000 as E5400 v3 (SYSPREP). I then deploy the sysprep image to another machine. Upon the startup process I receive an error "Windows setup could not configure windows to run on this computer's hardware." It then prompts for a reboot and that following error is "Windows could not complete the installation. To install Windows on this computer, restart the installation."
As I stated, I've chased down nurmerous threads and posts all with the same results. I've escalated my issue to Dell Kace and I am currently waiting for a response. I am willing to provide any additional details that someone thinks is relevant to this issue. Based on what I've read this is a common issue but most of the posts have not been related to the K2000 appliance.
Anxiously awaiting any suggestions.
Dave
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
warmep
12 years ago
Is there a difference of SATA operation modes on the source system and deployment target? e.g. Source is using ATA mode and the target is on AHCI or RAID?
Were you able to deploy the v2 sysprepped images without an issue? If so, what changed since you've started doing v3?
Were you able to deploy the v2 sysprepped images without an issue? If so, what changed since you've started doing v3?
Posted by:
dbradfield2
12 years ago
That issue came up when trying to deploy the updated image to another device.
Deployed v2 (NO sysprep) to Golden Image - Captured image to the K2000 (v3 (NO Sysprep).
Deployed v3 (NO sysprep) to another laptop - received error. Noticed that Golden Image was ATA and target machine was ACHI.
Side note: as far as I know, we have never changed these settings from the factory - not sure how/why this got changed.
Read an article to change back from ATA to ACHI using registry update - captured new image (v3a (NO sysprep)).
Verified BIOS settings on both machines as ACHI. Still getting the same results. I am trying to go back through my notes to determine if I was ever told to switch to ATA - based on some posts I've read it appears ATA is better for my scenario but don't want to complicate my life. I am going to deploy the v2 (SYSPREP) to a machine and see if the SATA operation remains the same. Unfortunately, during my JumpStart training the initial image capture failed and I was kicked over to Kace support so I am missing what happened to fix any issues.
I have a current support case open with Kace but so far I haven't been given a clear reason why stuff is failing. I am trying to go back to where I know things worked - which is why I am starting at the v2 (No SYSPREP) since we are successfully deploying V2 (SYSPREP) to our machines. The changing of the SATA mode on my golden image is a mystery and I am open to suggestions to rectify that mystery as well.
Deployed v2 (NO sysprep) to Golden Image - Captured image to the K2000 (v3 (NO Sysprep).
Deployed v3 (NO sysprep) to another laptop - received error. Noticed that Golden Image was ATA and target machine was ACHI.
Side note: as far as I know, we have never changed these settings from the factory - not sure how/why this got changed.
Read an article to change back from ATA to ACHI using registry update - captured new image (v3a (NO sysprep)).
Verified BIOS settings on both machines as ACHI. Still getting the same results. I am trying to go back through my notes to determine if I was ever told to switch to ATA - based on some posts I've read it appears ATA is better for my scenario but don't want to complicate my life. I am going to deploy the v2 (SYSPREP) to a machine and see if the SATA operation remains the same. Unfortunately, during my JumpStart training the initial image capture failed and I was kicked over to Kace support so I am missing what happened to fix any issues.
I have a current support case open with Kace but so far I haven't been given a clear reason why stuff is failing. I am trying to go back to where I know things worked - which is why I am starting at the v2 (No SYSPREP) since we are successfully deploying V2 (SYSPREP) to our machines. The changing of the SATA mode on my golden image is a mystery and I am open to suggestions to rectify that mystery as well.
Comments:
-
@ dradfield2 - did you find a solution for this problem? We are experiencing the same issue. We built the image, ran sysprep using the sysprep.bat and sysprep creator we acquired from Kace. We were then able to successfully capture the image. We also successfully deployed the image to an identical Dell PC. However, when we powered the PC back on, we recieved the same message you did, "Windows setup could not configure windows to run on this computer's hardware." It then prompts for a reboot and that following error is "Windows could not complete the installation. To install Windows on this computer, restart the installation."
Any thoughts? - beedjones 12 years ago
Posted by:
dbradfield2
12 years ago
Here is an update on my hardware.
Deployed v2 (SYSPREP) to another machine - imaged and applied all post install tasks without fail. Restarted Windows into BIOS and confirmed SATA operation was AHCI.
Deployed v2 (NO sysprep) to Golden Image - would not boot - BSOD - restarted into BIOS and confirmed SATA operation was AHCI. Changed to ATA applied settings and rebooted.
I am not sure how or why this happened. Going back through my notes I cannot see anything indicating the SATA mode was changed.
I guess I need a solid recommendation of how to move forward. It appears that even trying to change another laptop to ATA mode will not allow the image to boot. Could this be in the unattend file?
Deployed v2 (SYSPREP) to another machine - imaged and applied all post install tasks without fail. Restarted Windows into BIOS and confirmed SATA operation was AHCI.
Deployed v2 (NO sysprep) to Golden Image - would not boot - BSOD - restarted into BIOS and confirmed SATA operation was AHCI. Changed to ATA applied settings and rebooted.
I am not sure how or why this happened. Going back through my notes I cannot see anything indicating the SATA mode was changed.
I guess I need a solid recommendation of how to move forward. It appears that even trying to change another laptop to ATA mode will not allow the image to boot. Could this be in the unattend file?
Posted by:
warmep
12 years ago
I would compare your v2 unattend with the one you're using now; perhaps there is a difference, maybe something like persistalldeviceinstalls?
It appears that it may be a storage driver issue, have you looked at using the Driver Feed Workaround to install drivers?
It appears that it may be a storage driver issue, have you looked at using the Driver Feed Workaround to install drivers?
Posted by:
dbradfield2
12 years ago
Persistalldriverinstalls is most certainly included in both of my unattend files - that was one of my earliest discoveries into this process. I have very specific drivers that I needed to install for my image.
I am currently looking into the SATA settings. It appears that they changed for my golden image. I have 61 machines - 1 being the golden image. I can pull any of the 60 and the SATA settings would be set to AHCI. The golden image, for some reason, in the non-sysprep form is ATA. I cannot figure out when or why this was changed. Would there be any reason that this would be changed or I would have been instructed to change it?
I am currently looking into the SATA settings. It appears that they changed for my golden image. I have 61 machines - 1 being the golden image. I can pull any of the 60 and the SATA settings would be set to AHCI. The golden image, for some reason, in the non-sysprep form is ATA. I cannot figure out when or why this was changed. Would there be any reason that this would be changed or I would have been instructed to change it?
Posted by:
tpr
11 years ago
I know this thread is pretty old, but in trying to understand the process for updating an image, I wondered about this from the OP:
"I have one laptop designated as a Golden Image - I've deployed the E5400 v2 (MASTER) to this machine and started applying all Windows Updates (including SP1), updated driver hardware (as needed), added some additional programs, etc. I then captured this image as E5400 v3 (MASTER).
After the K2000 successfully captures the image, I go through the sysprep process and shutdown. Upon reboot, I capture the image to the K2000 as E5400 v3 (SYSPREP). "
My question: after the original image is deployed and updated on the target machine, shouldn't it be sysprepped again BEFORE capturing it as a new image? After he deploys the original sysprepped image and runs through the typical post-deploy process, new UIDs have been assigned and the computer is no longer seen as sysprepped, correct?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.