Whilst trying to rebuild a device via OSD I noticed that the advertised Task Sequence was not showing up my list of available Task Sequences.
I’m attempting to deploy a Windows 7 TS to my device which is in the Build collection.
But as mentioned the Task Sequence is not showing up as available.
I checked the deployment to ensure that it was advertised to PXE clients and it was.
So it was time to crack open the smsts.log to gather further information. In the log was the following information ‘Skipping Task Sequence CMR0002E because it’s not active yet’
Hmm. Quick check of my Task Sequence Package ID and, yep it matches.
So why is it skipping? Seems that with SCCM 2012 R2 SP1 I need to set the option ‘Schedule when this deployment will become available’ in my Task Sequence deployment Scheduling settings from today…
..to a date in the past, say yesterday.
Now when I start the build I can see the Task Sequence.
I almost lost half a day because I didn’t see my tasks sequence …
This make them appear…
Glad it helped you
What a bug again! I scratched my head when I saw the smsts.log… Thanks for the help!
Did you report this bug already? I think you should 🙂
It’s a known issue. I believe it’s addressed in R2 SP 1 CU 1 but can’t confirm that at the moment. Will do later
I have had this with R2 SP1 CU1.
Thanks for confirming. Nothing mentioned in the CU1 update so, yes this must not have been addressed. https://support.microsoft.com/en-us/kb/3074857
Thank you so much for this genius tipp! You saved my day 😉 The problem still seems to exist in 2012 R2 SP1 CU1 (which is what I use)
This saved my Day after nearly going mad with this Error 🙂
I can say also, Problem still excists with R2 SP1 CU1
Thanks alot mate 🙂
No problem. Frustrating it wasn’t patched with CU1.
I pulled my hair out for 8 hours today determine what is causing it to fail. I wish I would of found this blog earlier.
Thank you. This article helped me a lot.. Hurray
You are geat! Save me after 8hours of troubleshooting!!!!
This worked for me. Thank you for this post.
Still an issue with 2012 R2 SP1 CU1. Confirmed today. easy fix, yet still gets me occasionally.
What a deeply irritating bug… thank you for sharing the workaround with us!
I just spoke with MS, I don’t know how many people have upgraded to CU2 at this point, but that is the prescribed fixed.
Thanks for this info.
It works great!!
This is still an issue and this article was a life saver! Thank you