List of SCCM CB Prerequisite Checks via ConfigMgrPrereq

11
SCCM CB Prerequisite Checks

SCCM 1802 slow ring is released for all the environments which are on 1702 or later. The latest version of SCCM CB update should be available for all applicable environments. More details about the production version 1802 upgrade is explained in the video tutorial. SCCM CB prerequisite checks are very important to reduce the upgrade failures in the production environment.

I have listed down all the prerequisite checks included in the SCCM CB 1803 technical preview version. The SCCM CB prerequisite checks are noted down from the primary server. The sequence of prerequisite checks is traced from ConfigMgrPrereq.log file.

[Related PostWhat is the Secret Behind the Success of SCCM CB Updates and Servicing]

All the following SCCM CB prerequisite checks (rules) are not applicable in all scenarios. Following are some of the examples which I found in ConfigMgrPrereq.log file. I think some Prerequisite checks which are required for CAS server is not required for the primary server. The Same logic is applicable some scenarios like in-console update (updates & servicing – Easysetup), and fresh SCCM install.

Will run for easysetup upgrade
Or 
Is marked to not run for easysetup
Prerequisite rule 'SQL availability group replicas on default instance' will run for easysetup upgrade.
The rule 'SQL availability group replicas on default instance' has been run on server 'SCCMTP1.Intune.com', skipped.
Prerequisite rule 'Unsupported site system role 'Asset Intelligence synchronization point' for the LTSB edition' is marked to not run for easysetup.
Prerequisite rule 'Unsupported feature 'Cloud Distribution point' for the LTSB edition' is marked to not run for easysetup.

The prerequisite checks cover CAS, Primary servers, and remote site systems servers. It also includes SQL version, Collation settings, and Replication link verification. SCCM prerequisite checks consist of unsupported configurations (NAP, System Health Validation Point) and SCCM LTSB configuration with SCCM environment.

SCCM CB Prerequisite Checks – Rule Categories

SCCM CB primary server Rule Categories are listed down. These are the categories which I cracked down from ConfigMgrPrereq.log. However, Microsoft SCCM team will include new prerequisite checks with every new release of SCCM CB.

SCCM CB prerequisite checks are repeated for different site systems & servers before the start of the SCCM CB upgrade. This could vary depending upon your SCCM CB infra.

Access Permissions
System Requirements
Dependent Components
Site Upgrade Requirements
Database Upgrade Requirements

Rule Category: Access Permissions
Category Description: Checking access permissions

Prerequisite Rules

'Administrative rights on site system'
 'Administrative rights on central administration site'
 'Connection to SQL Server on central administration site'

SCCM CB Prerequisite Checks

Rule Category: System Requirements
Category Description: Checking system requirements for ConfigMgr/SCCM…

Prerequisite Rules

'Check Server Service is running'
 'Unsupported site server operating system version for Setup'
 'Domain membership'
 'Schema extensions'
 'Active Directory Domain Functional Level Check'
 'FAT Drive on Site Server'
 'Free disk space on site server'
 'Pending system restart'
 'Read-Only Domain Controller'
 'Site Server FQDN Length'

Rule Category: Dependent Components
Category Description: Checking dependent components for ConfigMgr…

Prerequisite Rules

'Microsoft XML Core Services 6.0 (MSXML60)'
 'WSUS on site server'
 'Windows Server 2003-based schannel hotfix'
 'Windows Remote Management (WinRM) v1.1'
 'Microsoft Remote Differential Compression (RDC) library registered'
 'Microsoft Windows Installer'
 'Existing Configuration Manager server components on site server'
 'Firewall exception for SQL Server'
 'Firewall exception for SQL Server (stand-alone primary site)'
 'SQL Server service running account'
 'Dedicated SQL Server instance'
 'SQL Index Create Memory option'
 'Parent/child database collation'
 'Minimum .NET Framework version for Configuration Manager site server'
 'PowerShell 2.0 on site server'
 'Windows Deployment Tools installed'
 'User State Migration Tool (USMT) installed'
 'Primary FQDN'
 'Verify site server permissions to publish to Active Directory.'
 'Site code in use'
 'Verify Central Administration Site Version'
 'Required SQL Server Collation'
 'SQL availability group configured for readable secondaries'
 'SQL availability group replicas on default instance'

Rule Category: Site Upgrade Requirements
Category Description: Checking if the target SCCM site is ready to upgrade…

Prerequisite Rules

