System Center Blog

    by Mikael Perhult (SCCMx)

    Browsing Posts in SCCM

    When installing an additional SMS provider on a Site System Server there are some things that has to be checked so that a successful installation can be carried out.

    If the additional SMS provider Server host any role that has SQL SRSS installed on it or any other SQL products, make sure to downgrade SQL Native Client to SQL 2008 if the SQL 2008 R2 version is installed. The method for fixing this is just an uninstallation via ARP and from the SCCM prereqs download folder can the MSI for SQLNCI be found.

    The same prereqs has to be installed on the Provider Server as with a CM2012 SP1 Primary Site Server.

    Which is the ADK with Components; PE, DEP Tools, Perf Tools and USMT

    If the SCCM Agent does not appear to initiate and register with the site after an OSD the agent can have settings left in the registry that the task sequencer puts ther by design:

    Set to the following and restart ccmexec:



    When adding a source hierarchy and then configure it for Share Distribution Points there are somethings to consider:

    – The boundaries associated will be migrated and there will be Boundary Groups created for the shared DP’s.

    – If the Shared DP is stuck on “Eligible for Upgrade” – NO, there as some roles that cannot exist on the DP before being changed to YES, for example PXE

    In SCCM 2012 there can be more than one active Management Point per site.
    The agent will automatically resolve this list and handle the assignment dynamically.

    Sometimes when the MP has been installed after for example the Reporting Role and WSUS the Inboxes path is not correctly set in the registry.

    The problem lies in that smsexec can not process the files and forward these to the primary Site and then to SQL.


    Missing from registry are the Key and the subvalues under:

    Subsequent are the MPFDM hive located wrongly under the Wow6432Node node.

    Remove MP, WSUS and other roles applicable and add the MP role first.
    Check that Inboxes are correctly set in the registry.


    When running the RTM media it fails on the Site Recovery scenarios for restoring the site database.

    The scenarios tested are:  Recover the site database using the backup set at the following location and Use a site database that has been manually recovered

    The ConfigMgrPrereq/UI log says:
    Dedicated SQL Server instance;    Error;    Configuration Manager requires a dedicated SQL Server instance to host its site database.  You selected a SQL Server instance that hosts the site database for another Configuration Manager site.  Select a different SQL Server instance for this new site to use, or resolve the conflict by uninstalling the other site or moving its database to a different SQL Server instance
    Tests using SP1 Beta media successfully completes the database restore.


    When there is a need for clearing out old packages can this report be created.

    It lists all packages and task sequences not being referenced from any advertisment.

    Create a report with the following query:

    select  v_Package.PackageID, v_Package.Name,v_Package.SourceVersion,v_Package.SourceDate 
    from dbo.v_package 
    packageID not in (select PackageID from dbo.v_Advertisement)and 
    PackageID not in (SELECT ReferencePackageID FROM v_TaskSequenceReferencesInfo) and not like '%deploy%' and (V_package.PackageType ='0' or V_package.PackageType ='4')
    group by v_Package.PackageID, v_Package.Name,v_Package.SourceVersion,v_Package.SourceDate
    order by v_Package.Name

    By using HINV and changes to SMS_DEF.MOF can inventory be made of maintenance windows in SCCM.
    Edit SMS_DEF.MOF (make sure to have a backup and check dataldr.log that the changes was applied successfully).


    //  *Maintenance Window - COMPANY
        #pragma deleteclass("COMPANY_MAINT_WINDOW",NOFAIL)
        #pragma namespace ("\\\\.\\root\\cimv2\\sms")
        [SMS_Report     (TRUE),
        SMS_Group_Name ("Company Maint Window"),
        Namespace      ("root\\\\ccm\\\\policy\\\\machine\\\\actualconfig"),
        SMS_Class_ID   ("CUSTOM|COMPANY_MAINT_WINDOW|1.0") ]
        class CCM_ServiceWindow : SMS_Class_Template
         [SMS_Report(TRUE), key] String ServiceWindowID;
         [SMS_Report(TRUE)] String Schedules;
         [SMS_Report(TRUE)] uint32 ServiceWindowType;


    This inventory can then be added as rules to Collections.

    Assigned Servers with Maintenance Windows (WMI):

    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 inner join SMS_G_System_CUSTOM_COMPANY_MAINT_WINDOW_1_0 on SMS_G_System_CUSTOM_COMPANY_MAINT_WINDOW_1_0.ResourceID = SMS_R_System.ResourceId where SMS_G_System_CUSTOM_COMPANY_MAINT_WINDOW_1_0.ServiceWindowType = 1

    Servers with no assigned Maintenance Windows (WMI):

    (Change to CollectionID above).

    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.Active = 1 and SMS_R_System.ResourceId not in (select ResourceId from SMS_CM_RES_COLL_XXX000YY) and OperatingSystemNameAndVersion like ‘Microsoft Windows NT%Server%’