MECM - Software Update Group

[eagle876291]

I would like to know what is the best way to get software update group for Microsoft windows patches:

1. ADR - Microsoft updates
   1. Create new software update group

When I try to create a monthly report to be emailed using the subscription feature, I come across an issue that when selecting the software update group, it it showing older reports instead of the current ones (not yet created or run by the rule)

how do I resolve this?

 

[Garth]

I would like to know what is the best way to get software update group for Microsoft windows patches:

1. ADR - Microsoft updates
   1. Create new software update group

When I try to create a monthly report to be emailed using the subscription feature, I come across an issue that when selecting the software update group, it it showing older reports instead of the current ones (not yet created or run by the rule)

how do I resolve this?

You will need to create a custom report for this. In it you select the newest SUG.

 

[eagle876291]

do you see anything wrong with this setup?

• workstations ADR Microsoft security patching
  • Evaluation: every week on Tuesday
  • maintenance window : every week on Tuesday

 

[Garth]

do you see anything wrong with this setup?

• workstations ADR Microsoft security patching
  • Evaluation: every week on Tuesday
  • maintenance window : every week on Tuesday

How does this help your reporting problem?

 

[eagle876291]

How does this help your reporting problem?

I want to know whether it is best practice to do the deployment once a month instead of weekly because if the machine(s) are not available during deployment sccm will try to deploy the updates next time the machine is online.

I am doing this weekly basis hoping it will catch all machines faster and get them all to be compliant.

am I missing something here?

 

[Garth]

I want to know whether it is best practice to do the deployment once a month instead of weekly because if the machine(s) are not available during deployment sccm will try to deploy the updates next time the machine is online.

I am doing this weekly basis hoping it will catch all machines faster and get them all to be compliant.

am I missing something here?

there is no such thing as best practices in the real world, there is only what works for you.
Yes doing once a month will work fine. But again what is wrong with doing it weekly or even daily?
again, exactly what problem are you trying to solve? As you started this thread off as a reporting issue and now move it to deployment settings.

 

[eagle876291]

there is no such thing as best practices in the real world, there is only what works for you.
Yes doing once a month will work fine. But again what is wrong with doing it weekly or even daily?
again, exactly what problem are you trying to solve? As you started this thread off as a reporting issue and now move it to deployment settings.

every month I get 1/3 amount of computers shown in unknown status during deployment

 

[Garth]

every month I get 1/3 amount of computers shown in unknown status during deployment

Ok, this will not be affected by how often you deploy SU per se. What troubleshooting have you done? Exactly how often are you scanning for SU status? Keep in mind Scan and deployment are not the same.

 

[eagle876291]

Ok, this will not be affected by how often you deploy SU per se. What troubleshooting have you done? Exactly how often are you scanning for SU status? Keep in mind Scan and deployment are not the same.

ADR> evaluation every week on Tuesday

 

[Garth]

ADR> evaluation every week on Tuesday

How often are you clients scan for the SU? e.g. what is your client setting configured for. What troubleshooting have you do for why devices are unknown's?