Few months ago,I blogged about SCCM Configmgr 2012 SSRS Patch Compliance Report Per Collection Per Update Group .This report tells you ,how your specific software update group (list of patches) is performing on specific collection(list of computers). It has linked report to see what computers are non-compliant for troubleshooting with some additional client information if you compare with default compliance report. In this post, I have made some changes and bring additional report called patch progression report (have added installed patches to the report) to show how patches each PC is missing and installed with client information like OS,Last…
Author: Eswar Koneti
Read More
The latest version of Configuration manager which is V1511 (YY/MM) RTM for December 2015 from Microsoft is now available for download and ready to install to production Environment. We call this version as System Center Configuration Manager current branch (CB) and Microsoft has updated TechNet documentation on December 8 (Yesterday) for this version .The documentation is Applies To: System Center Configuration Manager (current branch) https://technet.microsoft.com/en-us/library/mt346023.aspx As you all know by now that ,going forward ,Microsoft do not use year or product identifier like previous versions 2003,2007 and 2012 and it supports incremental product updates (no more service packs or cumulative…
Last week,I was working on Intergraph application upgrade to latest version.Client has different versions of Intergraph and the removal of older versions is not straight forward like other applications using msiexec /x{ProductID} /qn. The command line is different for all these versions and I cannot put these command lines in one script and run on remote computers using Configmgr. Doing by so,will give error on the higher version of clients while running uninstallation for older applications.For ex: client is having Version 2011 R2 and when the script runs ,it will have 2011 R1 uninstallation command line ,this will give error…
This post is an extension to my previous article to view the content status for the applications,packages,driver packages,software updates,windows images using SSRS report instead of Console. Few people contacted me ,if there is way to get the status /Report of all packages on all Distribution points with its compliance % and other information what is available in SCCM console, when you look at monitoring-Distribution Status—>content Status and the reason for this is, performance of the console for this node is little slower . To know the distribution status of specific application,we generally refer to monitoring node—content Status. By default this…
In Configuration manager 2012,the update limit per update-deployment group has been increased (hard limit) to 1000 where was in Configmgr 2007,it was just 500 updates.More information about the hard limit and further questions ,worth reading the blog post by Kevin http://blogs.technet.com/b/server-cloud/archive/2012/02/20/managing-software-updates-in-configuration-manager-2012.aspx The hard limit is --the list of software updates what you see in software update group from Configmgr console but not how what is downloaded to the source path.(I figure this in below SQL query) With above reference,the max hard limit that deployment group can contains only 1000 updates ( am sure, no one reaches there due its to…
Software update groups in Configmgr 2012 simplifies lot of administrative work ,which simply contains list of updates (must be downloaded before you add any updates) merged to single deployment (can have multiple deployments for single software update group). Coming to the subject line, It is necessary (during cleanup activity) to find software updates that are downloaded but not in any software update group (I said software update group but not deployment group ..there is little difference with these two). If you want to get software updates that are downloaded but not in any deployment group ,you can refer Stephen blog…
Recently ,I have got a request from the business unit manager on the reboot of computers due to patch management (applicable to Applications as well) .The Custom client device setting ‘ Display temporary notification to the user ' (shown below) set with 480 minutes across the enterprise workstations but specific department (ex: Engineering), not happy with this setting due to the nature of their business. So ,we have agreed to have custom reboot settings . Creating Custom device settings and applying it onto collection is not that much difficult but the deal here is,creating a device collection using user…
Microsoft released Technical preview 4 (TP4) for Configmgr Vnext ( System Center Configuration Manager and Endpoint Protection ) .The previous technical preview was Technical preview 3 with updated version 1510 (YYMM). Microsoft haven’t updated the TechNet documentation with capabilities available with this release (TP4) for now but soon to be updated here on https://technet.microsoft.com/library/dn965439.aspx. This technical preview must be installed as new installation on server box with all the prerequisites met .Upgrading to SCCM Configmgr Vnext TP4 from a previous version of SCCM Configmgr Vnext TP3 is not supported. Upgrading from TP4 4 to a later version of SCCM…