the Icons Used for Software Updates

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 R2 Configuration Manager

Synchronized software updates are displayed in the Configuration Manager console, and the first column for each software update contains an icon that indicates a specific state. Software update groups are also represented with an icon that provides information about the state of the software updates contained in the group. This section provides information about the software update icons and what each icon represents.

Icons for Software Updates

Synchronized software updates are represented by one of the following icons.

Normal Icon

 The icon with the green arrow represents a normal software update.

Description:

Normal software updates have been synchronized and are available for software deployment.

Operational Concerns:

There are no operational concerns.

Expired Icon

 The icon with the black X represents an expired software update. You can also identify expired software updates by viewing the Expired column for the software update when it displays in the Configuration Manager console.

Description:

Expired software updates were previously deployable to client computers, but once a software update is expired, new deployments can no longer be created for the software updates. Expired software updates contained in active deployments continue to be available to clients.

Operational Concerns:

Replace expired software updates when possible. When software updates become expired, Configuration Manager does not remove the software updates contained within active software update deployments. Configuration Manager continues to assess software update compliance on expired software updates in deployments, but they are considered “not required” for reporting purposes.

Superseded Icon

 The icon with the yellow star represents a superseded software update. You can also identify superseded software updates by viewing the Superseded column for the software update when it displays in the Configuration Manager console.

Description:

Superseded software updates have been replaced with newer versions of the software update. Typically, a software update that supersedes another software update does one or more of the following:

• Enhances, improves, or adds to the fix provided by one or more previously released software updates.
  
• Improves the efficiency of its software update file package, which clients install if the software update is approved for installation. For example, the superseded software update might contain files that are no longer relevant to the fix or to the operating systems now supported by the new software update, so those files are not included in the superseding software update's file package.
  
• Updates newer versions of a product, or in other words, is no longer applicable to older versions or configurations of a product. Software updates can also supersede other software updates if modifications have been made to expand language support. For example, a later revision of a product update for Microsoft Office might remove support for an older operating system, but add additional support for new languages in the initial software update release.
  

On the Supersedence Rules tab in the Software Update Point Component properties, you can specify how to manage superseded software updates. For more information, see the Supersedence Rules section in the Planning for Software Updates in Configuration Manager topic.

Operational Concerns:

When possible, deploy the superseding software update to client computers instead of the superseded software update. You can display a list of the software updates that supersede the software update on the Supersedence Information tab in the software update properties.

Invalid Icon

 The icon with the red X represents an invalid software update.

Description:

Invalid software updates are in an active deployment, but for some reason the content (software update files) is not available. The following are scenarios in which this state can occur:

• You successfully deploy the software update, but the software update file is removed from the deployment package and is no longer available.
  
• You create a software update deployment at a site and the deployment object is successfully replicated to a child site, but the deployment package has not successfully replicated to the child site.
  

Operational Concerns:

When the content is missing for a software update, clients are unable to install the software update until the content becomes available on a distribution point. You can redistribute the content to distribution points by using the Redistribute action. When content is missing for a software update in a deployment created at a parent site, the software update must be replicated or redistributed to the child site. For more information about content redistribution, see the Redistribute Content on Distribution Points section in the Operations and Maintenance for Content Management in Configuration Manager topic.

Metadata-Only Icon

 The icon with the blue arrow represents a metadata-only software update.

Description:

Metadata-only software updates are available in the Configuration Manager console for reporting. You cannot deploy or download metadata-only software updates because a software update file is not associated with the software updates metadata.

Operational Concerns:

Metadata-only software updates are available for reporting purposes and are not intended for software update deployment.

Icons for Software Update Groups

Software update groups are represented by one of the following icons.

Normal Icon

 The icon with the green arrow represents a software update group that contains only normal software updates.

Operational Concerns:

There are no operational concerns.

Expired Icon

 The icon with the black X represents a software update group that contains one or more expired software updates.

Operational Concerns:

