This post is more than 5 years old
2 Posts
0
140065
October 8th, 2015 09:00
Image Fails after about 1 week to install
We have an issue where our Windows 8.1 image fails to install after about 1 week. We can cut an image with ImageAssist and it works fine. We install and test it on multiple models without any issues. After about 1 week it start to fail with either blue screen, black screens, or is totally unresponsive after the image is applied and system is restarted.
Note:
We are able to create a stable image that lasts beyond a week but we don't know why some work and others fail. This is very frustrating and adds an additional week to our process which we don't like.
Has anyone seen this before or does anyone have a solution?
Image Desktop
Windows 8.1 Fully Patched
VMware Workstation 11 & 12
UEFI Enabled for the VM
Dell 9020
Dual SSD in RAID 0
32GB RAM
Dell Image Assist 4.0.0.8 (We have used previous versions with the same issue)
DELL-Tyler M
Moderator
•
342 Posts
0
October 9th, 2015 10:00
KentImager - thank you for the information.
We have seen an instance reported of the symptom you're experiencing. It was resolved by the resolution mentioned in this post "Issues restoring 64-bit images". If your W8.1 image is 64-bit, and your USB drive was not created using the /secureboot switch, that may be the problem.
As an aside, in our next release of ImageAssist - the USB drive creation process will no longer produce a 32-bit version by default, rather it will auto-create the matching version of the OS detected at time of production.
Thank you,
Tyler
HamiltonImager
3 Posts
0
October 22nd, 2015 09:00
Hello Tyler,
We are using WDS and experiencing the same problem, possibly they are linked?
Thanks!
HamiltonImager
3 Posts
0
October 22nd, 2015 09:00
Hello KentImager,
We are also experiencing the same problem but using WDS as our deployment utility. The only solution found is that setting back the BIOS clock time to the upload date allows for the image to deploy successfully. I read through Tyler's response but that does not seem to be associated with the way we are installing or deploying images.
Thanks!
DELL-Tyler M
Moderator
•
342 Posts
0
October 23rd, 2015 08:00
Hi HamiltonImager -
Is your deployment boot WIM the same architecture as the OS you're deploying? If not, that may be the cause. You mentioned "setting back the BIOS clock time to the upload date". What is the upload date you're referring to? Can you elaborate?
KentImager - did you happen to recreate your ImageAssist USB key with the /secureboot switch and retest this?
Tyler
HamiltonImager
3 Posts
0
October 23rd, 2015 09:00
Hello Tyler,
The deployment boot WIM is not the same architecture as the OS, this could be it. I will report back after the change is made. The BIOS clock work-around is as follows: After a week imaging fails, by setting back the BIOS clock to match the date in which the .WIM was sysprepped and uploaded into WDS seems to bypass the issue allowing for a successful deployment.
Thanks!
KentImager
2 Posts
0
November 5th, 2015 09:00
Thank you Tyler this worked for us. At first we just went the route of splitting the WIM files but after a little playing around by one of our desktop persons we found out we could use the /secureboot created USB files on a NTFS based bootable USB which was our desired approach since we could have multiple WIM's on one drive.
Here is what we did which could come in handy for other people.
Create a UEFI Bootable USB with the Dell Tool
C:\Program Files\Dell\ImageAssit\USB_Drive_Creator.exe /secureboot
Copied the files from the UEFI USB to a NTFS Bootable USB.
Put our WIM files on this USB along with our driver CAB's. We did not have to split the WIM's.
To image a system we would switch to legacy boot so that we could boot from the NTFS USB
We image the system
When we reboot we switch back to UEFI with SecureBoot enabled.
This is working like a charm for us. Worst case we could switch back to splitting the WIM files but we like having a large bootable USB (256GB Samsung S1 USB) with multiple images and all of our tools.
Take care,
DELL-Tyler M
Moderator
•
342 Posts
0
December 14th, 2015 12:00
Please note the /secureboot switch for USB_Drive_Creator.exe has been depreciated in the latest 5.0.1.1 release of ImageAssist. The USB creator tool will now auto-create the drive based off the OS architecture it’s run from. e.g. if 32-bit, it will create a 32-bit PE. if 64-bit, it will create 64-bit PE.