Posts made by bc601

Found a work around. Found one old image that works. Thanks for you all help

@george1421 said in BSOD after image with FOG on Optiplex 9010s:

windows just starts

When windows just starts is when the BSOD happens I have tried 3 9010s

@tom-elliott

Also to note I have more then one image on the FOG machine. Every image that I try on the Optiplex 9010 only goes to BSOD.
When I image the Optiplex9020 the image works without a BSOD

@tom-elliott

Thanks I think the image may be corrupted as well. How did it corrupted without any changes is suspicious

@george1421 said in BSOD after image with FOG on Optiplex 9010s:

m

hat version of fog are you using?Running Version 1.4.4
SVN Revision: 6077
What OS are you deploying? win 7
What mode is the target in (uefi or bios/legacy)? bios/legacy
What mode is operating system?bios/legacy
Did you sysprep the system? yes
Is the right drivers installed on the master image yes

PC has been imaging fine until last week

BSOD after image on Optiplex 9010. Happens on every Optiplex 9010 I try and image. Has anyone seen this issue before ?!

What are the proper steps to creating Groups in FOG vie the HOST Tab

@george1421

How do you properly verify if the FOG service is disabled.

@wayne-workman

Yes I did not activate the sysprep application. Once I activated it and recaptured the image. The problem was resolved.

@george1421

Okay found out what the issue was. I did not sysprep the image correctly went back and syspreped the PC used for the image and tried it again. This time it worked after redeploying the image

@george1421

I have no idea were they came from.

So how do I correct the setup error ?

@george1421

Ok it was a success. I now have the log files. I noticed something weird the setup.log file is empty and spelled incorrectly

@george1421

On the last step. Step 10. I received an error message stating the following
CANNOT CREATE REGULAR FILE '/IMAGES/DDACLSSYS.LOG:READ ONLY FILE SYSTEM.
This error repeated for each .log file. I also included the screenshot of the rights to the /images folder.

@george1421

I Received the following error on step 8 : ntfs-3g mount: failed to access mount point /ntfs: no such file or directory

@george1421

What are the instructions for getting to the logs in debug mode from FOG ?

@george1421

Unfortunately there is only one power option for the HDD in this case so I dont have the ability to plug in the second HDD without unplugging the main one

@george1421

@george1421

1: The system drivers for the 7020 are pulled from the FOG server during the image process. I cant get into the system to verify if the drivers successfully went into the drive or not
2: Yes the image was syspreped

I have my images setup in a VM. They have been captured in FOG. The images are all windows 7. I tries to deploy to an Optiplex 7020. And after deploying during startup I received the following error message :

WINDOWS FAILED TO START. A RECENT HARDWARE OR SOFTWARE CHANGE BE THE CAUSE.