Compliance based on Update Group Statistics

Hello,
I am confused about the "Statistics" looking at a Software Update Group. I have two groups, One for IE9, the other for IE10. Yesterday the IE9 group showed 80% (guessing looking at the chart graphic), then I pulled in IE10 updates and made a new
group. Now the IE9 group shows 14% compliant, and the IE10 group shows 76% compliant. Problem is I applied the updates to two different collections and right now all Windows 7+ get the automatically added to the IE9 group, so 3000+ clients, and the
IE10 group is manual, with 2 computers.
Now I understand that the chart shows overall compliancy instead of just the collection, but why am I now 76% complient on IE10 and not really compliant on IE9? I should be less compliant on IE10.
Someones insight on this would be helpful.
Thanks!

Also an addition. I found a thread on WindowsNoob about getting data out of v_GS_Installed_Executable. From what I can tell this is part of the hardware inventory, but when I look at the contents of the table it is empty. I do have hardware inventory enabled
on clients too.
I was looking for a report to show version of IE installed, which I was able to use v_GS_SoftwareFile to get the data since I am tracking *.exe in the database. Just curious why v_GS_Installed_Executable is empty, when by my understanding, it should have
data.

Similar Messages

Update group change in credit management

Dear All
We had earlier update group '00012' for the credit management. Now we want to change the update group to '00015' . We have changed so , it is working fine , but the earlier credit exposure was based on update group '00012' , hence sales value is open sales order value . Now while applying group '00015' , it should consider only open deliveries
After changing , we have also executed f.28 to re-organise the credit limit, still the credit exposure is not getting updated.
Kindly suggest any remedy.
Regard
AVS

Tyr execute the prgram - RVKRED77 and check once.

Collections based on Software Update Group compliance

Hi!
Is it possible to create a collection based on software update group compliance? This is for software update groups which are
not deployed, they are just monitor groups (for example, groups for yearly or quarterly software update compliance).
I would like to create a collection that lists all devices which are non-compliant in software update groups with names like "%Client Updates" - is this possible?
The reason for this is so I can impose some stricter Compliance Settings (among some other stuff) on devices that are not compliant.
I looked around a bit, but I could not find anything that I can use. Even Google couldn't solve my question :/

you can try something like this:
This collection is basically sub selected query get list of computers that do not have specific assignment enabled.
select * from SMS_R_System where SMS_R_System.ResourceId not in (SELECT distinct SMS_UpdateComplianceStatus.MachineID FROM SMS_UpdateComplianceStatus JOIN SMS_UpdateDeploymentSummary ON SMS_UpdateComplianceStatus.CI_ID = SMS_UpdateDeploymentSummary.CI_ID
WHERE SMS_UpdateDeploymentSummary.AssignmentName like "%Client Updates%")
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

Query version of a report 'Compliance 3 - Update Group (per update)'

Hi,
I was wondering if it was possible to create a query where I can view number of missing updates based on
my baseline. This will be similar to an existing report 'Compliance 3 - Update Group (per update)' and when I select a collection, I would expect it to show me the results similar to the report itself.
Example:
Title Bulletin ID
  Installed Required
Security Update for Windows Server 2008 R2 x64 Edition (KB2977292)
  0 145
Security Update for Windows Server 2008 R2 x64 Edition (KB2984972)
  0 145
Security Update for Windows Server 2008 R2 x64 Edition (KB3002885)
MS14-079   0
144
Thanks.
144

I'm not totally following what you're asking but why not create a new software update group (no deployments necessary) containing the same updates as in your baseline? This type of update group is informally called a compliance group. That way,
you just run the report you've called out against this compliance group.
Jason | http://blog.configmgrftw.com | @jasonsandys
This is purely for reporting purposes as we currently have a problem with Reporting Services. I thought I could create a query which will list the updates we have compiles in software update group and show how many servers require that update within limited
collection I will select on the query.
Thanks.

What Changes to Software Update Group Causes Clients to Re-check Compliance

Hello,
I have a number of software update groups that have been deployed over the past couple of years. When Microsoft release new updates etc. some of the updates already deployed change their status e.g. an update might get marked as expired. As a result of this
I can go from having clients reporting as being compliant to a situation where they are in an unknown state until they report back again.
Does anyone know what changes to an update already deployed would cause clients to have to check their compliance status for that software update group?
Thank you.
Stephen

If you are referring to the enforcement state, this is indeed specific to the deployment, not the group itself.
With regards to your question - Upon a change to your deployment, your clients will receive updated policy. On a successful evaluation of the deployment, it will re-send a state message if necessary. Unfortunately I do not know if there are certain
things that do not trigger a policy update (i.e. change in the name or description vs. update membership or deadline change)

