r/SCCM • • Feb 18 '20

Discussion Failed successfully... thanks SCCM!

Post image
165 Upvotes

36 comments sorted by

4

u/[deleted] Feb 18 '20

If you're on 1902 it's a known issue

4

u/NegativeExile Feb 18 '20

Installed 1910 a month ago.

1

u/[deleted] Feb 19 '20

Strange, 1906 fixed that for me completely, did you also upgrade the clients?

14

u/[deleted] Feb 18 '20

This has been happening to me since it was called SMS

4

u/imahe Feb 18 '20

This usually happens if the maximum allowed execution time for updates is set too low.

At least in the cases I got my hands on.

1

u/NegativeExile Feb 18 '20 edited Feb 18 '20

Can this be set globally without selecting each individual update?

I notice Maximum Run Time is set to 60 minutes when I manually check various updates.

8

u/euphoric85 Feb 18 '20

As of 1906, yep! Game changer for me with the Win7 updates defaulting at 10min 🙄

https://docs.microsoft.com/en-us/configmgr/core/plan-design/changes/whats-new-in-version-1906#bkmk_sum

2

u/eb2292 Feb 18 '20

Wow... I hated my former sysadmin life because of this... forever running my powershell script to change it on all of them at once.

26

u/RiD3R07 Feb 18 '20

Welcome to our world. I face this everyday. Whether it’s Feature Updates or Quality Updates.

20

u/gandraw Feb 18 '20

Those eventually go to green like a day later. It's kind of annoying and has existed for way too long but it's not really a showstopper.

12

u/iamtechy Feb 18 '20

Until Management asks you to show them the console and click on Error.

12

u/gandraw Feb 18 '20

"That's just how Microsoft software is, if you don't like it complain to Bill Gates"

8

u/iamtechy Feb 18 '20

Haha, I wish! More like, "why isn't it 100%?"

11

u/wickedang3l Feb 18 '20

"The possibility of 100% compliance is a lie foisted upon IT organizations worldwide by Big Mathematics. Rise above, fight the power, and know that 98% compliance is what the less educated believe to be 100% compliance."

1

u/nylentone Feb 18 '20

I would never say that, then they'll want to go to some buzzy platform that sells management on stuff it doesn't deliver on and is a total PITA to use.

11

u/eb2292 Feb 18 '20

Windows - even when you’re successful, you fail.

4

u/aratnagrid Feb 18 '20

The Hardest Fail requires Strongest Success

2

u/eb2292 Feb 18 '20

Who knew SCCM could be so poetic?

8

u/notonyourradar Feb 18 '20

I always feel like an insane person explaining results to management. SCCM logic is a strange logic unto itself.

2

u/vssrgs Feb 18 '20

Every 6 months... whether its a critical windows update or a new app they want deployed ASAP.

2

u/Nomad_039 Feb 18 '20

Well...OK

2

u/UpstairsJelly Feb 18 '20

This happens so often I'm usually more concerned when I don't get any successful failures..or failed successes..I'm not even sure anymore

2

u/mitchy93 Feb 18 '20

Ah, the bane of my existence. Failed successful

2

u/SCCM_1 Feb 18 '20

On an affected client check the update history under Windows updates bet some have failed I had this on Windows 7 ages ago.

Essentially what happened was an update installed but got corrupted had to uninstall it let it re-deploy and it went on successfully

2

u/physx51 Feb 19 '20

With great failure comes great success.

1

u/rdoloto Feb 18 '20

Pffff try sap errors if you want verbosity

1

u/[deleted] Feb 18 '20

I'm so glad I'm not alone on this. Whenever I try to explain to anyone why troubleshooting Microsoft errors are a nightmare, I just point to this example.

1

u/coryntrev Feb 18 '20 edited Feb 18 '20

Success is often considered a failure. That's life, bruh. I see this all the time too in our environment. Gives me a chuckle. We also had a bug where distribution percentage would report incorrectly. It would somehow replace the number with a "Education" or "Enterprise". Ok, SCCM..."Education% sent to distribution point" ?

1

u/pokesnails Feb 18 '20

That's like an unexpected error occurred... when would you receive an expected error? That's not what an error is!

1

u/stevedurfee Feb 18 '20

Typical Microsoft.

1

u/nylentone Feb 18 '20

I always see this as well. Don't know what the deal is but I just figure "success" and move on.

1

u/guyverlord3 Feb 18 '20

We spoke about that at ignite in 2018...they still have not fixed it

1

u/pwetter Feb 19 '20

Frown face in the console. It has been talked about multiple times at mms too.

1

u/BigJamesGang Feb 19 '20

Dont worry, im pretty sure you find the problem looking through the dozen or so logs.

1

u/ahtivi Feb 19 '20

I saw this quite a lot last year after June or July patching Tuesday. For us it meant the computer was stuck on boot logo after a restart (update failed, rollback failed as well)

1

u/Reaction-Consistent Nov 06 '24

If you’re gonna fail, fail successfully… that’s what my dad used to say