Remove or replace expired software updates in the software update group when possible.

Superseded Icon

 The icon with the yellow star represents a software update group that contains one or more superseded software updates.

Operational Concerns:

Replace the superseded software update in the software update group with the superseding software update when possible.

Invalid Icon

 The icon with the red X represents a software update group that contains one or more invalid software updates.

Operational Concerns:

When the content is missing for a software update, clients are unable to install the software update until the content becomes available on a distribution point. You can redistribute the content to distribution points by using the Redistribute action. When content is missing for a software update in a deployment created at a parent site, the software update needs to replicated or redistributed to the child site. For more information about content redistribution, see the Redistribute Content on Distribution Points section in the Operations and Maintenance for Content Management in Configuration Manager topic.

For More Information :

http://technet.microsoft.com/en-us/library/hh848254.aspx

Troubleshooting Content Mismatch Warnings on a Distribution Point in System Center 2012 Configuration Manager

You might see content mismatch warnings in System Center 2012 Configuration Manager when content validation runs and determines that there is a discrepancy between the expected list of packages in WMI on the distribution point and the packages in the content library. In this scenario, the distribution point status goes into a warning state and the status message returned by the distribution point is listed in the Details pane when you view the status of the distribution point in the Monitoring workspace, Distribution Point Configuration Status node.

You can see an example of this scenario in the following screenshot where a distribution point has a Warning state and there is a status message in the Details tab in the Details pane that shows there was a failure to retrieve the package list.

 

Note: There is currently a known issue in the current release where the warning might not always clear to return the distribution point status back to a success state. We hope to address this issue in a future release.

To determine which package is causing this mismatch, review the smsdpmon.log file on the distribution point.

Using the CMTrace log file tool, the following snapshot shows the corresponding smsdpmon.log entry:

Notice the log entries:

CContentDefinition::LibraryPackagesWmi: The package data in WMI is not consistent to PkgLib CContentDefinition::LibraryPackagesWmi: Package CCA0000A can't be found in PkgLib

The simplest way to determine the missing package is to view the Content Status  in the Monitoring workspace and search for the package ID by using the search field. After you have found the package ID, you can determine the name of the software.

If the package is not on the site, you must remove the package from WMI on the distribution point. The namespace to connect to is root\sccmdp. The class that contains the list of packages expected is SMS_PackagesInContLib. The simplest way to find the package and remove it from WMI is to run a query on the distribution point such as the following, and then delete the object that is returned.

select * from SMS_PackagesInContLib Where PackageID = 'CCB00002'

Note: Ensure that you replace the CCB00002 with your own package ID

If the package is on the site, you can update the content on the distribution point to clear the Warning state.

To update the content on the distribution point for applications:

1. In the Configuration Manager console, click Software Library.
2. In the Software Library workspace, expand Application Management, and click the Application node.
3. Find and select the application by using the name that you identified from the Content Status.
4. In the Details pane, click the Deployment Types tab, right click a deployment type, and then select Update Contentto create a new package and version of the content on the distribution point: 
   

The next time content validation occurs, the warning is cleared.

To update the content on the distribution point for packages:

1. In the Configuration Manager console, click Software Library.
2. In the Software Library workspace, expand Application Management, and click the Packages node.
3. Find and select the package by using the name that you identified from the Content Status, or by using the Package ID.
4. Right click the package, and select Update Distribution Points to create a new package and version of the content on the distribution point: 
   

The next time content validation runs, the warning is cleared.

For More Information 

http://blogs.technet.com/b/configmgrteam/archive/2012/05/07/troubleshooting-content-mismatch-warnings-on-a-distribution-point-in-system-center-2012-configuration-manager.aspx

Printer Report with More Info

SQL :

SELECT distinct
A.Name0, A.UserName0, B.Name0, B.DriverName0, B.Location0, B.PortName0, B.ShareName0,Manufacturer0, Model0

