Two edits: 1. It's a machine-based deployment, not a user based like I mentioned below.
2. The machines under both failure and success, I noticed the failures list one username and the success lists another. So that must be the reason its listed under both. Question is, any way to prevent that in the Monitoring node? Or will I just have to use reporting to get a more accurate snapshot? From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Tuesday, February 04, 2014 12:01 PM To: [email protected] Subject: [mssms] Deployment Monitoring I was having issues with a deployment this past week where I had over 500 failures. I fixed it last night so that number has gone down but I noticed it wasn't going down as much as the successes were going up. After further examination and comparing the list of machines under Success vs the list under the Error tab, I see a bunch of assets that are listed under both. They were failures yesterday but late last night/this morning, they ran the deployment successfully so I would assume that those assets would no longer exist under the Error tab. I tried to run summarization but no change. Will that straighten itself out as time goes by? Or is it normal for the Monitoring node? Also, I'm curious why a lot of the assets are listed twice under failure. One by SYSTEM and the other by the userid. It's a user-based deployment so is that just indicating that it tried to run as both contexts and failed both times? One last thing, how long after a deployment fails will it try to run again? Is that the "Schedule re-evaluation for deployments" setting within the client policy? Thanks, James ________________________________ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. ________________________________ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
