When you are carrying out a Configuration Manager upgrade did you ever wonder what "Run Prerequisite Check" actually means?
I did so I had a look. This is the list of prerequisite checks while upgrading from ConfigMgr CB 1511 to 1602. It's quite a comprehensive list.
[Passed]:Prerequisite
check starting
[Passed]:Verifies
that the logged on user account has administrative rights on the site system
computer.
[Passed]:Verifies
that the user running Setup has local administrator rights on the central
administration site server.
[Passed]:Checks if
the user account running Setup has sysadmin rights on the SQL Server for the
CAS.
[Passed]:Check
Server Service (LanmanServer) is running.
[Passed]:Verifies
that the computer specified for installation is a member of a Windows domain.
[Passed]:Verify that
the Active Directory domain functional level is Windows Server 2003 or later.
[Passed]:Checks that
the site server computer has sufficient available disk space to install the
site server.
[Passed]:Checks if a
system restart is pending.
[Passed]:Checking
unsupported Read-Only Domain Controller on site server.
[Passed]:Checking
Site Server FQDN Length.
[Passed]:Verifies
that the Microsoft Core XML Services (MSXML) version 6.0 or later libraries are
installed.
[Passed]:Determines
if the Windows Server 2003-based schannel hotfix is installed on the site
server.
[Passed]:Verifies
that the Microsoft Remote Differential Compression (RDC) library is registered
on the computer specified for Configuration Manager site server installation.
[Passed]:Checking
Windows Installer Version >= 4.5.
[Passed]:Checks if
the target site server computer already has existing Configuration Manager
server components installed.
[Passed]:Checks if
the Windows Firewall is disabled or if a relevant Windows Firewall exception
exists for SQL Server.
[Passed]:Check SQL
Server service running account.
[Passed]:Check to
see if the selected SQL Server instance is already in use by another
Configuration Manager site
[Passed]:Verifies
that the site server's database collation matches the database collation of its
parent site.
[Passed]: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.
[Passed]:Checks
whether the User State Migration Tool (USMT) component of Windows Assessment
and Deployment Kit (ADK) for Windows 8.1 is installed.
[Passed]:Checks if
the FQDN provided for the site system uses the primary DNS hostname for the
computer.
[Passed]:Checks if
the specified site code is already in use by another site in your hierarchy.
[Passed]:Check the
parent Central Administration Site has the same version.
[Passed]:Verifies
that the SQL Server instance and Configuration Manager site database (if
present) are configured to use a supported collation.
[Passed]:Verifies
that the site server is processing critical inboxes in a timely fashion, and
that inboxes do not contain files older than one day.
[Passed]:Verifies
that all distribution points in the site have the latest version of software
distribution packages.
[Passed]:Verifies
that the SQL Server database collation settings of the tempdb database and site
database to be upgraded are the same.
[Passed]:Share Name
in Package has invalid character: #.
[Passed]:Verifies
that SUM is not using any virtual locations for active SUPs.
[Passed]:Verifies
that no active source hierarchy is currently configured for migration.
[Passed]:Verifies
that all site servers in the hierarchy meet the Configuration Manager minimum
version that is required for upgrade.
[Passed]:Active MP
Replica detected
[Passed]:Verifies
that the replication status of the parent site is Replication Active
(corresponds to status=125).
[Passed]:Checking
that the site system role 'Out of band service point' is not deployed.
[Passed]:Checking
whether the site system role 'System Health Validator' exists in the hierarchy.
[Passed]:Checking
whether there are Software Updates that are enabled for NAP
[Passed]:Pre-requisite
rule to verify database consistency
[Passed]: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.
[Passed]: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.
[Passed]:Verifies
that the site server computer account has administrative rights on the SQL
Server and management point.
[Passed]:Verifies
that the version of Microsoft SQL Server installed on the computer selected to
host the site database meets the minimum requirements.
[Passed]:Checking
the site SQL Server is not Express Edition.
[Passed]:Checking
the site SQL Server Tcp is enabled and set to Static port.
[Passed]:Checks if
the SQL Server hosting the Configuration Manager site database is using a
case-insensitive collation.
[Passed]:Check that
the specified FQDN for the SQL Server computer is valid.
[Passed]:Check
target SDK machine is not Windows Cluster Node.
[Passed]:Checks
whether the Windows Deployment Tools component of Windows Assessment and
Deployment Kit (ADK) for Windows 8.1 is installed.
[Passed]:Checks
whether the Windows Preinstallation Environment component of Windows Assessment
and Deployment Kit (ADK) for Windows 8.1 is installed.
[Passed]:Checks if
SMS Provider machine has same domain as site server.
[Passed]:Prerequisite
check complete with no warnings or failures
Until next time.....
Hi Gerry,
ReplyDeleteI left a comment yesterday but it has not been published,
I have SCCM Current Branch on 1602, I have moved the SQL database to SQL 2016 and all is well, one issue is that the server cannot see any updates using the in console updater, my understanding is it should see 1607, dmpdownloader.log has no errors and is contacting the microsoft download site but says there is no update,
Any ideas would be greatly appreciated,
Thanks,
Neil
No, you won't see 1607 Neil. That is a Technical Preview. You should be able to see 1606. It was previously released to fast ring only and maybe that's why you didn't see it. You have to run a PoSH script to opt into fast ring. You should see it now though. It was released GA yesterday.
DeleteThanks for your response Gerry I ran this https://gallery.technet.microsoft.com/ConfigMgr-1606-Enable-043a8c50
ReplyDeleteand it can now see 1606,
Although the upgrade/install was greyed out, I had to remove an offending 1602
hotfix from both the file system and SQL, then it would let me install 1606,
Will you be doing walkthrough's/knowledge transfer on SCCM 2016?
Cheers,
Neil
No worries Neil. I will continue blogging about new ConfigMgr versions. However I'm not sure that there will be a 2016 version. We'll have to wait and see.
ReplyDeleteThanks Gerry, I'm sure you have your ear to the ground but my understanding was
ReplyDeleteall the System Center Technical Previews, DPM, SCCM, SCOM would become 2016 versions at the end of next month when Microsoft release them for GA?
Cheers Neil
my understanding was that configuration manager 1511 requires minimum 2008 domain functional level
ReplyDelete