nicholab Posted July 23, 2019 Posted July 23, 2019 I seem to have an issue with SCCM not deploying applications as part of a task sequence after an upgrade. I have update the package for the client and the tick box is selected to allow the use of the package in a task sequence. Also is it best to deploy application to a task sequence or to an AD group in SCCM?
Guest Guest Posted July 23, 2019 Posted July 23, 2019 We had issues with this recently. Turns out the client cache despite being set in client settings was only set to 5Gb as is default. I manually set this in the task sequence and this seemed to resolve the issue. However we had other apps that wouldn't install as an Application we had to use an Application package instead.
free780 Posted July 23, 2019 Posted July 23, 2019 For larger applications I don't let SCCM handle the content and run the command line from the UNC path directly. I also adapted a script to pull the application deployments targeted at the device and install them. You can run some powershell to increase the cache as part of the TS.
nicholab Posted July 24, 2019 Author Posted July 24, 2019 SCCM does not seem to be honoring the "Allow this application to be installed form the install application task sequence without being deployed."
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now