Forum Discussion
Solved
Error Deploying from SiG image, WVD Spring 2020
Hello, We are testing deploying a host pool using the new ARM-based deployment and I'm running into an error when deploying new versions. Source VM is running in Azure (server 2016 datacenter...
fgottman hi, this issue seems related to preparing the master image and not WVD. It is Azure compute that reports that the VM cannot be build based on the image provided. Path to for troubleshooting will be to try building a stand alone vm based on the image that has been selected. Once a single VM can be successfully provisioned then that image can be used in the with WVD.
Technically an image from an image should work but if support states its not supported I cannot argue the point.
We have also seen situations where certain applications break sysprep.
Stefan Georgiev
Microsoft
Microsoftfgottman hi, this issue seems related to preparing the master image and not WVD. It is Azure compute that reports that the VM cannot be build based on the image provided. Path to for troubleshooting will be to try building a stand alone vm based on the image that has been selected. Once a single VM can be successfully provisioned then that image can be used in the with WVD.
Technically an image from an image should work but if support states its not supported I cannot argue the point.
We have also seen situations where certain applications break sysprep.
Support hasn't said anything yet. I was hoping the community here might have run into a similar issue given the use case, as I can't find information about this anywhere else. I am going to have a need soon to do the same process with a Windows 10 image for a VDI deployment. I agree that the issue isn't directly related to WVD, but I can't find any other community that is attempting to use images in this way.
The same error occurs when deploying a VM straight from the image (no WVD). Sysprep process completes successfully, and I don't believe it is a conflict with an application, as this would have caused the first sysprep to fail as well.
Or am I just fundamentally misunderstanding the point of using images for WVD? Is everyone just building out new host pools and session hosts any time they need to apply software updates to a hosted application? Do they not maintain a "golden image", even for a desktop-VDI use case? Perhaps I will attempt all of this with a vanilla marketplace image instead of a cloned server, to see if that makes any difference
- Hi fgottman,
I am also in the same situation as you. I am using WIn10 Enterprise multi-session 2004.
I customized, sysprep, and capture and I get the same error.
I tried deploying a hostpool with just the standard image and it works.
Please let me know if you find a solution or close to it.That is not possible when a hostpool has been created using a shared image gallery.
You would have to recreate the hostpool.
I don't think the shared image gallery itself is the problem, we have deployed hosts before using image versions from the gallery.
I am now getting the same problem. My colleague had this too. We notice that when we run sysprep with the shutdown option, the VM is nevertheless rebooted. When that happens the image is not generalized anymore.
- Stefan Georgiev
fgottman the process being used in this case is not exactly what we have recommended as best practice (https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-customize-master-image) and also seems very unique to your context.
When it comes to images in WVD there isn't one answer that fits all organizations out there. From what organizations have shared with me I am not aware of anyone doing the below. (Most have scripts to automate and with fewer steps)