SCCM 2012: windows updates groups, based upon criteria required?

Hi,
Is it correct to say that, for updating Windows machines/creating a software update group, you can use the criteria "required" + deployed = no?
That would simplify our setup: just select the OS, prodcuts, severity and "required" + deployed = no would contain all necessary updates.
J.
Jan Hoedt

Concur with Torsten. In general, I think using required as a criterion is a bad practice for exactly what Torsten outlined above. Additionally, if you are doing OSD, how will you deploy the updates to those systems during the task sequence as not all updates
will be available for them?
Jason | http://blog.configmgrftw.com | @jasonsandys

Resolution to error - Unable to update Database Statistics

OK, If there's one thing i hate most about SAP, its the dreaded installation, I am always so paranoid, as to something will definitely go wrong,
Lately i realized that it aint my mind , but the damn installation itself is pretty damn stupid. Why cant SAP leave the installation packaging to professionals like installshield...
Unfortunately SAP doesnt think of it as a better idea, so until then lets try to resolve as many errors as possible thru these forums..
Here's one error resolution ,i am pretty sure, many are checking for..
Use the following procedure to resolve error
Warning - "loading of sql client library oci.dll failed"
Error - Unable to update Database Statistics, Check BRCONNECT.log
The problem seems to be with the SAP Patch Collection InstallMaster disc Material No.(51032143_13).
To resolve the problem, here's what needs to be done,
1)Install DB Instance as usual.Then after the installation errors out due to loading of sql
client library oci.dll ..
2)I unsar the downloaded DBATOOLS.sar (Thanks for the Link Andreaz!!!)
log into sapnet (eg. service.sap.com) with your user-id/pwd:
-> downloads -> support packages and patches -> entry by application group -> additional
components -> sap kernel -> now chose either 32 or 64 bit; either unicode or non-unicode ->
sap kernel 6.40 -> windows server -> oracle -> download the package DBATOOLS Package for
Oracle 9.2.x ... brconnect is part of that package...
3)Copy the files in the Unsar'd package, as follows
 overwrite br*.exe to S:\usr\sap\R31\SYS\exe\run
 overwrite initSID.sap to S:\usr\sap\R31\SYS\exe\run &
S:\usr\sap\R31\SYS\exe\nuc\NTI386
 overwrite libsbt.dll to S:\usr\sap\R31\SYS\exe\run &
S:\usr\sap\R31\SYS\exe\nuc\NTI386
 overwrite sapdba_role.sql to S:\usr\sap\R31\SYS\exe\run &
S:\usr\sap\R31\SYS\exe\nuc\NTI386
4) Retry the installation again & Guess what!! it works....
Warning-: I initially tried a shortcut by replacing DBATOOLS.sar on the installmaster disc, rather than following above steps, but that doesnt seem to work, the installation fails as as soon as Tablespace creation starts. So the shortcut aint a good one..

Well, it looks like you resolved your problem yourself.
you can send feedback to SAP directly instead of posting this here in a forum.

Software Updates - Compliance Report Discrepency - Updates Listed in Report that aren't part of the deployment

I will try to explain this as clearly as I can. I've been unsuccessful in trying to search for this exact problem. I've not yet called support on this as it's not critical.
I recently began to see a problem in that our compliance reports showed two servers as compliance status unknown for an extended period of time. I made sure they had the most current version of
the WUA, I re-installed the SCCM agent, I manually applied patches using windows update directly on the machine. I've tried running the "RefreshSererComplinaceState" vbscript. However, the same issue persisted. I also noticed that
the number of servers listing as compliant and non-compliant remained relatively the same between deployments of
windows updates.
I began to research the compliance report "Compliance 1 - Overall Compliance". I began to see that there were updates listed in the report which do not correspond to updates which are
members of the deployment.
Example, The following patch "Update for Windows Server 2008 R2 x64 Edition (KB2800095)" I currently don't have as a member of any of my deployment packages. It's not a member of any
of my update groups. Yet, it's consistently being reported in the list of updates in that update group. That's one of several like that. It's not something I've encountered before.
Is there a way to reset my updates list on the server side the next time I get ready to do updates?

Hi,
Here is a good blog discussed the issue:
http://damatisystemcenter.com/2013/07/21/sccm-client-unknown-status-what-could-be/
In the meantime, please check UpdatesHandler.log on the client which status show unknown.

Credit control update group

Hi All,
Each automatic credit control must be assigned an update group.
The system allows for no update, as well as update groups 000012, 000015 and 000018.
What these update group does and please give me details of update group 000012.
Regards
Nidhi

