jim.b

Yes! That would be mega helpful. I'm in California (PST). I can make time to work with yoo as this is a priority - LMK times that work. <removed email address>

Further, logged in as the administrator on the CM server (which hosts the sql just for this sccm,) I can issue "sqlcmd" and exec commands w/o error. Puzzled

I should mention I started the install process using a vanilla 2016 server for ADDS and a vm with pre-installed sql2014 for the CM server

Here's the tail of ConfigMgrSetup.log: INFO: 'USER-PC.CLDemo.local' is a valid FQDN. $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: Read SQL Data and Log file Path from script file if specified. $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: SQL Data file Path not specified, using default. $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: SQL Log file Path not specified, using default. $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: This isn't a named instance SQL Server. $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: SQL Server instance name (pSetupInf->SqlInstName): $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: SQL Server master database (pSetupInf->SqlMasterDB): master $$<Configuration Manager Setup><02-06-2019 12:07:58.719+480><thread=5748 (0x1674)> INFO: Site SQL Server database name (pSetupInf->SqlDatabaseName): CM_P01 $$<Configuration Manager Setup><02-06-2019 12:07:58.720+480><thread=5748 (0x1674)> INFO: Site SQL Server computer name (pSetupInf->SqlServer): USER-PC.CLDemo.local $$<Configuration Manager Setup><02-06-2019 12:07:58.720+480><thread=5748 (0x1674)> INFO: Site SQL Server Data File Path (pSetupInf->SqlDataFilePath): $$<Configuration Manager Setup><02-06-2019 12:07:58.720+480><thread=5748 (0x1674)> INFO: Site SQL Server Log File Path (pSetupInf->SqlLogFilePath): $$<Configuration Manager Setup><02-06-2019 12:07:58.720+480><thread=5748 (0x1674)> Failed to connect HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL registry key for reading on SQL Server [USER-PC.CLDemo.local]. $$<Configuration Manager Setup><02-06-2019 12:07:58.720+480><thread=5748 (0x1674)> ~~===================== Failed Configuration Manager Server Setup ===================== $$<Configuration Manager Setup><02-06-2019 12:08:03.278+480><thread=5748 (0x1674)> <02-06-2019 12:08:03> Failed to create process of SetupWpf.exe. return value 1 error is a pop-up window that it "could not connect or execute SQL query" manually my user on server can connect with windows credentials via SSMS and has sys admin priv. Don't know what it is using to connect. Stuck.

Sorry for last post - turns out it is not successfully connecting to sql - hidden msg box behind windows.... diagnosing.

Great stuff but I find my self unsure of the result. End of Part3 last step have: Looking for ConfigMgr media in 'C:\Source\SCCM1802'...done! skipping schema extension Checking for'C:\Source\SCCM_Prerequisites' folder...done! The folder 'C:\Source' already exists, will not recreate it. The file 'C:\Source\ConfigMgrAutoSave.ini' already exists, removing... Creating 'C:\Source\ConfigMgrAutoSave.ini'...done! installing SCCM (please wait)...done! Exiting script, goodbye. Did it install? Looks like it and it was quick... What process of file presence help me know as I'm no SCCM user... I do have suspicions about the files in C:\Source\SCCM1802 as looks like what is in C:\Source\SCCM_rerequisites. Thoughts? I've merged your many good ps1 scripts in to just a few. Nice. Just not sure of result.

Well, I'm a bit bummed I went thru Part1 and Part2 and there's scripts but no help on what order AND no Part 3???? I'll have to look back - did I miss an upfront warning/advisory? Doing it all via powershell.... if I find the order, I hope this works....