anyweb

sounds to me like the configmgr client agent version is older (like 1802) than the site version (1806) update it and you should be fine

With Microsoft Ignite just around the corner, Windows Server 2019 is set to get its full release and the signs look good. Very good. Unless you’re part of the Windows Server insider program - which grants you access to the latest Windows Server Preview builds - you probably haven’t had a hands-on experience yet with Windows Server 2019 but the guys over at Altaro have and are preparing to host a webinar on the 3rd of October to tell you all about it. The webinar will be held a week after Microsoft Ignite so it will cover the complete feature set included in the full release as well as a more in-depth look at the most important features in Windows Server 2019. Whenever a new version of Windows Server gets released there’s always a lot of attention and media coverage so it’s nice to have an hour-long session where you can sit back and let a panel of Microsoft experts cut through the noise and give you all the information you need. It’s also a great chance to ask your questions direct to those with the inside knowledge and receive answers live on air. Over 2000 people have now registered for this webinar and I’m going to be joining too. It’s free to register - what are you waiting for? Save your seat: https://goo.gl/aVmX2e

thanks, this guide is about installing the current baseline (1802 at time of writing) not upgrading, but sure, upgrade away ?

thanks ! you cannot add that account because that account is already a predefined Local Administrator,

open either of the 2 files (stored in C:\Windows\Inf) with notepad, and see what the driver actually is, that should help you pinpoint the problem

good point, @PaulWhite@pickens.k12 can you please share the configmgrprereq.log which detailed that your dp server OS was the issue please ? feel free to redact it

you'll need to create a custom script to detect where that original system is installed, and use that for the apply operating system step (using a variable), but read my first comment in this thread....

ah great to hear it, thanks for the update

have you made sure to distribute both 32 bit and 64 bit architecture boot images to your pxe enabled distribution point what does the smspxe.log reveal ?

did you browse to the link mentioned to see why ? and what does the Configmgrprereq.log say in the root of C:\

you are welcome, it was one of the more difficult thing I've gotten around to blogging, and I did it to understand the process better myself and to teach others, I've done the lab 3 times already and I know it works :-), if you follow the next in the series you can also configure SCCM with HTTPS, links below How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 1 How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 2

did Microsoft CSS explain why they thought your SQL was in such a bad state ?

thanks for posting the solution, your SQL server configuration was well messed up though.

more than likely yes

do you see any value in the registry key mentioned in the script ?

glad to hear it worked, what error did you get in PowerShell ISE as a matter of interest ?

you still have these issues, and until they are fixed there's no point trying to upgrade CONFIGURATION_MANAGER_UPDATE service is starting... $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Microsoft System Center Configuration Manager v5.00 (Build 8540) $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Process ID: 2844 $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Worker thread ID: 2868 $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Inbox source is local on abc.com $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Set inbox to C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> This running on active site server abc.com. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.024+240><thread=2868 (0xB34)> Inbox source is local on abc.com $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.040+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.165+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.165+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> *** Failed to connect to the SQL Server, connection type: SMS ACCESS. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> ExecuteSqlCMUpdateInitScripts: Can't get SQL connection $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.181+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> *** Failed to connect to the SQL Server, connection type: SMS ACCESS. $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> ERROR: Can not get InstallationType from SetupInfo $$<CONFIGURATION_MANAGER_UPDATE><08-21-2018 15:29:46.196+240><thread=2868 (0xB34)> Failed to initialize.

and if it's stuck on the upgrade then once again, share the logs (cmupdate.log)...

try restarting sms_executive and see does it kick into action

so are you still getting the errors ? is SQL on the same box as the primary or is SQL remote ?

does NT Authority\System have dbo connect permission in SQL ?

this is the most recent failure. System cannot connect to SQL, start troubleshooting it - https://support.microsoft.com/en-us/help/4009936/solving-connectivity-errors-to-sql-server

from the log there are several reports of SQL access issues, double check your permissions before trying again. *** [42000][4060][Microsoft] [SQL Server]Cannot open database "CM_MDC" requested by the login. The login failed.

please attach your cmupdate.log....

have you made sure it's got the latest bios ?