Переименование названия сервера Windows 2012R2 Server

Каждый сервер MS Windows должен иметь уникальное имя, чтобы уникальным образом идентифицироваться в рамках своей сети. Чтобы оперативно дать нужное имя серверу в командной строке, с помощью команды netdom:

C:\>netdom / renamecomputer Server1 / newname : Server2

This operation will rename the computer Server1
to Server2
Certain services , such as the Certificate Authority, relyon а fixed
machine name . If any services of this type a re running оп
Server1, then а computer name change would have an adverse impact.
Do you want to proceed (Y or N)
Y
The computer needs to bе restarted in order tо complete the operation.
The command completed successfully .

Эта операция переименует компьютер Server1 на Server2. Будьте осторожны, некоторые службы, такие как центр сертификации, полагаются на фиксированные имена машин. Если на сервере под именем Server1 работают службы такого типа, то изменение имени компьютера может иметь неблагоприятное последствия.
Желаете ли вы продолжить (У(да) N(нет)) ?
у (да).
Для завершения операции компьютер необходимо перезапустить.
Команда успешного завершения.
С : \ >
Ниже приведен синтаксис команды netdom:

netdom /renamecomputer / newname :

После выполнения netdom команд, обязательно понадобится перезагрузить сервер.

Изменение имени зарегистрированного сервера или зарегистрированной группы серверов Change the Name of Registered Server or Registered Server Group

Применимо к: Applies to: SQL Server SQL Server (все поддерживаемые версии) SQL Server SQL Server (all supported versions) База данных SQL Azure Azure SQL Database База данных SQL Azure Azure SQL Database Управляемый экземпляр SQL Azure Azure SQL Managed Instance Управляемый экземпляр SQL Azure Azure SQL Managed Instance Azure Synapse Analytics Azure Synapse Analytics Azure Synapse Analytics Azure Synapse Analytics Параллельное хранилище данных Parallel Data Warehouse Параллельное хранилище данных Parallel Data Warehouse Применимо к: Applies to: SQL Server SQL Server (все поддерживаемые версии) SQL Server SQL Server (all supported versions) База данных SQL Azure Azure SQL Database База данных SQL Azure Azure SQL Database Управляемый экземпляр SQL Azure Azure SQL Managed Instance Управляемый экземпляр SQL Azure Azure SQL Managed Instance Azure Synapse Analytics Azure Synapse Analytics Azure Synapse Analytics Azure Synapse Analytics Параллельное хранилище данных Parallel Data Warehouse Параллельное хранилище данных Parallel Data Warehouse

В этом разделе описывается изменение имени зарегистрированного сервера или группы серверов в SQL Server SQL Server с помощью среды SQL Server Management Studio SQL Server Management Studio . This topic describes how to change the name of a registered server or server group in SQL Server SQL Server by using SQL Server Management Studio SQL Server Management Studio . Это имя может быть изменено в любое время. The name can be changed at any time. Изменение имени сервера для зарегистрированных серверов изменяет только отображение имени. Changing the name of a server in Registered Servers only changes how the name is displayed. Чтобы подключиться к другому серверу, необходимо изменить свойства соединения зарегистрированного сервера. To connect to a different server, you must edit the connection properties of the registered server.

Использование среды SQL Server Management Studio Using SQL Server Management Studio

В меню перейдите к Вид\Зарегистрированные серверы открыть панель Зарегистрированные серверы. From the menu navigate to View\Registered Servers to open the Registered Servers pane.

Изменение имени сервера To change the name of a server

В списке Зарегистрированные серверы разверните узел Ядро СУБД и затем узел Группы локальных серверов. In Registered Servers, expand Database Engine and then Local Server Groups.

Щелкните правой кнопкой мыши сервер и выберите Свойства , чтобы открыть диалоговое окно Изменение данных регистрации серверов . Right-click a server and select Properties to open the Edit Server Registration Properties dialog window.

В поле Имя зарегистрированного сервера введите новое имя для регистрации сервера и нажмите кнопку Сохранить. In the Registered server name text box, type the new name for the server registration, and then click Save.

Изменение имени группы серверов To change the name of a server group

В списке Зарегистрированные серверы разверните узел Ядро СУБД и затем узел Группы локальных серверов. In Registered Servers, expand Database Engine and then Local Server Groups.

Щелкните правой кнопкой мыши группу серверов и выберите Свойства , чтобы открыть диалоговое окно Изменение свойств группы серверов . Right-click a server group and select Properties to open the Edit Server Group Properties dialog window.

В поле Имя группы введите новое имя для группы серверов и нажмите кнопку Сохранить. In the Group name text box, type the new name for the server group, and then click Save.

Change server name windows server

(1 row(s) affected)

(1 row(s) affected)

name network_name status id collation_name connect_timeout query_timeout

NewName NewName rpc,rpc out,use remote collation 0 NULL 0 0

Msg 15015, Level 16, State 1, Procedure sp_dropserver, Line 42

