Jump to content


anyweb

How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 - Part 3

Recommended Posts

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.

 

 

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.