SCCM Query find All Server count with OS Name

SCCM Query find All Server count with OS Name

• Recently I was asked to count of servers by OS
• It was quite Challenging as we need to understand the SCCM Structure very well to do the SQL Queries.
• Following are the Queries to fin the Server by OS Name and the count of Servers

SELECT VR.operatingSystem0,COUNT(VR.operatingSystem0) FROM v_R_System AS VR

WHERE VR.operatingSystem0 LIKE '%Windows Server%'

GROUP BY VR.operatingSystem0

SCCM 2012 R2 Log File for Operating System Deployment issue

SCCM 2012 R2 Log File for Operating System Deployment issue

Operating System Deployment

The following table lists the log files that contain information related to operating system deployment.

Log name	Description	Computer with log file
CAS.log	Records details when distribution points are found for referenced content.	Client
ccmsetup.log	Records ccmsetup tasks for client setup, client upgrade, and client removal. Can be used to troubleshoot client installation problems.	Client
CreateTSMedia.log	Records details for task sequence media creation.	The computer that runs the Configuration Manager console
For System Center 2012 R2 Configuration Manager and later: DeployToVhd.log	Records details about the VHD creation and modification process	The computer that runs the Configuration Manager console
Dism.log	Records driver installation actions or update apply actions for offline servicing.	Site system server
Distmgr.log	Records details about the configuration of enabling a distribution point for PXE.	Site system server
DriverCatalog.log	Records details about device drivers that have been imported into the driver catalog.	Site system server
mcsisapi.log	Records information for multicast package transfer and client request responses.	Site system server
mcsexec.log	Records health check, namespace, session creation and certificate check actions.	Site system server
mcsmgr.log	Records changes to configuration, security mode and availability.	Site system server
mcsprv.log	Records multicast provider interaction with Windows Deployment Services (WDS).	Site system server
MCSSetup.log	Records details about multicast server role installation.	Site system server
MCSMSI.log	Records details about multicast server role installation.	Site system server
Mcsperf.log	Records details about multicast performance counter updates.	Site system server
MP_ClientIDManager.log	Records management point responses to the client ID requests task sequences initiated from PXE or boot media.	Site system server
MP_DriverManager.log	Records management point responses to Auto Apply Driver task sequence action requests.	Site system server
OfflineServicingMgr.log	Records details of offline servicing schedules and update apply actions on operating system .wim files.	Site system server
Setupact.log	Records details about Windows Sysprep and setup logs.	Client
Setupapi.log	Records details about Windows Sysprep and setup logs.	Client
Setuperr.log	Records details about Windows Sysprep and setup logs.	Client
smpisapi.log	Records details about the client state capture and restore actions, and threshold information.	Client
Smpmgr.log	Records details about the results of state migration point health checks and configuration changes.	Site system server
smpmsi.log	Records installation and configuration details about the state migration point.	Site system server
smpperf.log	Records the state migration point performance counter updates.	Site system server
smspxe.log	Records details about the responses to clients that PXE boot and details about the expansion of boot images and boot files.	Site system server
smssmpsetup.log	Records installation and configuration details about the state migration point.	Site system server
Smsts.log	Records task sequence activities.	Client
TSAgent.log	Records the outcome of task sequence dependencies before starting a task sequence.	Client
TaskSequenceProvider.log	Records details about task sequences when they are imported, exported, or edited.	Site system server
loadstate.log	Records details about the User State Migration Tool (USMT) and restoring user state data.	Client
scanstate.log	Records details about the User State Migration Tool (USMT) and capturing user state data.	Client

Upgrading an Operating System from Windows 2003 to Windows 2008: How to Prevent Discovery Problems

Upgrading an Operating System from Windows 2003 to Windows 2008: How to Prevent Discovery Problems

• Before you upgrade the operating system on a monitored computer, uninstall the Operations Manager agent. After the upgrade, reinstall the Operations Manager agent.

Reason:

• The objects that the management pack discovers, such as logical disks, are hosted by a parent class that is not version-specific. When you upgrade the operating system, the order in which discovery occurs can result in duplicate objects being discovered.
• For example, you upgrade a computer running Windows Server 2003 to Windows Server 2008. 
• If the Windows Server 2003 discovery rules run first after the upgrade, the instance of the computer running Windows Server 2003 and its objects will be removed from discovery because the operating system base class has been removed. When the Windows Server 2008 discovery rules run, the computer and its objects will be discovered again.
• If the Windows Server 2008 discovery rules run first after the upgrade, the computer running Windows Server 2008 and its objects will be discovered. When the Windows Server 2003 discovery rules run, the instance of the computer running Windows Server 2003 will be removed from discovery, but the objects hosted by that instance will not be removed.
• So If you upgrade a computer without uninstalling the agent first and then discover duplicate objects, uninstall the agent to mark all hosted objects as deleted in the database. Next, reinstall the agent to only discover existing applications/objects.  

New Windows Server Operating System Management pack for Windows 2012 R2 version 6.0.7297.0

New Windows Server Operating System Management pack for Windows 2012 R2 Version 6.0.7297.0

• Microsoft has released a new MP for Windows Server which include 2012,2012 R2, Windows 2008

Following are the Fixes that has been done in this latest

• In 2008, 2012 platforms, the “Logical Disk Free Space (%) Low” monitor do not alert as expected when free space is 0%. With this fix, this monitor will alert when free space is 0%

• In all platforms, logical disks are un-discovered if we configure them as Asymmetric storage on Failover Cluster. With this fix, this issue will be resolved

• The Windows Server OS Management pack collects logical disk size is megabytes. During discovery this value used to be assigned to integer property. When logical disk size is significantly large (for example, when disk is of several petabytes), in megabytes format it goes out of boundaries of integer type. As a result the workflow fails while trying to insert discovery data. To support large logical disk another double properties was introduced, since double type has much more wide values range. Old integer property with constant “-1” value is preserved for upgrade compatibility and marked as DEPRECETED

• “Volume Mount Points on Dynamic Disks” aren’t discovered by Microsoft Windows Server 2012 Discovery MP. With this fix, this issue will be resolved

• MP has been modified to not discover System Reserved volumes on Windows Server 2012 to ensure it is consistent with the rest of the OS versions

To Download the Latest MP: Click Here