FROM v_GS_COMPUTER_SYSTEM A, v_GS_PRINTER_DEVICE B
WHERE A.ResourceID = B.ResourceID
AND B.Name0 != 'Microsoft Office Document Image Writer'
AND B.Name0 != 'Adobe PDF'
AND B.Name0 != 'Microsoft XPS Document Writer'
AND B.Name0 != 'PDF-XChange 3.0'
AND B.DriverName0 != 'Microsoft Shared Fax Driver'
AND B.DriverName0 != 'pdfFactory 2'
AND B.DriverName0 != 'CutePDF Writer'
ORDER BY A.Name0

List all printers (local and networked) SQL Report

SQL Report :

1. SELECT SYS.Netbios_Name0,printer.DriverName0, printer.Location0,printer.PortName0,printer.PrintProcessor0
FROM v_GS_PRINTER_DEVICE printer

JOIN v_R_System SYS ON SYS.ResourceID = printer.ResourceID

ORDER BY SYS.Netbios_Name0

Enable Printing Related Classes in SCCM 2012 and SQL Report

Enable Printing Related Classes in SCCM 2012 and SQL Report  :

There is a limited amount of network printer information available in SCCM 2012 and most of the information that is available is generally limited to local printer resources. Apparently this is because the SCCM client uses the user context “System” and therefore queries the HKEY_CURRENT_USER (HKCU) of “System” and not the HKCU of the user that is currently logged into the computer. So, for example, if you are looking for the default network printer that is selected by the local user, that information is a little harder to retrieve. Let’s look at the printer information that is relatively easy to come by before getting to the HKCU.

Before you can get the printer information you need to make sure that hardware inventory is enabled in the client settings and the printing classes are available in the hardware inventory classes.

Go to \Administration\Overview\Client Settings and click on properties for the Default Client Settings.

Click on Hardware Inventory and then Set Classes

After the Hardware Inventory Classes screen comes up Click on Add

This brings up the “Connect to Windows Management Instrumentation (WMI)”  dialog box.

In this case the classes would be loaded from the SCCM server that I am logged into. Since all of my clients are Windows 7, I would rather choose classes directly from a windows 7 box to be safe.

So enter a fully qualified domain name in the “Computer name” field, I left the WMI namespace the same, click “Recursive”, Credentials required since the computer is not local and type in credentials with administrative access, then “Connect”.

Now you will see all of the available classes, some will be marked “No” which means they are not enabled and the other will say “Yes” meaning that they are already available in theHardware Inventory Classes screen. There are allot of classes to look through, if you want to find the printing related classes just do a search from the “Search for inventory classes” search bar above.

As you can see all of the printing related classes say “Yes” and their associated boxes to the far left are grayed out which means I have already enabled these classes in the hardware inventory. If you’re print related classes say “No” the check boxes will be white so simply check the box and click ok.

Now that you are back in the main “Hardware Inventory Classes” screen you will see theprinting classes available. Now you must check the boxes to include these classes in your hardware inventory. Now after a hardware inventory has been completed this information will be available through Resource Explorer , Queries and Reports. 

SQL Report :

select Distinct 
    PD.Name0, 
    count(*) 
from 
    dbo.v_GS_PRINTER_DEVICE PD 
Group by 
    PD.Name0 
Order by 
    PD.Name0

Count of Local Printers SQL Report

SQL :
select Distinct 
    PD.Name0, 
    count(*) 
from 
    dbo.v_GS_PRINTER_DEVICE PD 
Group by 
    PD.Name0 
Order by 
    PD.Name0

Count of PC within each OU SQL Report

SQL :

select
    ou.ou,
    count(*) as 'total'
from
    (SELECT sys.ResourceID, max(OU.System_OU_Name0) AS 'OU' FROM dbo.v_R_System AS sys INNER JOIN dbo.v_RA_System_SystemOUName AS ou ON sys.ResourceID = ou.ResourceID GROUP BY sys.ResourceID) ou
group by 
    ou.ou
Order by 
    ou.ou