Uploading windows 8.1 to Fog 1.2.0



  • I seem a bit stuck at the minute with uploading my latest windows 8.1 image. every time i run the upload process then i get the attached image, this is after multiple reboots/shut-downs and also after running chkdsk /f any ideas would be a huge help.

    Things i have tried.
    Rebuilding the OS
    Trying different HDD
    Running chkdisk

    fog.jpg


  • Moderator

    @flat4 said:

    Im Having the same problem, i can deploy an windows 8.1 image but for some reason i cannot upload it. I get the same screen as the OP. Any progress on this?

    Edit i fix my issue with a little google, someone else posted to use Part Magic and try to open the drive in the file viewer. When this happens it will tell you to run a command to remove the hibernated file. I did and boom fog is now uploading the image.

    “Removing hibernate file and page file” feature is available since FOG 0.12



  • Im Having the same problem, i can deploy an windows 8.1 image but for some reason i cannot upload it. I get the same screen as the OP. Any progress on this?

    Edit i fix my issue with a little google, someone else posted to use Part Magic and try to open the drive in the file viewer. When this happens it will tell you to run a command to remove the hibernated file. I did and boom fog is now uploading the image.


  • Moderator

    @Dcopple said:

    Sorry new here, So after installing fog 1.2 i’d update the trunk and it should let me image win 8/8.1 ? Would this image it in UEFI mode or legacy only ?

    That depends on your PXE boot / DHCP configuration.

    It’s simple.

    Undionly.kpxe and undionly.kkpxe and pretty much ANY file that does NOT have an .efi extension is used for BIOS.

    ANY file WITH an .efi extension is used for UEFI.

    There are two versions of the .efi files, the ones in /tftpboot are 64 bit. The ones in the i386 folder ( /tftpboot/i386 ) are 32 bit.

    And, the boot files have nothing to do with your original error. It’s that FOG is treating this like… whatever image type you have it set to… I am assuming Win7. Windows 7 image handling obviously does not work for windows 8.1.

    There is support written for Windows 8.1 in FOG trunk. You can either update to Trunk to get that functionality, or wait for FOG 1.3.0 to be released.



  • Sorry new here, So after installing fog 1.2 i’d update the trunk and it should let me image win 8/8.1 ? Would this image it in UEFI mode or legacy only ?



  • @need2 i have come in to test this is working and yet again it is giving me the same error in the original post. that was while i was running version 3493 of the trunk.



  • @Wayne-Workman

    @Wayne-Workman said:

    @need2 said:

    I’m fairly certain there was a bug with 8/8.1 in FOG 1.2.0. It is working fine in the latest SVN, but I suggest caution if you use FOG in production, since the SVN is the development branch. Bugs happen.

    For using the latest FOG Trunk versions,

    It’d say it’s paramount to have FOG virtualized and maintain snapshots.

    Hyper-V makes upgrading to trunk really easy… Don’t like the new version? Apply the last snapshot. Done.

    Exactly what i have done, Unfortunately i didn’t have time to test to see if it fixed my issue. Monday morning will be when i am next able to test.


  • Testers

    I am Deploying Windows 8.1 with no issues except my server is 1.2 and my storage nodes are .32
    If i upgrade storage nodes to 1.2 the server will not see them


  • Moderator

    @need2 said:

    I’m fairly certain there was a bug with 8/8.1 in FOG 1.2.0. It is working fine in the latest SVN, but I suggest caution if you use FOG in production, since the SVN is the development branch. Bugs happen.

    For using the latest FOG Trunk versions,

    It’d say it’s paramount to have FOG virtualized and maintain snapshots.

    Hyper-V makes upgrading to trunk really easy… Don’t like the new version? Apply the last snapshot. Done.


  • Senior Developer



  • @need2 do you have a recommended procedure for upgrading to the trunk?

    Thanks


  • Moderator

    I know 1.3.0 is coming around the corner, but an actual ETA, that I do not know. If you can, I would suggest making a backup of your FOG server, then updating to the latest SVN. Then test if everything works well for you. I have been using the SVN for quite a while and haven’t had any major issues, but there are always things that could go wrong during development.



  • @need2 is there a ETA for when the fix will be in the stable version of fog? my server is practically useless without been able to deploy windows 8 due to the new licensing system forced by Microsoft.


  • Moderator

    I’m fairly certain there was a bug with 8/8.1 in FOG 1.2.0. It is working fine in the latest SVN, but I suggest caution if you use FOG in production, since the SVN is the development branch. Bugs happen.



  • @need2 It’s single image realizable


  • Moderator

    Which type of imaging options did you select?


Log in to reply
 

449
Online

38940
Users

10697
Topics

101495
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.