This is how I've deployed Windows 8.1 with Fog 0.32
-
That’s great. Do you know any resources or where I might find directions for creating an xml unattended file?
-
I have a recent post about sysprepping windows 7/8 that includes a download of my setupcomplete.cmd and unattend.xml files. I also include links to the main articles that helped me create the files so I know which options to set to avoid the welcome screen or anything that might cause the installed to pause and ask a question.
You’ll need Windows AIK and the install files for your version of windows so you can pull out the catalog file.
-
Thanks, this will help out greatly!!!
-
So im trying to do this process now. When you speak of repair are you talking of startup repair or like bootrec /fixmbr /fixboot? Neither worked
Receive error: A disk read error occurred
Update: Updated Image to be a Multiple Partition Not Resizable. This allowed me to push out the image with no issues booted first try. Is the issue laying with Single Partition (Resizable)? Is there something i can do to correct it as Single Partition Resizable is the preferred method as it would save space and elevate extra steps on my part.
Thanks in advance for the help and feedback
-
MPSD images are still compressed when stored on the FOG server. I have NEVER had luck with resizable and most times I have tried it (on FOG 0.32 at least) it has hosed my image up with a problem during the resize and I had to start all over. A windows machine that takes 40GB on a disk will probably take about 15GB after it’s compressed into the /images folder.
-
Typically speaking, to use Resizable with Windows 7, and I imagine 8, you would need to have sysprepped the system. This is because, during the sysprep process, it generalizes the hard-drive. If it’s not sysprepped, windows believes the drive is exactly whatever device it was when it was initially installed. If there’s any variance (size drive space) it borks the entire process. There is a way to set bcd so this isn’t the case, but I haven’t had any luck finding any good documentation on it so I can automate it into the FOG system.
-
Thank you for the responses. I have always sysprep’d all my images as it allows me to push it to a different model computer if needed. I tested pulling a Windows 8.1 image using the ‘Multiple Partition (Single Disk)’ option and was able to deploy the image and boot fine first try with no issues. Just wanted to note that in case future users encounter similar issues.
-
I’m using FOG 1.1.2, I’ve tried all of the above, nothing works. When I got the “winload.exe failure”. I booted off a 8.1 disk/usb and ran the repair, that failed.
So, I upload the image as RAW Disk, very slow, but it works.
-
you’re using fog 1.1.2 and you followed a guide for 0.32? the software was almost completely rewritten between the two.
-
[quote=“Junkhacker, post: 40134, member: 21583”]you’re using fog 1.1.2 and you followed a guide for 0.32? the software was almost completely rewritten between the two.[/quote]
I’ve used several processes from different forums. The process here was the last that I tried.
I’ve used all combinations from many forums, none worked.
With this newer version, there should not be and issue, but Windows 8.1 is a beast.
-
you don’t have to do anything special to prepare a windows 8/8.1/10 image with the latest versions of fog. sysprep isn’t even needed. a normal default install and upload just works.
-
And just to clear up any confusion. FOG does not require Sysprep.
However Windows heavily recommends a sysprep.
-
[quote=“Junkhacker, post: 40149, member: 21583”]you don’t have to do anything special to prepare a windows 8/8.1/10 image with the latest versions of fog. sysprep isn’t even needed. a normal default install and upload just works.[/quote]
No it doesn’t, I’ve tried that first, I’ve tried from other forums, that didn’t work, so I did a RAW disk upload, that worked.
Just the normal upload, then do a download to a machine would give me the winload.exe failure.
I would boot up to a USB Windows 8.1 drive and run a repair, that would fail.
I saw on forum using the RAW disk format, and that worked.
-
update to 1.2.0
-
[quote=“Junkhacker, post: 40164, member: 21583”]update to 1.2.0[/quote]
All ready tried that, had to move back down, because of Windows 7.
-
what about windows 7? 1.2 works fine with windows 7
-
[quote=“Junkhacker, post: 40168, member: 21583”]what about windows 7? 1.2 works fine with windows 7[/quote]
Nope, when i did the upgrade, my Windows 7 would net even boot, just a black screen with a cursor. I ran windows 7 repair, failed, ran MBR fixer, still a black screen with a cursor.
I didn’t time to mess with that version, so I move back down. I had to image 30 Windows 7 machine for new hires.
The Windows 8.1 is not being push, but I want to be ready.
The 1.1.2 is working great, my Windows XP, 2003 server, 2008 R2 server, and Windows 7 work, needs to be working, we are expanding again.
If there is no other solution, I just stay with the RAW image format, at least it works.
-
When you installed Windows 8, did you install with UEFI? If you installed with UEFI, before you uploaded (using the other than RAW methods), did you disable secure boot?
Did you try installing through CSM/Legacy BIOS on a Pure MBR system?
Your details are very limiting hence all the “back and forth.”
The black cursor. When did this happen? Was it on the PXE boot itself? When it was actually booting to the system? If so, did you try other Exit types?
-
[quote=“Tom Elliott, post: 40170, member: 7271”]When you installed Windows 8, did you install with UEFI? If you installed with UEFI, before you uploaded (using the other than RAW methods), did you disable secure boot?
Did you try installing through CSM/Legacy BIOS on a Pure MBR system?
Your details are very limiting hence all the “back and forth.”
The black cursor. When did this happen? Was it on the PXE boot itself? When it was actually booting to the system? If so, did you try other Exit types?[/quote]
The BIOS is set to legacy on all of them, the machines came that way, Lenovo 10AY, the secure boot is disable by default.
These machine come with Windows 8, I wipe them clean re-installed Windows, with out all of the crappy software. Run all of the updates, which is the 8.1 update.After the updates, I run CCleaner to clean the machine up, run check disk, to clean up the disk, then defrag. Then I boot to WinPE to remove the System Volume folder and recycle bin, then create my image.
This has always worked for Windows XP, 2003 Server, 2008 R2 server, Windows 7, never had any issues. Until FOG 1.2
The black cursor for the Windows 7, is after I updated to 1.2.
When it finishes imaging the machine, and reboots, I get the black cursor, and it can’t be fixed. I tried different types single disk, multiple partition singles disk, multiple partition image all disks, changed from partimage to partclone, nothing worked.
So, I move back to 1.1.2, I was running out of time pissing with 1.2, I had to get 30 machines imaged for new hires.
The only question I have, what is up with Windows 8.1? That is the only question.
-
First, the image type had no effect on the systems booting. Lots changed between 1.1.2 and 1.2.0. I think this is related to one of two things. 1. maybe it’s related to the exit type, maybe it’s not. But you could give that a shot. 2. It’s most likely related to the hdd’s having GPT, and that also my thoughts of the Windows 8/8.1 that you’re having.
Maybe start an upload of a good system but make it a Debug task. Before running fog, run fixparts on the system. See if this helps.
