This is how I've deployed Windows 8.1 with Fog 0.32
-
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.
-
nothing is up with windows 8.1, i’ve deployed hundreds of them.
did you try booting up with them disconnected from the network? did you try different exit types for the pxe menu? -
[quote=“Tom Elliott, post: 40177, member: 7271”]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.[/quote]
- When you said the image type did you mean Part-Image and Part-clone?
- The exit type, not sure what you mean by that, a little more detail.
- As fog GPT or MBR, those are not an option during the install, like a said before, the are Lenovo’s. So that part I can’t help you with.
- Start an upload of a good system, I already have that, other wise I couldn’t push what I have right now, but the Debug task sounds interesting. Would like some more detail on that, please.
- Fixparts on system, not sure what you mean by this, and again more detail, thank you.
-
[quote=“Thomas Rucker, post: 40178, member: 1970”]1. When you said the image type did you mean Part-Image and Part-clone?
2. The exit type, not sure what you mean by that, a little more detail.
3. As fog GPT or MBR, those are not an option during the install, like a said before, the are Lenovo’s. So that part I can’t help you with.
4. Start an upload of a good system, I already have that, other wise I couldn’t push what I have right now, but the Debug task sounds interesting. Would like some more detail on that, please.
5. Fixparts on system, not sure what you mean by this, and again more detail, thank you.[/quote]I would like to say though Part-Clone is much faster then Part-image.
-
[quote=“Thomas Rucker, post: 40178, member: 1970”]1. When you said the image type did you mean Part-Image and Part-clone?
2. The exit type, not sure what you mean by that, a little more detail.
3. As fog GPT or MBR, those are not an option during the install, like a said before, the are Lenovo’s. So that part I can’t help you with.
4. Start an upload of a good system, I already have that, other wise I couldn’t push what I have right now, but the Debug task sounds interesting. Would like some more detail on that, please.
5. Fixparts on system, not sure what you mean by this, and again more detail, thank you.[/quote]- no
- it’s how the pxe boot environment hands off boot to the next device, it’s configurable in the settings page
- he’s talking about the boot sector. if there’s any trace of a GPT boot configuration, even if it’s not what is currently is being used, it needs to be cleaned off.
- and 5. are the same thing, he’s telling you a single thing to do. boot into a debug task, run “fixparts” this is for point 3.
-
[B][SIZE=18px]Tom Elliott Could you and I finish this conversation.[/SIZE][/B]
[SIZE=4][B][COLOR=#ffffff][SIZE=18px][COLOR=#141414]I was asking for details, and got general information.[/COLOR][/SIZE][/COLOR][/B][/SIZE]
-
I can’t spell everything out.
I’ll try my best.
The upload-debug is it’s own option. So, after you’ve ensured the image is “ready”, and are about to choose to upload it, set it for the setting you want: (e.g. Multipart non-resize, Resize)
Create it as upload debug by going to Host Management-><list/search relevant host>-><relevant host edit>->basic tasks->advanced->Upload-Debug
Image format is what deals with Partclone/Partimage, as you’re uploading it will always be partclone so this does not matter.
Exit type is done by FOG Configuration->FOG Settings->FOG Boot Settings->FOG_EXIT_TYPE and select either exit, sanboot, or grub. (I’m not thinking this the way you’re describing the issue though so it’s safe, for now to leave it alone)
GPT/MBR doesn’t mean much in the Windows world. It just doesn’t care. And my guess is lenovo, while nice enough to reset the image as a legacy model, probably didn’t properly destroy all data on the disks before putting the OS back on them. This is normal because most of us just reimage the systems anyway. However, I’m not smart enough…yet… to detect if the image is meant to be mbr, or gpt. Because of this, my guess is gpt was left on the disk. When fog created the “backup” mbr of the disk, it formatted it in GPT format. That “master” system works fine but all other deployed systems (windows 7/8/xp, or otherwise) would do the “stop at cursor” because they’re expecting data in the first 512 bytes of the hdd (the mbr data). In GPT this doesn’t exist and because “legacy” bios is looking for data there, and nothing exists, the system just stops because there’s nothing to do. To fix this, as again I suck or something, boot into upload-debug. Fixparts is a program that’s in the fog init file. SO when you get to debug, you run fixparts /dev/sda on the command line presented. I don’t know what it will tell you, I just know it “might” help.
Then once the fixparts is done, you can run the command “fog” and hit enter a bunch of times. Then you should be good to go.
For the Windows 8/8.1 issue. I don’t know what else to try. I know it works, but I don’t know all the case scenarios. If RAW works, then maybe, when you have more time, try sitting down to bash it out. If it’s something I’ve done, let us know and I can try to correct it.
-
I answered you on the other forum, about the 6 partitions. As for trying the above, maybe later, I have new servers coming in, and more people are being hired. So, the move 1.2 will have to be delayed, thanks for your help.
-
[quote=“Thomas Rucker, post: 40129, member: 1970”]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.[/quote]
I fail to understand how you “tried” all of the above and:
[quote=“Thomas Rucker, post: 40138, member: 1970”]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.[/quote]
Yet you end yup with 6 partitions on your disks.
And you’re IT Support? So you say, nah I won’t follow any of the actual instructions that are presented, but I’ll do my OWN thing. Then I’ll complain that My OWN thing isn’t working?
I’m done answering your questions. Sorry it has to be like this, but after reviewing of the information it appears that you lack the ability to follow simple instruction and just feel things should work the way you want them to because you want them to work that way. You’ll blame your problems as a “limitation of FOG” which seems rather selfish in the firstplace because you obviously have no understanding of what fog actually is.
-
WOW
What’s wrong with you.
Fist, when I reload the Lenovo’s with the system disks that come with it, it creates these partitions!
Second, when I found in a forum, and you stated that FOG doesn’t like more that three partitions, I queried you on that detail.
Third, I’m not doing things the way I want to, I’m using the tools that are given to me by Lenovo.
Fourth, have you worked with any Lenovo’s ? Have you wiped one clean, and reload it using it’s systems disk, there is four on them.
Fifth, I trying to keep and open dialog with you, to work through this, didn’t expect you to throw your hands in the air, then start insulting me.If you and others state your here to help, what’s with the insults.
I’ve been an LAN Administrator for 15 years, started using FOG four years ago, and have pushed it to other offices, and applauded FOG over Ghost.
At what point have I insulated YOU!
-
[quote=“Tom Elliott, post: 40201, member: 7271”]You’ll blame your problems as a “limitation of FOG” which seems rather selfish in the firstplace because you obviously have no understanding of what fog actually is.[/quote]
:oops: Love you
-
[quote=“Thomas Rucker, post: 40202, member: 1970”]
I’ve been an LAN Administrator for 15 years, started using FOG four years ago, and have pushed it to other offices, and applauded FOG over Ghost.[/quote]What a LAN Administrator don’t understand in Tom instruction ?
[quote=“Tom Elliott”]
SO when you get to debug, you run fixparts /dev/sda on the command line presented
[/quote] -
NO, I quoting you from another forum, and it was not insult, it was a question.
Let me try again. The Lenovo’s, when using their systems disks, creates six partitions, is this why that RAW image format only works.
What can I do to get around the six partitions?
Do you think that the debug is going to work? I’m getting ready to try the process, with the instructions you gave me.
Thank you for you help.
-
What I’m confused about,
How are there 6 partitions being created on a disk?
Are you 100% sure this disk is being setup in MBR [B]AND[/B] using extended/logical partitions over GPT? I ask because the “limitation” that I reference in the other thread is specific to Resizable images. It should not have any impact on Multipart Single/All disk setup, and as you already know, does not have any impact on RAW.
I’m not trying to Insult you or state that you insulted me. However, as we keep trying to get and give information, it feels like you’re just looking for the quick answer. Because of this, it feels to me like you’re just doing whatever willy nilly and then coming back saying it’s not working. If you actually read the information, it should give what I like the call the “aha” or “epiphany” moment. Installing the system from scratch is the best bet, but obviously if your system disks are adding these extra things that we (assume) are causing most of the problems right, then maybe look into using a different disk.
Are these systems you’re working with enterprise or consumer grade? If so, can lenovo provide you with an enterprise style install disc as this should remove all the “bloatware” and allow you to default install your windows systems. I haven’t played too much on installing windows 8/8.1 and even less with installing it on and MBR setup. The first thing that pops into my mind is GPT though. Mostly because I’ve been working and helping people for over a year here on the forums.
There is little you can do to insult me. Do I get frustrated, sure, I am human. When I read things and things really start to fail to add up, I will let you know. I’m not throwing my hands up, I just don’t know how to help out any further. If you’re following all the instructions, then you should be able to use Multipart imaging. If you upgrade to 1.2.0, which Junkhacker was trying to request you to do (he’s a developer too) You would also be able to, when things are correctly setup, operate with Windows 8 and resizeable images.
Sure, you had the issues with Windows 7. That’s probably a similar issue to my thoughts on what’s happening with your Windows 8 systems, but you keep throwing excuses rather than attempting things being suggested. Why should we continue to help?
-
[quote=“Tom Elliott, post: 40201, member: 7271”]I fail to understand how you “tried” all of the above and:
Yet you end yup with 6 partitions on your disks.
And you’re IT Support? So you say, nah I won’t follow any of the actual instructions that are presented, but I’ll do my OWN thing. Then I’ll complain that My OWN thing isn’t working?
I’m done answering your questions. Sorry it has to be like this, but after reviewing of the information it appears that you lack the ability to follow simple instruction and just feel things should work the way you want them to because you want them to work that way. You’ll blame your problems as a “limitation of FOG” which seems rather selfish in the firstplace because you obviously have no understanding of what fog actually is.[/quote]
I just wiped a Lenovo 10Ay, to see if I get the same thing, I did. I uploaded it to a Test image. So, I’m showing you what I see in FOG, and what I see when it does the download.
[IMG]http://ruckersystems.com/avatar/windows-8.1.jpg[/IMG]
As you can see there are six partitions, but what is weird in Windows disk management, it only shows five.
This looks like it is using mbr, but if I’m wrong, correct me.I used a different set up disk, got the same result.
Is this limited to Lenovo?
-
It seems like it is to me.
What is weird (and maybe you can explain it) is the Windows8 file sitting there.
The d1p# files look great, although things don’t work, but were/what is this Windows8 file?
-
I wiped clean again, but this time I used diskpart, and remove the recovery partitions.
Then I rebooted the system, it came up just fine.
So, I uploaded as multiple partition single disk, PartClone.
Wipe again, and down loaded, it gave me the blinking cursor, no big deal, just ran Windows 8 repair.
It could not fix it, no big deal, I’ll just do a recovery on it. Still had the blinking cursor, no big deal ran MBR fixer, WTF.
Now it says no operating system. Boot up with WindowsPE, all of the files are there, no big deal.
Boot to Windows 8 and did PC refresh, yes move the partitions, WTF, it still says no operating system.
I’m going to reload again, us diskpart, remove the recovery partition, upload as RAW image, them download again.
-
I wiped it clean again, and used a generic Windows 8.1 disk, didn’t use the restored disks.
Loaded the OS, it only had two partitions, just like Windows 7.
Uploaded, set the test image to multiple partitoin image single disk, partclone.
Wiped it clean again.
Did a download, it worked!?
So, the issue is what ever Lenovo is doing to the partitions, during the restore, will not work with FOG.
