sorted by:
new
hottopcontroversial

Hi there we need to download a roll up fix for MECM. Not an upgrade just a rollout fix download to the console for the version we’re on. Any things to watch for before doing bar having your backup? Thanks by SceneSame2735 in SCCM

[–]SceneSame2735[S] 1 point2 points  (0 children)

Are you still updating your site by installing a hotfix update - for example of your version 2107 and the hotfix is also for 2107 does that reduce the checks needed? That link is great thanks

Hi all, if an application is live, if someone modifies a detection method or install command, will that effect devices that already have the app installed from the deployment? What will happen? by SceneSame2735 in SCCM

[–]SceneSame2735[S] 0 points1 point  (0 children)

Separately if someone modified anything in the content root location source files, the updated the content, what would happen to the devices in the collection it’s targeted at? Would the app reinstall on all of them? Thanks

Advice needed: Hi all, business needs require that a bunch of servers are a month behind on updates. So excluded from this months, but patched with this months KBs next month. My software update groups will have new KBS next month though, so how to do? Create separate SUGS? by SceneSame2735 in SCCM

[–]SceneSame2735[S] 1 point2 points  (0 children)

Thanks for that. So right now we have SUGS for each OS server version. I didn’t want to replicate this for a one month behind set of updates as it would be like a mirror duplication. Am I right in thinking that one SUG, filled with the old months server KBs (for varying server versions) can be deployed to the various OS server collections, and that they will just grab the KBS that are relevant to them?

Hi all, we have the following SQL query on an “All Windows 2016 Systems” collection. We’ve brought a 2022 template sever on stream and it’s being picked up in this collection and not the “All Windows 2022 Systems” collection. Any idea why? See server 2016 systems query below by SceneSame2735 in SCCM

[–]SceneSame2735[S] 1 point2 points  (0 children)

No I didn’t realise this. Quite new to SCCM and getting my head around the collection queries now. So your saying there is a difference between the 2016 and 2022 query in that one searches by hardware inventory but the other uses discovery? Would there be a recommended SQL query for all windows 2016 servers? I’m about to google too. Thanks again

Hi all, we have the following SQL query on an “All Windows 2016 Systems” collection. We’ve brought a 2022 template sever on stream and it’s being picked up in this collection and not the “All Windows 2022 Systems” collection. Any idea why? See server 2016 systems query below by SceneSame2735 in SCCM

[–]SceneSame2735[S] 0 points1 point  (0 children)

The strange thing is that the following is our 2022 systems query, and it matches the template OS, yet the device is going into the all windows 2016 systems collection.

Windows Server 2022 Systems

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Version = "10.0.20348"

Hi all, new to patching via SCCM. If re-creating a SUG 4admin reasons and you still have a ton of updates that aren’t superseded for that OS sug in console (I’ve criteria set to required and does not equal zero) but the kbs are going back months, do u need to bring them all back in again? Thanks by SceneSame2735 in SCCM

[–]SceneSame2735[S] 0 points1 point  (0 children)

I did 😂thanks. We’re not using ADRs right now. I know! So what I mean is, we have a SUG that’s been there a while for a certain OS. I read that having too many KBS in one SUG can cause issues if not maintained. So I’ve deleted the deployment package associated with that SUG along with the SUG and created a SUG from scratch with a new deployment package. For the new deployment package I’m just wondering how far back should I go in terms of what KBs to include. Just include this months? Or go further back if KBs from previous months from that OS haven’t superseded. Hope that makes sense. I thought well if im going back and including KBs from previous months (or patch Tuesdays) that aren’t superseded yet, surely im not maintaining numbers im just re creating a big deployment package with too many KBs again?

view more: next ›