Windows Server 2016 WIM -OSD

Hello All,

I’m trying to import this image into the OSD image library. It’s been running for 30+ mins. and seems to be hung in the initial analysis. Any thoughts?

It’s generating a sha1 hash of the WIM image. I’ve seen very poor performance using BigFix to calculate hashes of files over a network path (I see you’re reading from \client\Z$), I believe due to a very small read buffer being used (you can see this in procmon, that it’s reading something tiny like 512 bytes at a time or something like that).

It should perform better if you copy the wim to a local path on your console machine first, then the small read buffers aren’t exacerbated by the network read latency.

1 Like

Thanks the solution was helpful.
I have one more question, Please suggest I have uploaded WIM image but still it says complete setup file was not uploaded.
Kindly check the below screenshot and suggest.