Microsoft Configuration Manager
An integrated solution for for managing large groups of personal computers and servers.
4,244 questions
Cannot deploy applications in OSD Task sequence. Packages will deploy.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 21%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENP%3C/text%3E%3C/svg%3E)
Neville Patrawala
0
Reputation points
MECM Version - 2303 (Not Hotfix Rollup)
This is a new environment. The server has been stood up for about a year before I inherited this.
MECM environment
· One Server with all roles installed. (MP, DP, etc)
· SQL 2019 DB also resides on this server
Issue - When running OSD TS, we are receiving an error: The task sequence could not be run because the program files for ScopeID could not be found. If I remove all applications in the TS, and leave only packages, the TS will start
Resolution Attempts
- Confirmed "Allow this application to be installed from the Install Application task sequence action without being deployed" is checked.
- Verified boundaries are good.
- Confirmed content is distributed on DP.
- Confirmed in monitoring pane for content distribution
- Confirmed in Content library Explorer Tool that the application is not Pending.
- Browsed to the path displayed by the Content Library Explorer Tool that the folder and files exist.
- Redistributed application to DP.
- Created new application, and replaced that in the TS.
This also happens if I create a standalone USB media. I confirmed the application was on USB drive.
Items of Interest
- Content Explorer does not show a version for the application currently in the TS. This is shown in the Content Explorer Screenshot (bottom arrow). Another application does show the version, however this did not deploy either. The difference here is that I have redistributed the application that does not show the version number. I'm not sure what to make of this, it could be nothing.
Content Explorer Tool Screenshot.jpg - There is another SCCM Management Point in the same domain. The other SCCM Management Point is published to AD. I see that the Management point I'm dealing w/ is not published to AD. In the smsts.log (file has been sanitized), I see it is looking at the AD site of the other management point. I do not see a reference for the MP server name of the other site. Should this site be published to AD for application deployment to function?
Files
1. smsts.log
2. distmgr.log