Dear Nidhi,
Update group 000012
This is the stadard updategroup.
If you create an order you will get open values in S066. Afterwards you create the delivery, the open order values in S066 will be reduced and you get open delivery values in S067. Afterwards you create the billing document, the open delivery values will be reduced and the open billing values will be created in S067.
If you post the billing document to FI, the open
Update group 000015
No posting to open order values. The order is placed after the delivery is created.
Delivery u2013 increases open delivery value
Invoice u2013 reduces open delivery value and increases open invoice value
Acc. Doc. u2013 reduces open invoice value and increases open items
Used for orders without schedule lines u2013 service items or orders with schedule lines that are not relevant for delivery.
Update group 000018
No posting to open order values, only open delivery values (table S067) are updated
Sales order u2013 increases open delivery value
Invoice u2013 reduces open delivery value and increases open invoice value
Acc. Doc. u2013 reduces open invoice value and increases open items (accounts receivable)
This update group will be always used by order items which are billed order-related (VBAP-FKREL = B for example).
S066 Open orders: credit management table u2013 based on the confirmed quantities on the schedule lines times the credit price. Time period controllable via horizon. (Update report RMCSS066)
S067 Open deliveries/billing documnets u2013 uninvoiced deliveries and open billing documnets (not passed to accounting). Open orders can directly update the S067 (Update report RMCSS067)
Updating from S066 and S067 is hard coded and is not controlled by normal information structure !
I hope that the information are helpful
regards
Claudia

List of customer report based on account group - T.Code

Dear Guru's
I need list of customer report based on account group in standard SAP if it there please update th T.Code as earl as possible.
regards,
bhanu

Hello,
I don't think there is a standard report for this. SE16 select table KNA1 and check for the entries with respect to account group.
Prase

Update group in credit management

Hi friends , can anybody please tell me what is the use of update group in credit management.
regards
shyam

Hi S Sundhar
Credit update groups are based worked on opend documents for example of
000012 is the consider to the credit check to open sales orders,deliveries,billings,and F/I documents consider.
000015 is the consider only open deliveries and FAdocuments.
000018 is the consider open sales orders,open billings and FA documents only
this are diff to update groups
Thanks
Rajendra

About update group in credit management

can any one help of what is the exact work of update group what type of advanatage we get wwhile using update group for ex: 000012,000015,000018.
it is given that for 000012 sales order: increases openitems for orders for delivery relevant schedule lines.
how the system increases the open items for sales orders under update group 000012

Hi
Update groups are used, in order to group different key figures from (e.g) SD module to the structures in Logistics Information System.
What happens is when ever an event take place, e.g billing document raised, it can be customized to populate the LIS Structure (kind of a data warehouse) with key data you are looking for to report and evaluate. This update can be made either immediately or periodically.
The credit relevant data is updated into an information structure, where it is accessed andupdated. Thus each automatic credit control must be assigned an update group. The system allowsfor no update, and update group 000012, 000015 and 000018.
The difference between the three update groups is as follows:
Update group 000012
Sales order: Increases the open order value from delivery-relevant schedule lines
Delivery: Reduces the open order value from delivery-relevant schedule lines and increases the open delivery value
Billing document: Reduces the open delivery value and increases the open billing document value
Financial accounting document: Reduces the open billing document value and increases open items
Update group 000015
Delivery: Increases the open delivery value and increases the open billing document value
Financial accounting document: Reduces the open billing document value and increases open items
Update group 000018
Sales order: Increases the open delivery value
Billing document: Reduces the open delivery value and increases the open billing document value
Financial accounting document: Reduces the open billing document value and increases open items
The decision on which update group to use is based upon the business requirements; however,
update group 000012 is thorough and used in most businesses.

Update group in automatic credit control

Hi Everybody,
Can anyone explain me the meaning of update group in automatic credit control screen OVA8.
Do we have to set this update or it happens when we start usinng?
Regards,
raghu

