Just to follow up... the log there, ConfiMgrPrereq.log, was littered with "ERROR: Failed to connect to SQL Server". Our Internet Security Office has recently been cracking down on TLS 1.0 available servers. Our SCCM runs in HTTPS only mode. Aside from 2008 clients not being able to connect past TLS 1.0, it appears the prereq checker can't either. On my test installs of SCCM I had enabled TLS 1.2 only on the server side, testing the new requirement. Looks like the prereq checker executable doesn't support TLS 1.2. I reverted back to enabling TLS 1.0 server and everything worked as expected.
So, to update SCCM and support Server 2008 I'll just have to tell the ISO that I have to have TLS 1.0, and to please not quarantine our SCCM servers. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Tuesday, April 11, 2017 7:23 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: 1702 prereq check fails Check the logs on the root of the site server. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Mote, Todd Sent: Tuesday, April 11, 2017 8:08 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] 1702 prereq check fails In a weird way. I have 4 total installs, one is prod, one is qual, and the other two are places where I test stuff like upgrading. All on Server 2012 R2 single site server, all roles on the same server, SQL 2016 no SP, though I might give SP1 a try given some of the failures, all but prod are 1610, but the prereq check on all three of the non-prod ones fail with some strange results. I haven't run the prereq check on prod yet. All three list the same failures. Is there a log somewhere I can look at with more information that what's provided in the checker? Todd [Failed]:Verifies that the site system to be upgraded meets the minimum operating system requirement of Windows Server 2008 R2 for site system installation. (all are 2012 R2 fully patched) [Failed]:Verifies that the SQL Server database collation settings of the tempdb database and site database to be upgraded are the same. (but they are, I checked) [Failed]:Verifies that no active source hierarchy is currently configured for migration. (these haven't been migrated from or to any other hierarchy, all single installs) [Failed]:Verifies that all site servers in the hierarchy meet the Configuration Manager minimum version that is required for upgrade. (this is the only site servers and they are all 1610) [Failed]:No Active MP Replica detected (I have no replicas) [Failed]:Checking whether the site system role 'System Health Validator' exists in the hierarchy. (this role is not installed) [Failed]:Checking whether there are software updates that are enabled for NAP (never used NAP with SU, or at all) [Failed]: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. (the user I'm using has SA) [Failed]:Checking whether there are custom Client Agent Settings that enable NAP (two of the sites don't have custom client settings but all of them have this failure) [Failed]:Checking whether the default Client Agent Settings enable NAP (I can't find NAP in the default client settings) The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
