markm091 Posted August 15, 2013 Report post Posted August 15, 2013 Hello all: I'm working on a Windows 7 OSD project and experiencing a weird issue. Before running a build and capture task sequence, I've updated a vanilla Windows 7 WIM using the offline servicing feature (by right-clicking the image in the console and hitting Schedule Updates). I've confirmed this process works just fine by checking out the OfflineServicingMgr log. 74 updates are applied and the size of the WIM grows by several hundred MB. When I deploy the resulting WIM using OSD however, a trip to view installed updates shows no updates installed. I've confirmed in the CM logs from the console and the smsts.log on the machine that it is indeed the updated WIM that was applied to the workstation. Deploying the same WIM using MDT and taking that same trip to view installed updates shows exactly what I expect, the 74 updates. I actually came across the issue several weeks ago and dismissed the successfully updated WIM as a failure. Then out of curiosity, I tried the test deployment with MDT and found it wasn't truly a failure. I later went back and tried the same WIM through OSD and that time the updates did show. I'm wondering if this is another weird SP1 bug. For instance, there's a bug that prevents me from using a newly captured WIM in an existing task sequence for 12 hours. I had this bug confirmed for me by a Microsoft Premier support specialist. Has anyone experienced this issue or something similar? Quote Share this post Link to post Share on other sites More sharing options...
markm091 Posted August 16, 2013 Report post Posted August 16, 2013 Never mind. Forget to update the DPs after updating the image. Today I am truly a Windows noob. Quote Share this post Link to post Share on other sites More sharing options...
