I’ve run into an issue that I haven’t seen mentioned anywhere so I thought I would ask here. I have deployment of all my images working fine. Last week I decided to try using the ‘Offline Servicing’ feature to inject the Windows Updates into the images. I tested on one image and everything updated just as I expected. I did a second one and it also updated fine. When I did the third one, it failed. Digging into the issue, I discovered that it was using a drive that doesn’t have enough space for it to extract and mount the WIM file, and then add all of the updates. This drive does have the NO_SMS_ON_DRIVE.SMS file, but apparently that doesn’t apply to the offline servicing function. Does anybody know if there is a way to make this feature use a specific drive? All of my wim files and application sources are on my F: drive which has about 1TB free. The servicing function is using the E: drive, which only has about 20GB free. I would like to redirect the Offline Servicing to use F: if possible.
↧