Upgrading SCCM with respect to SCSM 2012R2
That said - for us SCSM 2012 R2 users who aren't exactly sprinting into 2016 what things (if any) do we need to be aware of when upgrading our SCCM deployment? Is there some risk to the SCSM/SCCM connector that we should be aware of?
I get the impression (and hope) that since it isn't explicitly mentioned in @wally_mead's blogpost everything should be ok. But I certainly wouldn't mind some confirmation with respect to the latest 1610 branch.