Today when Nerdio clones a desktop image for sysprep (computername-tmp), it chooses Standard HDD as the disk type. I have a long running script that applies Windows Updates and Office updates and Winget updates which occasional hits the 90 minute max time for script exectution in Azure leading to an error. Retrying the job works because nothing has really gone wrong, its just waiting for all the updates to complete.
Set-as-image process should use Premium SSD for the temp VM
4
Thank you for submitting your feature request—we truly value input from our community.
Next steps:
• We will review your request and update its status as it progresses through our evaluation process.
• If any clarification is needed, we'll follow up with you directly in the comments.
We also encourage the community to influence our decision through comments, votes, and feedback.
Next steps:
• We will review your request and update its status as it progresses through our evaluation process.
• If any clarification is needed, we'll follow up with you directly in the comments.
We also encourage the community to influence our decision through comments, votes, and feedback.
Hi Sean, this request is on our roadmap and is a feature that we are working towards implementing in the future.
We are beginning to run in to significant performance and timeout headaches on some of our busier images because of this issue. HDDs simply do not have the IOPS to complete sysprep on some of our complex images in a timely manner. We have had to increase the sysprep timeout environment variable to unreasonable levels.
Microsoft is deprecating HDDs as OS disks in September 2028. Can we get an update or timeline estimate for this feature?
Hi Barry Ferguson, we plan to have this feature implemented in Q3 of this year. Apologies for the delay.
Thank you for reaching out.
Please sign in to leave a comment.
Comments (4 comments)