Program rejected (wrong platform) at end of SCCM OSD for Win 10

SCCM windows 10 (64-bit) deployment has mystery task status of "Program rejected (wrong platform)" at the very end of task sequence history report. There are no error codes that I can see in the report. It looks like everything installed correctly. I've tried disabling recently added tasks to see if I can find the culprit, but no such luck.

I don't see anything in the smsts.log. But it's very possible I'm not looking for the right thing.

I've double checked the 64-bit specific package installs to make sure the "requirements" are defined properly.

While I'm trying to find whatever it is I've missed, does anyone have any suggestions on how to find the problem task?

KH
RhoSysAdminAsked:
Who is Participating?
 
Adam LeinssConnect With a Mentor Senior Desktop EngineerCommented:
Nothing I find in that log file indicates a problem, so I took your original error and found this:

http://henkhoogendoorn.blogspot.com/2014/07/strange-issue-in-monitoring-status.html
 
I checked our task sequences here and we have "Run on any platform" selected in the TS properties.  Ours are set to "Only media and PXE".

Supposedly, the fix would be to change the "Make available" under Deployment Settings to "Configuration Manager clients, media and PXE", but I don't know that I would recommend that, since every CM client would have to process that TS even if it is not applicable to them.
0
 
Adam LeinssSenior Desktop EngineerCommented:
Sounds like a program as part of the task sequence is restricted from running on a certain platform.

I would create two groups: Success and Failure.  _SMSTSLastActionSucceeded set to TRUE for Success and _SMSTSLastActionSucceeded for Failure

Then create the steps here:

https://blogs.msdn.microsoft.com/steverac/2008/07/15/capturing-logs-during-failed-task-sequence-execution/
http://www.markcorsillo.com/?p=128

Once you have a copy of SMSTS.LOG, you can open that with CMTRACE to debug which program is not installing.
0
 
RhoSysAdminAuthor Commented:
I've been looking at the SMSTS.LOG, and I can't find anything that doesn't have an exit code of zero.

The "Program rejected" status is always the very last entry for the TS deployment. It's always a couple of minutes after the previous status entry - which tells me it's being reported after the final reboot I configured with the SMSTSPostAction task variable I configure at the end of the TS.

To get a clean shutdown after the TS has completed, I've configured this variable to be "cmd.exe /c timeout /t 30 & shutdown /r /t 0 /f". This appears to work according to the status report. But at the end of the SMSTS.LOG, I see this:

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.

End program:
Finalize logging request ignored from process 3992
Waiting for CcmExec service to be fully operational
CcmExec service is up and fully operational
Current Assigned Management Point is SCCM12-SITE-PRD.ms.rhoworld.com with Version 8540 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>
Successfully connected to MP SCCM12-SITE-PRD.ms.rhoworld.com:80
Attempting to release request using {0594C768-5E1C-4DA3-AA89-5EFAFD21B774}
ReleaseRequest failed with error code 0x80004005
Task Sequence Manager could not release active TS request. code 80004005
Process completed with exit code 0
Exiting with return code 0x00000000
Process completed with exit code 0
Task sequence completed 0x00000000
Resume SCCM Client.
CCMExec service startup type is set to enabled
Modifying CCMExec Service to auto start.
CCMExec Service started
Waiting for CcmExec service to be fully operational
CcmExec service is up and fully operational
Successfully connected to MP SCCM12-SITE-PRD.ms.rhoworld.com:80
Cleaning up any active TS requests in WMI.
No instances of CCM_TSExecutionRequest found.
Cleaning up any maintenance task requests in WMI.
No instances of SMS_MaintenanceTaskRequests found.
Uninstalling Setup Hook
Removing setup hook from registry.
Successfully removed C:\WINDOWS\system32\OSDGINA.DLL
Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE
Successfully removed C:\WINDOWS\system32\_SMSOSDSetup
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.

End program:
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs


I know it does the final reboot. I also know if I remove the SMSTSEndProgram task, I still see the "Program Rejected" status entry at the bottom of the report.


There is the following earlier in the SMSTS.LOG, but only by a few seconds:

Failed to delete directory 'C:\_SMSTaskSequence'
SetNamedSecurityInfo() failed.      
SetObjectOwner() failed. 0x80070005.
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.      
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence      


The C:\_SMSTaskSequence directory is not there when the TS completes. This could just be my extra reboot causing an extra attempt to delete something that's already gone.
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
Adam LeinssSenior Desktop EngineerCommented:
Can you attach the full SMSTS.LOG to your question?
0
 
RhoSysAdminAuthor Commented:
See attached.
opti_5050_smsts.log
0
 
RhoSysAdminConnect With a Mentor Author Commented:
Well, that worked. After making the change to the deployment settings to be "Configuration Manager Clients, media, and PXE", the final status message at end of task history report is now "Program received".

We only deploy OSD TS's to a specific collection, and have a password in front of it. So I can live with this setting change.

I have to agree with Henk. This is still odd, but it's better than seeing the words "rejected" and "wrong platform".  We can live with "Program received".
0
 
Adam LeinssSenior Desktop EngineerCommented:
It is odd, since we are also on 1706 (same as you) and we don't have that set and we do not see that error message.
0
 
RhoSysAdminAuthor Commented:
I didn't see this until I starting tweaking the TPM settings in the bios and enabling bitlocker in the TS - all of which works.

I'll have to take this as a win and move on I guess.

Thanks for your help!!
0
 
Adam LeinssSenior Desktop EngineerCommented:
Solution is posted, it just appears it wasn't closed out.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.