CLIENTS STUCK ON DEPLOYMENT STATUS "IN PROGRESS"

After creating some task sequences and deploying them to some clients, there were some errors in the process and unfortunately the tasks didn't completed successfully. After making the corrections and trying to re-deploy them, the client wasn't able to receive and start them and I noticed that the clients were still stuck on "in progress" status on Deployment Status. So, to correct this situation as I didn't find any native mode on ConfMgr to do that, simply deleting the client from ConfMgr and making a rediscovery got the job done.

ENABLING MICROSOFT .NET FRAMEWORK 3.5 ON A TASK SEQUENCE WITHOUT MDT INTEGRATION

I've been struggling to enable Microsoft .NET Framework 3.5 on a ConfMgr 2012 task sequence without using MDT integration. As with MDT you simply add the "Add Roles and Features" to the task and select the framework, without it as proven to be harder. Something so simple and all Microsoft tech should be pretty straight-forward. After some research in the internet and some testing and retesting this is a working solution.

STEPS:

#1 Create a folder structure as you normally would to accommodate the source for our SCCM package. In that folder create a PowerShell script (run PowerShell as Admin) named InstallNetFX3.ps1 with the coding:

Set-ExecutionPolicy unrestricted -Force

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:".\"

#2 Create a package, with no program associated, in SCCM 2012 pointing to that source. Distribute the package.

#3 Create a task sequence step (Run PowerShell Script) and populated it like the next figure:

"Run Powershell Script" step on task sequence

Give it a try.