'Unsupported operating system version for site system role'
 'Unsupported site server operating system version detected on a child site'
 'Backlogged inboxes'
 'Check for incompatible collection references'
 'Distribution point package version'
 'SQL Server database collation'
 'Share Name in Package'
 'Software update points in NLB Configuration'
 'Migration active source hierarchy'
 'Unsupported upgrade path'
 'Active Replica MP'
 'Parent site replication status'
 'Unsupported site system role 'Out of band service Point'
 'The System Health Validation Point site system role is no longer supported'
 'Network Access Protection (NAP) is no longer supported'
 'Verifying Database Consistency'
 'Custom Client Agent Settings have NAP enabled'
 'Default Client Agent Settings have NAP enabled'
 'SQL availability group configured for readable secondaries'
 'Unsupported site system role 'Asset Intelligence synchronization point' for the LTSB edition'
 'Unsupported feature 'Cloud Distribution point' for the LTSB edition'
 'Unsupported feature 'Microsoft Intune Subscription' for the LTSB edition'
 'Software Update Point using a Load Balancer (NLB/HLB) is no longer supported'
 'Using HTTP management point with cloud management gateway is not supported'

Insides of SCCM CB Prerequisite Checks

I have completed prerequisite checks for SCCM CB 1803 TP environment. All the required prerequisite checks are completed successfully.

Verifies that the logged on user account has administrative rights on the site system computer.
 Verifies that the user running Setup has local administrator rights on the central administration site server.
 Checks if the user account running Setup has sysadmin rights on the SQL Server for the CAS.
 Check Server Service (LanmanServer) is running.
 Verifies that the computer specified for installation is a member of a Windows domain.
 Verify that the Active Directory domain functional level is Windows Server 2003 or later.
 Checks that the site server computer has sufficient available disk space to install the site server.
 Checks if a system restart is pending.
 Checking unsupported Read-Only Domain Controller on site server.
 Checking Site Server FQDN Length.
 Verifies that the Microsoft Core XML Services (MSXML) version 6.0 or later libraries are installed.
 Determines if the Windows Server 2003-based schannel hotfix is installed on the site server.
 Verifies that the Microsoft Remote Differential Compression (RDC) library is registered on the computer specified for Configuration Manager site server installation.
 Checking Windows Installer Version >= 4.5.
 Checks if the target site server computer already has existing Configuration Manager server components installed.
 Checks if the Windows Firewall is disabled or if a relevant Windows Firewall exception exists for SQL Server.
 Check SQL Server service running account.
 Check to see if the selected SQL Server instance is already in use by another Configuration Manager site
 Verifies that the site server's database collation matches the database collation of its parent site.
 Verifies that the Microsoft .NET Framework version 3.5 is installed on Configuration Manager central administration site servers, primary site servers, and secondary site servers.
 Checks whether the Windows Deployment Tools component of Windows Assessment and Deployment Kit (ADK) for Windows 10 is installed.
 Checks whether the User State Migration Tool (USMT) component of Windows Assessment and Deployment Kit (ADK) for Windows 10 is installed.
 Checks if the FQDN provided for the site system uses the primary DNS hostname for the computer.
 Checks if the specified site code is already in use by another site in your hierarchy.
 Check the parent Central Administration Site has the same version.
 Verifies that the SQL Server instance and Configuration Manager site database (if present) are configured to use a supported collation.
 Verifies that the site server is processing critical inboxes in a timely fashion, and that inboxes do not contain files older than one day.
 Verifies that all distribution points in the site have the latest version of software distribution packages.
 Share Name in Package has invalid character
 Verifies that SUM is not using any virtual locations for active SUPs.
 Verifies that no active source hierarchy is currently configured for migration.
 Verifies that all site servers in the hierarchy meet the Configuration Manager minimum version that is required for upgrade.
 No Active MP Replica detected
 Verifies that the replication status of the parent site is Replication Active (corresponds to status=125).
 Checking that the site system role 'Out of band service point' is not deployed.
 Checking whether the site system role 'System Health Validator' exists in the hierarchy.
 Checking whether there are software updates that are enabled for NAP
 Pre-requisite rule to verify database consistency
 Verifies that the user account running Configuration Manager Setup has been granted sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation. SQL Server sysadmin role permissions are required in order to create the site database and configure necessary database role and login permissions for Configuration Manager sites.
 Verifies that the user account running Configuration Manager Setup has been granted sysadmin SQL Server role permissions on the SQL Server instance selected for reference site database installation. SQL Server sysadmin role permissions are required in order to modify the site database.
 Verifies that the site server computer account has administrative rights on the SQL Server and management point.
 Verifies that the version of Microsoft SQL Server installed on the computer selected to host the site database meets the minimum requirements.
 Checking the site SQL Server is not Express Edition.
 Checking the site SQL Server Tcp is enabled and set to Static port.
 Checks if the SQL Server hosting the Configuration Manager site database is using a case-insensitive collation.
 Check that the specified FQDN for the SQL Server computer is valid.
 Check target SDK machine is not Windows Cluster Node.
 Checks whether the Windows Preinstallation Environment component of Windows Assessment and Deployment Kit (ADK) for Windows 10 is installed.
 Checks if SMS Provider machine has same domain as site server.
 Checking whether there are custom Client Agent Settings that enable NAP
 Checking whether the default Client Agent Settings enable NAP
 Checking secondary read state of availability group replicas
 Checking failover state of availability group replicas
 Checking availability group replicas for instance configuration
 Checks if default value is set for SQL Index Create Memory
 Starting with version 1702, Configuration Manager does not support SQL Server 2008 R2.
 Starting with version 1702, Configuration Manager does not support Software Update Points on Loadbalancers (NLB/HLB).
 Starting with version 1706, Upgrade Assessment Toolkit is no longer supported.
 Verifies that the site system to be upgraded meets the minimum operating system requirement for site system installation.
 Checking if HTTP management point is enabled for cloud management gateway

