So 4M status messages / 30k workstations means you have about 130 steps in the TS that gets run every night? What all do you have this thing doing? I'd agree with Daniel and try to setup some scheduled tasks on the workstations. You also mention installing software during this TS? You're installing software on each machine every night?
From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, June 5, 2014 9:05 AM To: [email protected] Subject: [MDT-OSD] RE: Long-Shot: Possible to turn off Status Messages from a Task Sequence? A few things come to mind... 1. Stand-Alone media does not send status messages, but you would need to engineer running that every night 2. What about a package/application deployment instead? 3. Why not compliance or something scheduled locally on the workstations? Personally, I would go with #3. A nightly job deployed from ConfigMgr isn't the best mechanism in my opinion. I would rather have something that runs locally and you just verify it ran each night. Also, I would ask this to mssms instead of mdtosd. Probably less of a OSD question, and more of a general practice question. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Thursday, June 05, 2014 8:54 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Long-Shot: Possible to turn off Status Messages from a Task Sequence? (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://urldefense.proofpoint.com/v1/url?u=https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=YLoaD9diI1s4%2Bbj3PlFZfFYUoWamOOAiffEMydP82vk%3D%0A&s=3393a0a1e760a421048b350bdb66fd7d34fd3b142c6f0ebadc5c65c41f3f6c5e>] -------------------------------------------- "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 The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
