Jump to content


Namoh21

Established Members
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    1

Namoh21 last won the day on May 24 2018

Namoh21 had the most liked content!

Namoh21's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. From my MS ticket that I have open, it sounds like there was a bug with Task Sequences that should be fixed in the next update (1610) that hopefully is available on Thursday 11/4. They cannot confirm when the update will be released, but the Tech said they release the updates on Thursdays.
  2. no difference to my errors. Per Microsoft, it's a known bug (SMS 448525) and I'm waiting for them to have a solution to the issue.
  3. sorry, early morning for me. I have redeployed the deployment, Created a new collection and a copy of the TS to make sure there was no "bad data" causing this issue. MS has replied to me today saying this might be an existing bug and they might have a fix to test with. Crossing my fingers on this one.
  4. We do not use SCCM for system updates for our windows 7 TS, just our Windows 10. Our Windows 7 TS has been working for years before I did the 1607 upgrade. The only system updates we have deployed to the system is Windows 10 cumulative, Security and Virus Definitions. None of those updates are deployed to a Windows 7 device, as we use a WSUS for Win7. I do not have an option to redeploy the TS to the DP as all the packages are showing as being distributed. I have even rebuilt the DP role on the DP with no luck. I can run the TS when the computer has an older client, so I'm thinking there is an issue with the new SCCM client. Still waiting to hear back from MS on if they have found anything in their code.
  5. I do see this part of the execmgr.log at the time of clicking Install for my OSD: OnOptionalExecutionRequests attempted for package IVP00330 optional program * [QueueRequest: false RunOnCompletion : true QuietMode: true SDKCallerId: (null)] execmgr 10/17/2016 9:36:08 AM 496 (0x01F0) Validating package IVP00330 program * in the chain. The content request ID is {00000000-0000-0000-0000-000000000000} execmgr 10/17/2016 9:36:08 AM 496 (0x01F0) Creating an optional execution request for package IVP00330 program * execmgr 10/17/2016 9:36:08 AM 496 (0x01F0) Content is not available on the DP for this program. The program cannot be run now. execmgr 10/17/2016 9:36:10 AM 496 (0x01F0) OnOptionalExecutionRequests failed for program * : 0x87d01106 execmgr 10/17/2016 9:36:10 AM 496 (0x01F0) OR OnOptionalExecutionRequests attempted for package IVP002B9 optional program * [QueueRequest: false RunOnCompletion : true QuietMode: true SDKCallerId: (null)] execmgr 10/17/2016 9:42:07 AM 3908 (0x0F44) Validating package IVP002B9 program * in the chain. The content request ID is {00000000-0000-0000-0000-000000000000} execmgr 10/17/2016 9:42:07 AM 3908 (0x0F44) Creating an optional execution request for package IVP002B9 program * execmgr 10/17/2016 9:42:07 AM 3908 (0x0F44) Content is not available on the DP for this program. The program cannot be run now. execmgr 10/17/2016 9:42:09 AM 3908 (0x0F44) OnOptionalExecutionRequests failed for program * : 0x87d01106 execmgr 10/17/2016 9:42:09 AM 3908 (0x0F44) I have validated that the DPs for this client had all the packages that are part of this Task Sequence (which is ID: IVP00330 or IVP002B9, two different tests seen here). I have tested this same Task Sequence with an older SCCM client and the image works. It seems like I cannot install my Windows 10 Task Sequence or Windows 7 while using client 5.00.8412.1307. If I PXE or Media boot the computer, I can image with no issues.
  6. Were you able to find a solution for this issue? I'm experiencing the same issue and have seem to stump Microsoft.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.