Hi,
More info on this ,
Credit update for open order/delivery/billing document value
The credit update controls when the values of open sales orders, deliveries, and billing documents are updated.
Note
The open order value is only updated for schedule lines that are relevant for delivery.
Use
You can specify the following update groups for updating credit-related statistics:
Update group 000012
Sales order
Increases open order value from delivery-relevant schedule lines
Delivery
Reduces open order value from delivery-relevant schedule lines
Increases open delivery value
Billing document
Reduces open delivery value
Increases open billing document value
Financial accounting document
Reduces open billing document value
Increases open items
Update group 000015
Delivery
Increases open delivery value
Increases open billing document value
Financial accounting document
Reduces open billing document value
Increases open items
Update group 000018
Sales order
Increases open delivery value
Billing document
Reduces open delivery value
Increases open billing document value
Financial accounting document
Reduces open billing document value
Increases open items
Note
If a document cannot be processed with the update group you specify, the system determines the next possible update it can carry out. For example, you select Update group 000012 which, at delivery, reduces the open order value and increases the open delivery value. Assume that one item in the order is not relevant for delivery. In this case, the system automatically determines Update group 000018 for this item. Update group 000018 increases the open delivery value for the order item. The system uses the confirmed quantity of delivery-relevant schedule lines to update the order value.
Hope it adds. Pl reward if helpful.
Thanks & Regards
Sadhu Kishore

All Software update groups expired

Hi,
Please see http://social.technet.microsoft.com/Forums/en-US/39b60e34-f30a-4963-a08b-6a8e13e44b91/software-update-groups-grey-icon-with-x-?forum=configmanagersecurity
for reference.
We created update lists for Windows 7 with Office, automatic updates for SCEP, they all are expired (Expired icon of “http://technet.microsoft.com/en-us/library/hh848254.aspx). I don’t want them to expire. I want to make sure every new
OS will get the latest updates + antivirus updates.
Not sure if this is by design, an error on SCCM (http://social.technet.microsoft.com/Forums/en-US/0c13c27d-55a9-4f56-8ac0-f9053301ab0c/all-updates-in-sccm-software-updates-are-set-to-expire?forum=configmgrsum=>
my SCUP is there) or there is some misconfiguration.
Please advise. J.
Jan Hoedt

Jan,
> *Can you help me with this mechanism, I'm not familiar with it?
While viewing the updates that are a member of the software updates group, either sort by the "Expired" column or filter by Expired = Yex. Select all expired updates, right click, and select 'Edit Membership". Uncheck the checkbox for the software
update groups you are trying to remove them from.
> *I seem to remember there was somewhere an option that mentioned expired
This option has to do with how long 'superseded' updates will remain available for deployment. You can set under Administration > Site Configuration > Sites. Right click on your site and select Configure Site Components > Software Update
Point. The setting is on the "Supersedence Rules" tab.
However, Microsoft will also directly expire updates from time to time as well. In general, this is normal and something you shouldn't worry about managing. When the update has been expired by Microsoft, it is something you couldn't install even
by going to Windows Update, so you shouldn't worry trying to deploy them. Instead, deploy the current updates instead of superseded ones.
>How can I automate this (not automatically apply but using manually which updates to use and deploy at times I choose)?
For organizations with very simple Software Update processes, you could use an Automatic Deployment Rule to select updates based on a criteria, download the content to a deployment package, add the updates to a software update group, and create a deployment
to a collection. That deployment can be 'available' and not required if you plan to hand install them later.
This documentation gives you an overview of how all the Software Update Management features work:
http://technet.microsoft.com/en-us/library/gg682168.aspx#BKMK_DeploymentWorkflows
And this blog post gives an example of using an ADR:
http://blogs.technet.com/b/configmgrdogs/archive/2012/05/08/configmgr-2012-automatic-deployment-rules.aspx
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

Three updates from the same Software Update Group showing as unknown, while all the others are showing as expected.

Hi
I have an issue from Septembers security updates where three updates from the same software update group are showing as unknown status rather than required / not required / installed etc.
There are multiple other updates in the same update group and they are all displaying correctly with the figures I would roughly expect.
I would have expected if something was wrong with the clients not returning software update scans that all the updates in this software update group (all deployed automatically as part of the same ADR) would show the same status of unknown, rather than just
three of them.
The updates in question are: KB2894842, KB2972215 & KB2977629 (First two .net 4.0 and last one IE11).
Now these updates would largely be not required in our organisation as for the most part we use different versions so I would expect them to show as not required.
Short of kicking off a mass software update scan cycle I don't know a) why this has happened b) if a scan cycle will fix it. Our clients scan every week and its been several weeks since the updates were deployed, that and the other updates have all reported
back in.
Anyone have any ideas? Its making the compliance results look quite poor :(
Thanks
Jonathan

Hi,
Is there any clue in the logs? Please review WUAHandler.log.
What is the code you get when you run compliance report, like that in the following thread:
http://social.technet.microsoft.com/Forums/en-US/becda545-4a5e-4ea3-bd83-8c7026767af5/software-update-compliance-report-showing-status-unknown?forum=configmanagerdeployment

Compliance based on Update Group Statistics

Similar Messages

Maybe you are looking for