11 COMMENTS

  1. Hello Anoop,
    I am facing an upgrade problem in my network, same problem with upgrading to 1802 from 1710 as upgrading to 1710 Hotfix Rollup (KB4086143) from 1710.
    The error msg is –
    ERROR: Failed to copy E:\Program Files\Microsoft Configuration Manager\CMUStaging\B9CE572A-C6A0-4E97-AC71-FE5AEFF99E6C\SMSSetup\OSD\bin\x64\CcmCore.dll to e:\program files\microsoft configuration manager\osd\bin\x64\ccmcore.dll, Win32 error = 0
    CONFIGURATION_MANAGER_UPDATE 2018-04-05 8:43:18 AM
    3596 (0x0E0C)
    The Prerequisite check is passed fine and all the upgrades is STATUS windows shows green till the “Install Files” section where it fails.
    I submitted this issue in Technet, but so far no one responded back. Any idea how to deal with the CCMCORE.DLL error ? Here is the link to the detailed case filed in Technet –

    https://social.technet.microsoft.com/Forums/Lync/en-US/debef288-9ee7-4bc2-b692-272c5951c224/configmgr-cb-1710-servicing-status-hotfix-rollup-kb4086143-installation-failure?forum=ConfigMgrCBGeneral

    Thanks in advance,
    Any help will be much appreciated.
    Regds,

  2. Hello Anoop,
    At last I did a change control today and restarted my Windows 2016 server (my SCCM Primary Site Server) and disabled the Defender (Real Time Protection) in it. Then tried the 1802 upgrade. But it failed again. No difference. Same thing – getting stuck at “Install Files” section.
    Do I have to first apply the 1710 Hotfix Rollup and then try the 1802, or it will make no difference ? If not any other idea ? Looks like I have hit the wall now. Not much help from the web (technet and other MVA forums) yet as I have the most recent combination which seems to be pretty rare in the industry now (Win Server 2016 + SQL Server 2016 + SCCM CB 1710) …

    Thanks and your help much appreciated.

  3. Hello Anoop,
    For both 1710 Hotfix and 1802 upgrade, the error msg in CMUpdate.log file is as below:


    >>INFO: Failed to check if file \\?\e:\program files\microsoft configuration manager\osd\bin\x64\ccmcore.dll exists (LastError=0x80070005). No zapping is done.
    >>INFO: Failed to zap the file \\?\e:\program files\microsoft configuration manager\osd\bin\x64\ccmcore.dll (LastError=0). will try to copy file again.
    >>Failed to reset the permission on \\?\e:\program files\microsoft configuration manager\osd\bin\x64\ccmcore.dll. LastError=0″
    >>ERROR: Failed to copy E:\Program Files\Microsoft Configuration Manager\CMUStaging\B9CE572A-C6A0-4E97-AC71-FE5AEFF99E6C\SMSSetup\OSD\bin\x64\CcmCore.dll to e:\program files\microsoft configuration manager\osd\bin\x64\ccmcore.dll, Win32 error = 0
    >>ERROR: Failed to copy E:\Program Files\Microsoft Configuration Manager\CMUStaging\B9CE572A-C6A0-4E97-AC71-FE5AEFF99E6C\SMSSetup\OSD\bin\x64\CcmCore.dll to e:\program files\microsoft configuration manager\osd\bin\x64\ccmcore.dll.”

    Looks like my Server 2016 ccmcore.dll file might have a problem. I tried to unregister and register it but did not work that good so far.

    Thanks again.

    • Hello Sub,

      Were you able to overcome the failed upgrade to 1802?

      If so, what was the issue and how did you resolve it?

  4. Do you have checlist for Migrating from SCCM 2012 R2 to 1802.

    Still server is 2008 r2 & SQL server 2008 R2. If you send the details with Prereq check tool if would be great

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.