(We're probably pushing the use of Task Sequences beyond that which they were intended here.)
Every night we have a Task Sequence that we run on all of our machines (~30k) that performs maintenance routines and software installations. The problem is that our SCCM guys are finding that the flood of status messages coming in from all of those machines floods the Management Points and it takes them several hours to process them all and catch up. Estimates hover around 4 million status messages coming in from just this one TS running on all of our machines each night. Is there a way to stop a TS from submitting status messages? I'm sure it's a long shot but it's kind of our last hope before we're forced to re-engineer this nightly job into a single scripted solution. I don't like re-inventing the wheel and trying to duplicate all of the logic and features that a Task Sequence brings inside of scripts. I'd hate to lose all of that. Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA, MS [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
