SOLVED SCCM 2016 - Unable to deploy Secondary Site

[GordonM]

Hi All,

Firstly, I would like to thank Prajwal for his site! - without the information contained within, I doubt I would have obtained the knowledge in regards to SCCM as I do have now.

I am currently experiencing some issues when deploying a Secondary site via SCCM 2016

Although the messages are quite straight forward, I have been racking my brain trying to figure out what the issues are and have been unable to do so for the last 2 weeks

My set-up is as follows:

Site Server
- Windows Server 2012 R2
- Microsoft SQL Server 2016 - Fully Patched
- SCCM 2016 build 1610

- Issue1
-- [Failed]:The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.

I have created a "Domain Service Account" and SQL server is running under the Domain Service account and the SPN has been registered.

- Issue2
-- [Warning]:SQL Index create memory is not configured as default value of 0 and might hit issue

This as being a warning, I have not spent too much time upon, but it seems straighforward

- Issue3
-- [Failed]:The collation of the site database does not match the collation of the parent site's database. All sites in a hierarchy must use the same database collation.

Having run the following command on both the Primary site and the Secondary site (which is what I am trying to deploy) - SELECT CONVERT (varchar, SERVERPROPERTY('collation'));
I can see the collation is the same on both sites and thus I am confused
- Primary Site = SQL_Latin1_General_CP1_CI_AS
- Secondary Site = SQL_Latin1_General_CP1_CI_AS

- Issue4
-- [Failed]:Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.

I am running this via my SCCM account that is what I used with the Primay Site

I have been spending some time trying to get this solved and it's slowly making me wonder what I am doing wrong

Thanks to all for your assistance

 

[GordonM]

**UPDATE**

Issue1 & Issue3 have been resolved - It would appear to be a PICNIC (Problem In Chair Not In Computer) Issue
- During the installation, the wizard requests the name of the SQL Instance and by wanting to do the right thing, I entered "MSSQLSERVER" in the value box, but it's required to be empty in order to use default instance

Sharing my experiences for others to learn not to make the same mistake I have

Gordon

 

[GordonM]

**UPDATE**

Issue4 has also now since been resolved.

The "NT AUTHORITY\SYSTEM" required "SysAdmin" rights on SQL

All my "problems" I say this whilst blushing, have now been resolved.

Gordon