Hp pro x2 612 g1 windows 8.1 image issues
-
Sorry, I am new to all of this, coming from the Windows world (don’t judge me). Any more suggestions? Would upgrading to 1.2 help me?
-
[quote=“Tim Brown, post: 40800, member: 23073”]Sorry, I am new to all of this, coming from the Windows world (don’t judge me). Any more suggestions? Would upgrading to 1.2 help me?[/quote]
Hi,
Could you post a screenshot of your error ?
For the version of FoG, it’s sure that a 1.2 or more is better.Regards,
Ch3i. -
It should help but not entirely
If you want pure gpt nonuefi it should work, if you want pure mbr it should work . I don’t have all the answers and haven’t tested every possibility though
-
I’m really thinking this has more to do with the Hardware than anything else. If I leave all of the HP custom system partitions intact, delete only the Windows System partition, I am able to install Windows 8.1 Pro, sysprep and upload all of the partitions to our fog server. If I deploy this sysprepped image to the same computer, all is well. If I deploy this scenario to a different hardware (same but different machine) I get I get the error that terminate called after throwing an instance of ’
To clarify, this error is thrown up during the image deployment process when it gets to the volume that windows was installed on.
If I delete all of the HP images and install windows and sysprep, I get the an error [I][FONT=sans-serif][COLOR=#000000]unable to move /images/dev/macaddress to /images/name-of-image. [/COLOR][/FONT][/I]
I just found something while trying to clarify my issue. It may be because I’m trying to [FONT=sans-serif][COLOR=#000000]trying to image a single as multiple partitions. [/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]Let me change the image settings and I’ll try again and post my results. I already tried changing the directory permissionseven though I did not think this was the issue because I was able to upload other images but this makes sense now. Hopefully this will resolve the issue. [/COLOR][/FONT][FONT=sans-serif][COLOR=#000000][url]http://www.fogproject.org/wiki/index.php/Images_Directory_Permissions[/url][/COLOR][/FONT]
-
I don’t think it’s directly hardware.
Rather you’re using the OEM licensed OS disc, which will only work on the Maker systems?
-
No, I am using a Windows 8.1 pro disk for the imaging. When I tried to upload the image I got a different error from Fog: unable to find partition. I will need to figure out if this is a new problem or just a problem with the partition on that particular machine.
-
At this point, I’m just hoping someone who has been successful with this model or a similar model can chime in and let me know it’s possible and what they are using to make it work. If you google “fog imaging hp pro x2” this is the first search result that pulls up so it looks like we’re either on the bleeding edge or everyone who has been successful hasn’t had the time to post about it yet
-
Ok, so it appears that the GPT partitions will upload to fog 0.32 but it will not allow the windows system to be downloaded to a new computer for re-imaging. Oddly enough, it appears that the other HP volumes (even though the partition itself is GPT) get downloaded to the computer. Another oddity is that the Windows volume can be downloaded to the SAME computer.
When I reformat in MBR and reinstall windows 8.1 pro, sysprep and shutdown, Fog won’t allow me to upload the image and gives me the error copying to folder.
I’ll keep banging away at this and if anyone has any suggestions let me know. I’m going to try some other imaging software and post the results.
-
I don’t know how clear I can make this, so I’ll just try again?
0.32 is NOT compatible with GPT in any way, shape, or form
-
i suspect that what you’re seeing is the result of the gpt being partially recorded, and partially written. the part that isn’t being recorded and isn’t being rewritten already exists on the original computer the image was taken from. this is a bit like having half of a key broken off in a lock. the key will work on the original lock, because the other half is already there, but it won’t work on any new locks that should accept the same key, because it’s only half the key.
-
Thanks Tom. I get it. Yet upgrading to 1.2 will help, but not entirely. I actually did try upgrading and got an error upgrading the database so I reverted to my 0.32 snapshot in an effort to avoid conflating the issue.
Junkhacker-your comment makes sense.
So now the question, when I remove all of the partitions during the Windows install, then allow windows to reformat in MBR I get the copy error I described earlier from FOG?