Forum Discussion
Gallery Image vs Blob Custom Image
Hi,
I've limited experience, but I'll try and answer as many of your points as possible:
1. Primarily the usage of a custom image is to aid in the configuration process. As you say programs, registry tweaks, user language/input options, required files and nay other tweaks can be performed upon one VM. Then it's shut down and a "Gold" image is created. You can then use this to create/spawn your pool of Vms from as a base image. It's particualry useful if you have a large WVD pool with many hosts. As one might imagine once you get over 5 or more VMs perfomring the required setup "Tweaks" can take a long time, with the possiblity of missing something along the way.
2. Any hosts built from a custom image are ONLY built from that image. So their OS disk is formed of a COPY of the custom image. No changes are made to the image in any way.
3. As stated before, the custom image is not 2logged into", it's better to think of it as the image used as a copy for each VMs OS disk. If you need to update a custom iamge you would need to create a Vm using it as the image, then make your required changes, then create a new image from that VM to replace the older one.
4. The Microsoft gallery image is maintained by Microsoft, so in that sense is pure. As for whether Microsoft keep it up to date, I'm unsure. A quick Google produced no relevant results. So I'll have to leave that to someone else to answer. One would hope the gallery images are kept somehwat up to date. I do know I've still had Windows updates to install when using a Microsoft Gallery image, so how up to date they are is debateable..
Hope this helps somewhat.
Hi,
I've limited experience, but I'll try and answer as many of your points as possible:
1. Primarily the usage of a custom image is to aid in the configuration process. As you say programs, registry tweaks, user language/input options, required files and nay other tweaks can be performed upon one VM. Then it's shut down and a "Gold" image is created. You can then use this to create/spawn your pool of Vms from as a base image. It's particualry useful if you have a large WVD pool with many hosts. As one might imagine once you get over 5 or more VMs perfomring the required setup "Tweaks" can take a long time, with the possiblity of missing something along the way.
2. Any hosts built from a custom image are ONLY built from that image. So their OS disk is formed of a COPY of the custom image. No changes are made to the image in any way.
3. As stated before, the custom image is not 2logged into", it's better to think of it as the image used as a copy for each VMs OS disk. If you need to update a custom iamge you would need to create a Vm using it as the image, then make your required changes, then create a new image from that VM to replace the older one.
4. The Microsoft gallery image is maintained by Microsoft, so in that sense is pure. As for whether Microsoft keep it up to date, I'm unsure. A quick Google produced no relevant results. So I'll have to leave that to someone else to answer. One would hope the gallery images are kept somehwat up to date. I do know I've still had Windows updates to install when using a Microsoft Gallery image, so how up to date they are is debateable..
Hope this helps somewhat.