Imaging Windows 10
-
@dallenqns I don’t know when 1.3.0 will be released yet. I’m hoping to have everything much more stable, though I believe it’s pretty stable right now. Windows 10, however, should work by default even for 1.2.0 out of the box.
-
Just checking in. My company (including myself and the rest of the IT crew) are discussing moving to FOG as our imaging deployment. One of the items of discussion is will it work with Windows 10. I found this question in your forum. Is there an answer for this?
-
@eddiestuder I depends! I uploaded and deployed Win 10 using FOG 1.2.0 and FOG trunk without any issues BUT we have a pretty simple partition layout. MBR with only four primary partitions and using “non-resizable” image type. Having the same kind of simple setup you will be fine I am sure. But things like recovery partitions, GPT and other stuff might mess up. But if you are happy to give it a try and let us know if things go wrong (proper error report so we can reproduce the issue) we should be able to fix things pretty soon.
-
@Sebastian-Roth Awesome. Ok I will let you know. Like I said we are still in the discussion process of moving to a new environment for imaging. I can say though it looks like we will at least give it the old college try with Fog. We have received positive feedback form the offices that have tried it out.
-
@eddiestuder I’ve deployed re-sizable image types with GPT disks and Windows 8.1 from-scratch images without much trouble. As @Sebastian-Roth said, if you try with a manufacturer base image that you’ve simply modified, you will likely run into issues.
I personally can not understand why anyone would risk a security breach (lookup lenovo Superfish) just because they don’t want to build an image from scratch. I always build from scratch, and I never let manufacturer software manage manufacturer drivers, I install them manually through Windows (but that’s another story).
There are some tips here: https://wiki.fogproject.org/wiki/index.php/Windows_8_UEFI_Imaging_Tips
I would bet those steps will apply verbatim to Windows 10. -
Hi all…
I’m about to attempt to image a Surface Pro 3 that’s been upgraded to Windows 10 from Windows 8.1. It has multiple partitions (5 in total) on the drive and the Disk format in Disk Management is showing as Basic.
Do I set the Image type in FOG to be Single Disk - Resizable? Or Multiple Partition Image - Disk Disk (Not Resizable)?
-
@Toby777 said:
Resizable? Or Multiple Partition Image - Disk Disk (Not Resizable)?
Either can work - but you need FOG Trunk to make it work. See this thread: https://forums.fogproject.org/topic/5800/help-with-surface-pro-3-pxe
-
Thanks @Wayne-Workman
I am currently running a trunk version so will test it out. -
@Toby777 Also, you might want to check out this thread. It’s pretty long, but in my opinion - this is one of the best threads we have in the entire FOG Forums.
https://forums.fogproject.org/topic/5732/dell-venue-8-pro-imaging-emmc/20?page=4
I would imagine that the things learned in there will apply to many tablet devices.
-
@Wayne-Workman In relation to your manual installation of drivers… Windows 10 is able to automatically identify and install drivers for so many devices anymore, its hard to want to bother even adding drivers manually for most workstations.
-
@need2 except lan. If windows doesn’t have drivers for network, you need to provide them something otherwise it can’t identify and download latest
-
@Tom-Elliott True, if you are imaging odd systems, you absolutely want to specify LAN drivers. However the Windows Driver Framework supports so many classes of LAN adapters, chances are yours are already supported by built in Windows drivers. You should of course test a few systems before rolling out a new image.
-
Is the FOG-Windows-Client compatible with Windows 10?
-
@cotec
The legacy client (The one shipped with 1.2.0 and below) should be Windows 10 compatible. The new client (shipped with developer builds of FOG) is definitely compatible. -
@Jbob It’s compatible with Windows 8.1