Change collation of sql2017 when freshly installed.

Yes, since it’s a new install and has no production databases just the database installed by the SQL install, we don’t need to rebuild right?

The databases that gets installed with a fresh new SQL don’t need rebuild?

If change collation as recommended by David, we will not lose any configurations, logins and any other server objects like linked servers?

Yes, it will need a rebuild so yes, you'll lose all configurations from the SQL Server instance.
User databases have their own collation (usually from the SQL Server instance where they were created) but changing a database collation only affects the current database and not the SQL Server instance.

Understood, can you provide some link to full rebuild of the system databases.

@victor the commands given do not require a rebuild

A few days ago, I came across an issue where we had to change the SQL server instance collation and we were just asking the clients to rebuild the system databases to do so in the previous cases. But this time the client could not afford to do that and asked for a plan B.

Ok.  Note the new sql install has no working database, just the system database that it install with a new installation.

@David, I read that article but it's hard to me to believe that a SQL Server instance collation change doesn't need a rebuild. Of course rayluvs should give a try to confirm that. Unfortunately I don't have any available SQL Server instance to play with the -q parameter (btw, I checked in MSDN and couldn't find that parameter. It might be one of the hidden ones).

raylus, can you tell us if the SQL Server instance has been rebuilt or not?
I would like to confirm that the -q parameter doesn't rebuild the SQL Server instance, i.e., you don't loose any server object during the process.

No (seems to work fine)

Thank you for the confirmation.