SCCM SQl Query - Package Details with Type

select *,
'Package Type (Text)' =
Case
when v_Package.PackageType = 0 Then 'Software Distribution Package'
when v_Package.PackageType = 3 Then 'Driver Package'
when v_Package.PackageType = 4 Then 'Task Sequence Package'
when v_Package.PackageType = 5 Then 'Software Update Package'
when v_Package.PackageType = 6 Then 'Device Setting Package'
when v_Package.PackageType = 7 Then 'Virtual Package'
when v_Package.PackageType = 8 Then 'Application'
when v_Package.PackageType = 257 Then 'Image Package'
when v_Package.PackageType = 258 Then 'Boot Image Package'
when v_Package.PackageType = 259 Then 'Operating System Install Package'
Else
'Unknown'
End
from v_Package

SCCM incremental versions & Features

Release             Feature 
Version

1511 Pre-production client deployment
1511 Upgrade OS from upgrade package
1511 WinPE Peer Cache
1511 Windows 10 Servicing
1511 Universal Windows Platform (UWP) app distribution
1511 New software center
1511 Deploy MSI through MDM
1511 Windows store browsing from Admin UI
1511 Detect Windows Update for Business clients
1511 WSUS cleanup task in ConfigMgr Admin UI
1511 Mac OS X support
1511 Integration with Microsoft Passport for Work
1511 On-premises Mobile Device Management
1511 In-console updates
1602 Monitor terms and conditions deployments
1602 iOS activation Lock
1602 Health Attestation
1602 Software center branding changes
1602 Client Online Status in Admin console
1602 Allow Intune devices access to Exchange on-premises
1602 Conditional Access for PCs
1602 Kiosk mode for Android KNOX  devices
1602 Manage Office 365 client updates
1602 Manage volume-purchases iOS apps
1602 iOS App Config policies
1602 Win 10 servicing improvements
1602 SQL Always-on support
1602 Support for in-place upgrade of ConfigMgr OS
1602 Sync Policy button in Software Center
1602 Auto creation of MS Office mobile apps for iOS and Android
1606 “site servicing status” node changed to “Updates and servicing”
1606 Consent required for Pre-release features
1606 OMS Connector
1606 Configurable client cache size
1606 Support for multiple MP
1606 Manage Windows store for business apps
1606 iOS volume purchased apps mangement improvements
1606 Improved software center user interface
1606 smart lock for android devices
1606 iOS activation lock
1606 Device categories
1606 SQL Always-on support
1606 Remote Control file transfer improved
1607 Custom end user dialogs
1607 Manage Duplicate hardware identifiers
1607 OMS Connector
1607 Win10 Edition upgrading
1608 Application requests from Software Center
1608 Asset Intelligence improvements
1608 New software indicators in Software Center
1608 Remote Control Keyboard translation
1610 Exclude clients from automatic upgrade
1610 Peer Cache for content distribution to clients
1610 Migrate multiple shared distribution points at the same time
1610 Cloud management gateway for managing Internet-based clients
1610 Manage hardware identifiers
1610 Enhancements to Windows Store for Business integration with Configuration Manager
1610 Use compliance settings to configure Windows Defender settings
1702 Support for Windows 10 Creators Update
1702 Express files support for Windows 10 Cumulative Update
1702 Deploy Office 365 apps to clients
1702 Customize high-risk deployment warning
1706 New Windows 10 compliance settings
1706 Three new MAM policy settings introduced
1706 Ability to manage Microsoft Surface driver updates
1706 Run PowerShell scripts from the Configuration Manager console
1706 Update reset tool to troubleshoot in-console updates
1706 Client Peer Cache support for express installation files for Windows 10 and Office 365
1710 set icon size of apps in software center to 512×512 pixels
1710 Enhanced Software center customization
1710 New step in the task sequence to run another task sequence
1710 You can now restart computers right from SCCM console
1710 Co-management for Windows 10 devices. You can now concurrently manage Windows 10 devices by Configuration Manager and Intune as well as joined to Active Directory and Azure AD
1802 Windows Delivery Optimization to use Configuration Manager boundary groups
1802 Cloud distribution point site affinity
1802 Co-Management Dashboard
1802 Surface Device Dashboard
1802 Phased deployments for task sequences
1802 Windows Autopilot Device Information
1802 Management Insights
1806 Site server high availability feature
1806 Uninstall application on approval revocation
1806 CMPivot
1806 Deploy PXE-enabled distribution point without Windows Deployment Services
1806 CMTrace is now installed along with client agent
1806 Configuration Manager Toolkit is now included
1806 View Currently logged-on user
1806 Feedback can be submitted from console
1806 Network congestion control for distribution points
1806 Partial download support in client peer cache
1806 Feature to configure remote content library for the site server
1806 Deploy software updates without content
1806 New software updates compliance report
1806 Deploy third-party software updates
1806 New product life-cycle dashboard
1810 Support for Windows Server 2019
1810 Prefer cloud distribution points over distribution points
1810 Improvements to collection evaluation by fully disable a schedule with a query-based collection
1810 Repair applications directly in Software Center
1810 Approve application request via email
1810 Task Sequence support of Windows Autopilot for existing devices
1810 Phased deployment of software updates
1810 Configuration Manager administrator authentication
1810 SMS Provider API
1810 New Permission for Client Notification actions
1902 Stop cloud service when it exceeds threshold
1902 New Client health dashboard
1902 Add cloud management gateway to boundary groups
1902 Distribution point maintenance mode
1902 Import a single index of an OS image
1902 Optimized image servicing
1902 Replace toast notifications with dialog window
1902 Office products on lifecycle dashboard
1902 View recently connected consoles
1902 In-console documentation dashboard
1906 Azure Active Directory user group discovery
1906 Readiness insights for desktop apps
1906 Add joins, additional operators and aggregators in CMPivot
1906 Use your distribution point as an in-network cache server for Delivery Optimization
1906 Support for Windows Virtual Desktop
1906 Multiple pilot groups for co-management workloads
1906 Application groups
1906 Install an application for a device
1906 Task sequence debugger
1906 Clear app content from client cache during task sequence
1906 Pre-cache driver packages and OS image
1906 More frequent countdown notifications for restarts
1906 Additional options for WSUS maintenance
1906 Configure the default maximum run time for software updates
1906 Drill through required updates
1906 Office 365 ProPlus upgrade readiness dashboard
1906 Role based access for folders

