Does FOG still support Windows XP Imaging?



  • Ive managed to capture & deploy images of Win 10,8.1 & 7. But, after I capture an image of Windows XP(completed as it shows in my FOG server), my Windows XP screen goes blank after it reboots. Initially, I thought it was still trying to boot to the NIC. But, I changed it to HDD back, yet, it still remains blank. Its just a small blinking “_” symbol at the top left corner and nothing more.

    My Windows XP client has a .NET Framework v3.5 & I used FOG Client Legacy set up since I know MSI & FOG installer doesn’t work in Windows XP. I have started the client service, I can receive undionly.kpxe file through TFTP, I can ping to my server. So, Im kinda clueless to whats the issue. Any suggestions?


  • Developer

    @Reuban1219 said in Does FOG still support Windows XP Imaging?:

    Other than Single Disk - Resizable option there is three other choices.
    a) Multiple Partition Image - Single Disk(Not Resizable)
    b)Multiple Partition Image - All Disks(Not Resizable)
    c)Raw Image (Sector BY Sector,DD,Slow)
    Which of these do I choose?

    If you don’t need to deploy the image to a smaller size disk you wanna choose “Multiple Partition Image - Single Disk(Not Resizable)”. Check out the information in the wiki on this: https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images

    Btw, I have an additional question. Is it okay to capture and deploy image without doing sysprep? Or is it a must to do sysprep?

    Sysprep is not needed in general. FOG doesn’t care if you sysprep or not. BUT Windows will need to be syspreped if you capture from one hardware model and deploy to another one being quite different. Good you bring up this point as I have not had that in mind. While I don’t think the hang on the blinking “_” can be caused by deploying to a different hardware as it’s very early in the boot process it’s very likely Windows will give you a blue screen later on in that case.



  • @Sebastian-Roth Other than Single Disk - Resizable option there is three other choices.
    a) Multiple Partition Image - Single Disk(Not Resizable)
    b)Multiple Partition Image - All Disks(Not Resizable)
    c)Raw Image (Sector BY Sector,DD,Slow)

    Which of these do I choose?
    Btw, I have an additional question. Is it okay to capture and deploy image without doing sysprep? Or is it a must to do sysprep?


  • Developer

    @Reuban1219 said:

    I changed it to HDD back, yet, it still remains blank. Its just a small blinking “_” symbol at the top left corner and nothing more.

    I would expect this to happen if something goes wrong with a resizable image. Can you set the image to be non-resizable, re-capture and deploy again?


Log in to reply
 

246
Online

7.0k
Users

14.2k
Topics

134.3k
Posts