anyweb

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 ?

can you explain what you mean by " due to home lab situation. "

I assume you upgraded the CAS first and then the PRI, are there any errors at all in the cmupdate.log that you think may be important on either site ?

if i have the energy and time this week (doubt it) I might try and test this for you...

nope haven't had time yet, what if anything do the logs tell you ? what adk are you using ?

good troubleshooting !

hi are you seeing this after completing my 8 part lab ?, I've booted mine up, and verified on the IssuingCA as EntAdmin with pkiview that everything looks good, and it still does after leaving it running for a day, i'd suggest you start at the beginning again and work your way through it, it's a good exercise anyway, take snapshots after completing each Part, so that you can always revert if there's an issue later.

4gb should be ok but i would put a pause before the install offline language step and after to analyze logs to see what's happening.. here's one way - also try and move to a supported scenario, as it's impossible to say if this is because you are running unsupported right now...without me too trying it, and i don't have time, sorry

hmm you are using adk 1803 to deploy windows 10 1607 images ? i don't think that's supported, but aside from that, how much ram is in these computers and have you also updated the mdt integration to a newer release ? are you really still deploying windows 10 1607 it's eol in November

did you try rebooting the cas & pri to see if it makes any difference ?

take a look at this old post to give you some ideas of where you are going wrong

yes you can do that, but if you are installing more than one language then you must include all the language packs you intend to install together

Microsoft has introduced support for the Web Authentication specification in Microsoft Edge, enabling better, more secure user experiences and a passwordless experience on the web. With Web Authentication, Microsoft Edge users can sign in with their face, fingerprint, PIN, or portable FIDO2 devices, leveraging strong public-key credentials instead of passwords. A web without passwords Staying secure on the web is more important than ever. We trust web sites to process credit card numbers, save addresses and personal information, and even to handle sensitive records like medical information. All this data is protected by an ancient security model—the password. But passwords are difficult to remember, and are fundamentally insecure—often re-used, and vulnerable to phishing and cracking. For these reasons, Microsoft has been leading the charge towards a world without passwords, with innovations like Windows Hello biometrics and pioneering work with the FIDO Alliance to create an open standard for passwordless authentication – Web Authentication. We started this journey in 2016, when we shipped the industry’s first preview implementation of the Web Authentication API in Microsoft Edge. Since then, we have been updating our implementation to as we worked with other vendors and the FIDO alliance to develop the standard. In March, the FIDO Alliance announced that the Web Authentication APIs have reached Candidate Recommendation (CR) status in the W3C, a major milestone for the maturity and interoperability of the specification. Authenticators in Microsoft Edge Beginning with build 17723, Microsoft Edge supports the CR version of Web Authentication. Our implementation provides the most complete support for Web Authentication to date, with support for a wider variety of authenticators than other browsers. Windows Hello allows users to authenticate without a password on any Windows 10 device, using biometrics—face and fingerprint recognition—or a PIN number to sign in to web sites. With Windows Hello face recognition, users can log in to sites that support Web Authentication in seconds, with just a glance. Users can also use external FIDO2 security keys to authenticate with a removable device and your biometrics or PIN. For websites that are not ready to move to a completely passwordless model, backwards compatibility with FIDO U2F devices can provide a strong second factor in addition to a password. via > https://blogs.windows.com/msedgedev/2018/07/30/introducing-web-authentication-microsoft-edge