Source - https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-incremental-versions 

WMI Query to List Down two Application Installed Machines - SCCM 2012

Query to list all the systems with Program A and Program B, use the following query.
Replace Program A and Program B with your application add remove programs display name

Select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from  SMS_R_System where SMS_R_System.ResourceId in (select SMS_R_System.ResourceId from  SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like 'Programe A') and SMS_R_System.ResourceId in (select  SMS_R_System.ResourceId from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like 'Programe B')

Unable to access DP Source - HTTP code 503 service unavailable

Sometimes you find clients are failed to download software updates , application and you will be seeing error massage HTTP code 503 service unavailable in few client logs.

First you have to check the boundary and boundary group are correctly configured
Then check if you see any error in IIS or check the application pool is running, If its stopped start again.
If the IIS Application Pool stops frequently,  check for any error in event viewer

If you find the about error, it could be related with permission issue
Check  HKLM\Software\Microsoft\SMS permission, if the permission are not configured for users,
Create it as mention below.

WSUS Cleanup Using SQL Script

Whenever we do a cleanup on WSUS we always get the below error.

Every update on WSUS (even if they are unapproved) get their metadata sent to clients unless the updates are marked as expired

WSUS does not clean unneeded (obsolete? superseded? unapproved?) updates itself. we had been running it as a "fire and forget" server: allow it to auto approve security updates and then leaving it alone. This fills the database with a bunch of updates that gets sent out

WSUS has a Cleanup Wizard which is supposed to expire obsolete and unneeded updates. We tried running this, but it would get stuck and hang forever

There is lots of advice about how to fix this problem: defragging hard drives, running the Cleanup Wizard multiple times, running weird PowerShell scripts that launch the Wizard via the command line. Most of the time noting will work 

Finally we found the below script which will help to do the cleanup through SQL

1. ·         We can’t access WSUS database through remote SQL Management Studio, so we have to install SQL Management Studio locally.
2. ·         To connect SUSDB - \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query For Server 2012 \\.\pipe\MICROSOFT##WID\tsql\query.
3. ·         Make a New Query

Run the below query to check the status

exec spGetObsoleteUpdatesToCleanup

Again execute the below query to clean up the unapproved, superseded and obsolete updates.

DECLARE @var1 INT

                                DECLARE @msg nvarchar(100)

                                 CREATE TABLE #results (Col1 INT)

                                INSERT INTO #results(Col1) EXEC spGetObsoleteUpdatesToCleanup

                                 DECLARE WC Cursor

                                FOR

                                SELECT Col1 FROM #results

                                OPEN WC

                                FETCH NEXT FROM WC

                                INTO @var1

                                WHILE (@@FETCH_STATUS > -1)

                                BEGIN SET @msg = 'Deleting ' + CONVERT(varchar(10), @var1)

                                RAISERROR(@msg,0,1) WITH NOWAIT EXEC spDeleteUpdate @localUpdateID=@var1

                                FETCH NEXT FROM WC INTO @var1 END

                                CLOSE WC

                                DEALLOCATE WC

DROP TABLE #results

Now check if you see any update using this query - exec spGetObsoleteUpdatesToCleanup

Finally, run the WSUS cleanup wizard now, you will not get any errors now.

Task Sequence - Restart Option - Error (0x00000032)

In SCCM image deployment if you get the below error during software/application installation, it could be a problem with restart step in task sequence

To confirm this you have to check the deployment log and you will be getting the below error after the restart step,

The operating system reported error 50: The request is not supported

If you check the restart properties in the task sequence the important thing to note here is that the Reboot must be set to restart "The currently installed default operating system" otherwise it will try and run the TS boot image again which obviously won't really like trying to install drivers/software/applications. In short, be sure any reboot which forms part of the Task Sequence has the below option selected,

SCCM Console Object Edit Error (Cannot edit the object which is used by...)

Sometimes when you try to edit any objects in 2012 Console, you probably get the below error, 

his because the ConfigMgr console was crashing while editing the object.

We have to run the following query in SQL to free the objects again

 select * from SEDO_LockState where LockStateID <> 0
(where SEDO stands for Serialized Editing of Data Objects)

Collect the Lock ID from the above query result and delete it with the below query,

DELETE from SEDO_LockState where LockID = ‘<LockID of the record identified in the previous query>’

Once the record is removed, We should be able to modify the object again. Hope it helps!