But no. It’s still there which makes me kind of sad.
I know Microsoft has priorities. But any update which breaks core functionality should be addressed with the next patch cycle. In this case however this issue is carried on to every next iteration of the update rollups…
Sure, the earlier reported workaround solves the issue here as well. But still it’s a pain in the #@!. Makes updating a SCCM 2012 R2 hierarchy unnecessary complex, especially when multiple DPs with Multicast enabled are being used.
Hopefully Microsoft will find the time, resources and budget to fix this nagging issue for once and for all.
No comments:
Post a Comment