Advanced settings is disabled while running prod config & removing and adding 2 DC server to the farm

sns 9,226

I want to remove 2 distributed cache servers from the farm. and adding those 2 servers to farm as there issue with Distributed cache issue with these 2 DC servers.

FY: we have 2 app , 2 wfe , 2 search , 2 DC servers , it is 2016 farm

in process of removing these 2 DC servers I am seeing Advanced settings option is disabled while running config wizard.

Account I am using to perform this operation is present in the farm admin group, then what is the issue?, why advanced settings option is disabled.

Please suggest how to fix this, thak you

1 answer

Emily Du-MSFT 41,771 Reputation points Microsoft Vendor

2023-05-22T08:49:25.9333333+00:00

According to this Microsoft article, by default, Advanced Settings is disabled in the SharePoint 2016.

The Advanced Settings option is not available in SharePoint Servers 2016 and 2019.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
sns 9,226 Reputation points

2023-05-22T09:44:03.6433333+00:00

Hi Emily Du,

In that case how do we add the Distrubbuted cache server to farm?

becuse advannced settig is disabled while running wizard

Emily Du-MSFT 41,771 Reputation points Microsoft Vendor

2023-05-25T09:37:59.54+00:00

1.Add a new server in the VMs.

2.Join the new server into the domain.

3.Run the SharePoint PrerequisiteInstaller for installing the prerequisites.

4.Run the SharePoint 2016 Products Configuration Wizard as administrator, on the "Connect to a server farm" page, click "Connect to an existing server farm".

5.In the Specify Server Role page, choose Distributed cache role.

Emily Du-MSFT 41,771 Reputation points Microsoft Vendor

2023-05-30T08:39:24.28+00:00

Any issues about how to add Distributed cache server into SharePoint farm?

If there is any problem, please feel free to let me know.

sns 9,226 Reputation points

2023-05-31T16:38:00.2733333+00:00

Hi EMily Du,

We have 2 Distributed servers, example x, y servers are 2 Distributed servers

We want to remove this server, we removed one Distrubuted server from system settings, manager server option.

however if we want to add that back again , when we run the product config wizard advanced settings option is disabled. so we are not able to proceed.

I am not finding option to add the server in to the farm.

what we noticed

system settings -> manage servers --> DB server name is: DBSP2016TST

When we connect to SQL server , while connecting SQL studio server name it is showing SP2016TST

We verified below:

First command is from SharePoint PowerShell Get-SPDatabase | Select Name,Server . All web applications and service applications were showing "DBSP2016TST" as the database server name instead of "SP2016TST".

Second command in SQL server database, to get the distributed cache configuration. SELECT [ID],[Properties] FROM [SharePoint_Config].[dbo].[Objects] WITH (NOLOCK) WHERE Properties like '%_cacheConfigStorageLocation%' This one to retrieve the properties of the distributed cache which is stored in the configuration database and also pointing to "DBSP2016TST" instead of "SP2016TST".

so 2 months ago SQL team migrated Databases from GS1015 to GS1020

I am logging to SQL server GS1020 which is showing SP2016TST while connecting. so this is fine. and at that SQL team and AD team updated DNS in the backend.

Now when we click on maanged content databases and verified all SharePoint and Nintex content databasesshowing DBSP2016TST

Please clarify my following 6 questions:

1.

We got suggestion to change from DBSP2016TST to SP2016TST in SQL server by using update query, is there any impact for SharePoint applications and Nintex applications by doing so? and this is calling updating SQL alias? am I correct?

2.

once we done in SQL server and we supposed to update new SQL alias in all SharePoint servers , we are following document below. Does it have any impact? Do we need to reboot the servers? what are the precautions when we do this?

https://learn.microsoft.com/en-us/sharepoint/troubleshoot/administration/how-to-change-the-database-in-farms

is because of SQL is pointing to old SQL alias, we are not able to see advanced settings option while running the prod config wizard?

please provide me high level steps of doing this

Does it have any impact SharePoint and Nintex databases , we have 22 content databases, 2 nintex databases.

how come CA is loading and application and site are working fine and loading fine when still it is pointing to old SQLAlias which is DBSP2016TST

Thank you for the support
Sign in to comment