The server ‘OldName’ does not exist. Use sp_helpserver to show available servers.

Msg 15028, Level 16, State 1, Procedure sp_addserver, Line 74

The server ‘NewName already exists.

Does anyone know of an alternate method to change correct the content of @@SERVERNAME and where, if anywhere, is this data derived from in the system tables?

Thanks in advance for your assistance

Все ответы

Madhu MCITP, MCTS, MCDBA,MCP— Blog : http://experiencing-sql-server-2008.blogspot.com/

Thank you for the suggestion but this link describes the process which as I said above did not work for me. Another interesting thing we ran into with these copied virtual machines is that we could not set up replication with them in that state. It would not allow us to create a publication, all the time throwing an error that it was trying to connect to the initial machine instance name.

I have however uncovered a way to resolve the problem through modifying a registry key (insert usual disclaimers here about modifying the registry at your own risk).
The registry key in question is
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Machines\OriginalMachineName

I changed the value of this key to ‘NewName’, rebooted the virtual machine and we were good to go, both as far as the value returned when doing a SELECT @@SERVERNAME as well as being able to create publications for replication.

I hope others will find this information useful

Change server name windows server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have a problem upgrading a McAfee ePolicy Orchestrator which uses SQL Server 2008 R2 SP2. McAfee logs indicate that server names from SQL server and from McAfee installer does not match.

It seems that the reason is that machine name was changed after SQL Server was installed.

MSDN instructions for sql server name changing give next commands to solve this problem:

SELECT @@SERVERNAME AS ‘Server Name’;

sp_dropserver

;
GO
sp_addserver , local;
GO

But it didn’t work for me, because «SELECT @@SERVERNAME AS ‘Server Name'» shows correct (actual) name of sql server. So sp_dropserver says that there is now such instance.

In the same time if I use this commands:

I get old (not actual) name.

epo-server is an actual computer name

WIN-VUN5TSKAHG1 is an old name.

Answers

• Marked as answer by Lydia Zhang Microsoft contingent staff Wednesday, June 10, 2015 1:20 AM

All replies

Basically you cannot rename a named instance of SQL Server.

Essentially for any named instance on the Server you will need to uninstall then reinstall these instances.

Please click «Mark As Answer» if my post helped. Tony C.

after rename ,have restart sql instance ?

Hello ! Can you try this and post back your results to check if this works for you:

Good Luck!
Please Mark This As Answer if it solved your issue.
Please Vote This As Helpful if it helps to solve your issue

You can not rename instance without uninstalling and re-installing SQL Server. The steps you did and mentioned by other people in this post are for renaming your computer that is running SQL Server database engine.

I don’t know why people has answered it in-correctly(may be by quickly searching on Google); but this information is incorrect, you can not rename an instance in SQL Server (there is no such command), you can only rename the server.

But you can create another instance -> Move your database etc. — > delete old instance.

Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.

You can not rename instance without uninstalling and re-installing SQL Server. The steps you did and mentioned by other people in this post are for renaming your computer that is running SQL Server database engine.

I don’t know why people has answered it in-correctly(may be by quickly searching on Google); but this information is incorrect, you can not rename an instance in SQL Server (there is no such command), you can only rename the server.

But you can create another instance -> Move your database etc. — > delete old instance.

Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.

Anuj — Instance Name for Named Instance cannot be changed however assuming that ComputerName1\InstanceName needs to be changed to ComputerName2\InstanceName so this can be definitely achieved after all we are only concerned with changing the Server Name (Host Name or Machine Name), the second part of it still remains same.

If you look at the post which says » It seems that the reason is that machine name was changed after SQL Server was installed.» I do not think the possible solutions given by us anywhere contradicts.

MS Quote:

«you can change a computer named MB1 that hosts an instance of SQL Server named Instance1 to another name, such as MB2. However, the instance part of the name, Instance1, will remain unchanged. In this example, the \\ ComputerName \ InstanceName would be changed from \\MB1\Instance1 to \\MB2\Instance1.»

Are we missing anything ?

Good Luck!
Please Mark This As Answer if it solved your issue.
Please Vote This As Helpful if it helps to solve your issue

Just a Random Microsoft Azure and Computing Tech info

You can use the domain rename process to change the names of your domains, and you can also use it to change the structure of the domain trees in your forest. This process involves updating the Domain Name System (DNS) and trust infrastructures as well as Group Policy and service principal names (SPNs).

The ability to rename domains provides you with the flexibility to make important name changes and forest structural changes as the needs of your organization change. Using domain rename, you cannot only change the name of a domain, but you can change the structure of the domain hierarchy and change the parent of a domain or move a domain residing in one domain tree to another domain tree. The domain rename process can accommodate scenarios involving acquisitions, mergers, or name changes in your organization, but it is not designed to accommodate forest mergers or the movement of domains between forests.

