Thanks for reply. Apparently I am missing something.
When I execute sp_addserver @server ='TEST' -- I get the following error message:
Msg 15663, Level 16, State 1, Procedure sp_MSaddserver_internal, Line 60 [Batch Start Line 3]
Feature "sp_addserver" is no longer supported. Replace remote servers by using linked servers.
1. I am not able to update sys.servers or sys.sysservers for server_id =0 -- that is the (local) server; the reason I want to do that is that the name of the physical server / VM has been changed, but the old server name is retained in these two system tables in the [name] and [srvname] fields, respectively.
2. If I use sp_dropserver <old server name> -- note this is still functional in SQL Server 2016/Windows OS 2016, and I follow up with sp_addserver, I get the error message above and, of course, the two system tables no longer show any listing for server_id =0.
3. I am not trying to replace a 'remote' server; I'm trying to rename a 'local' server within the SQL Server system tables environment.
4. Is there a setting in the registry, where the old server name is persisted, or is that in SQL Server's resouce database, itself (which of course can't be touched) ?
I R Confused in 2016 !