Note:
Domain rename is intended to be a supported method for renaming domains when domain renames are necessary; it is not intended to make domain rename a routine operation. The domain rename process is complex, and it requires a great deal of care in planning and execution. In addition, the time that is required for a complete domain rename operation is directly proportional to the size of an Active Directory forest in terms of its number of domains, domain controllers, and member computers. Therefore, although domain rename is possible, it should not be undertaken lightly. The domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010. DNS domain rename is supported in Exchange Server 2003. However, renaming of the NetBIOS domain name is not supported in any version of Exchange Server. Other non-Microsoft applications might also not support domain rename.

For this time easy Guide, I will show you all how to rename domain name in Windows Server 2016, the process is straightforward. but as usual. backup any necessary information and Server before you proceed & I always advice, please do this exercises in LAB Environment (Hyper-V). Don’t simply take any risk by doing this is production environment unless you have to. 😦

The existing domain is Windows.ae and I will rename it to Sifad.local

So, let get started.

1 – Open your System Properties and check your existing domain name, if you see from my Windows Server 2016 system properties, my existing domain name is Windows.ae. This will be change to Sifad.local in the short while.

2 – Next, open your Server Dashboard, go to Tools & click DNS to open DNS Manager.

3 – on the DNS Manager, you must create the New DNS Zone (Sifad.local), this is to make -sure that after whole process successfully, your member server and Windows clients can join to new Domain name.

“to create new DNS Zone, Right Click Forward Lookup Zone, and click New Zone”

4 – On the Welcome to the New Zone Wizard, just click Next button.

5 – On the Zone Type, Click Primary Zone and click Next.

6 – On the Active Directory Zone Replication Scope, click button To all DNS servers running on domain controllers in this domain: Windows.ae and click Next.

7 – In the Zone Name, key in your New Domain Name, my new Domain Name is Sifad.local.

8 – On the Dynamic Update, Click Allow only secure dynamic updates (recommended for Active Directory), and click Next.

9 – On the completing the New Zone Wizard, click Finish to complete the process.

10 – On DNS Manager, you can see my new Domain Name is listed (sifad.local).

11 – Next, open Command Prompt, run as administrator.

12 – In CMD, type rendom /list and press enter – this command use to generate a state file named Domainlist.xml. This file contains the current forest configuration.

13 – Next, open computer and browse to C:\Users\Administrator folder to get your Domainlist.xml.

14 – Once you see the Domainlist.xml, right click the file name & choose Edit. I going to change the DNSname and NetBiosName in this Domainlist.xml file.

15 – Once the Domainlist.xml open, you can see there are few existing Domain name, change this existing domain name to new domain name. (Refer to picture)

16 – once you change to new Domain name, make sure you save the Domainlist.xml file.

17 – After you save the Domainlist.xml file, On the CMD, type rendom /showforest. This is to show the potential changes; this step does not make any changes.

18 – Next, type rendom /upload. This is to upload the rename instructions (Domainlist.xml) to the configuration directory partition on the domain controller holding the domain naming operations master role.

19 – Next, type rendom /prepare. This use to verify the readiness of each DC in the forest to carry out the rename instructions. This should contact all DC’s successfully and return no errors before proceed to next process.

20 – Next, type rendom /execute. This is to verifies readiness of all DC’s and then preforms the rename action on each one.

“Remember also there will be a service interruption during this process. Once the process successful, your DC Server will be restarted.”

21 – Once your DC Server restarted, log in using the new Domain name as Administrator.

22 – Next, after you successfully log in, open System Properties and check your old Domain Name is now gone. replace by new Domain name.

23 – Next, open CMD again, and type gpfixup /olddns:windows.ae /newdns:sifad.loca l This is to refresh all intra Domain references and links to group policy objects.

24 – Next, type gpfixup /oldnb:DC-CLOUD /newnb:sifad.

25 – Next, type rendom /clean. This is to remove references of the old domain name from AD.

26 – Next, type rendom /end. This is to unfreeze the forest configuration and allow further changes. This was frozen during the rendom /upload step.

27 – Next, Open DNS Manager, click your new created domain (Sifad.local), here you can see your own IP listed but we still have long way to go to make sure this DNS Zone is working.

28 – Next, turn on your client PC, for this exercise I’m using Windows 10 as a client. Open System Properties and join to new Domain (sifad.local). Windows Security box will show up and now key in administrator and domain password and click OK (Welcome to the sifad.local domain). (Refer pictures)

29 – After your Windows 10 restart, log in as a domain administrator.

30 – Once you log in, double check Windows 10 System Properties. Now your Windows 10 successfully join in to new Domain (Sifad.local).

31 – Now, go to the Server 2016 and open DNS Manager, you can see now your Windows 10 Client is listed in DNS.

32 – You can also check in Active Directory Users & Computers that your Windows 10 Client now also listed.

This ends the rename process and we have a dc now with a new domain name.

that’s all for now. any Doubts type a commend.. 🙂