• Windows Server 2003 Sp3 Download

Use Netdom.exe to Reset a Machine Account Password Install the Windows Server 2003 Support Tools on the domain controller whose password you want to reset. These tools are located in the Support Tools folder on the Windows Server 2003 CD-ROM. Domain Manager - Manage Machine Accounts and Passwords. NETDOM ADD Add a workstation or server account to the domain NETDOM COMPUTERNAME Manage computer names NETDOM HELP Display help NETDOM JOIN Join a workstation or member server to the domain NETDOM MoveNT4BDC Rename an NT4 backup domain controller NETDOM MOVE Move a workstation or member server to a new domain NETDOM QUERY.

we currently have an office server running on Windows 2003. The server hosts e-mail (exchange) and active directory. Also we have two client pc's which get their internet connection and their profiles through the server.

The server is currently running at a specific domain. xxx.companyname.nl. Our companyname has changed and we would like to change the domain to xxx.newcompanyname.nl. Is this a complex procedure (are we better off re-installing?), or can this be done easily?

Oskar Duveborn

8 Answers

Exchange being on a DC makes a normal 'Domain rename' a bit complicated. If you've only got a few mailboxes I'd consider doing a full PST export of the mailboxes with EXMERGE (and any Public Folders, using Outlook), uninstalling and retiring the Exchange organization, then performing a normal domain rename (see http://technet.microsoft.com/en-us/library/cc786120(WS.10).aspx), and re-installing Exchange and importing the email.

Be aware that after such a 'PST migration' you'll need to edit the X500 address proxies on recipients so that replies to old intra-organization emails work properly (see http://blogs.technet.com/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx for details about what I'm talking about).

This shouldn't be too hard of a road, really. Since you can gather all the pertinent details re: Exchange prior to the export / uninstall / reinstall / import, it should go fine.

Evan AndersonEvan Anderson

Seriously don't do it! Renaming your domain will take you far longer than migrating/creating to a new domain name.

Or easier still just ignore your domain name, end users never need interact with it. Aside form the 'member of domain' section in Windows it is irrelevant what your Domain is called - simply creating a new DNS zone and adding the new domain name to Exchange will do the trick.

Jon RhoadesJon Rhoades

Renaming domains has been possible since Windows Server 2003 was introduced (as opposed to Windows 2000, which explicitly stated domain names were not changeable). The procedure is a bit complex and involves using command-line tools (rendom.exe) and editing XML configuration files, but it can be done and works quite well.

Now, renaming a domain with Exchange is a bit more tricky. You can find a good guide to this here:

Massimo

Windows Server 2003 Sp3 Download

Massimo

just adding a related caution on ghost and DCs but can't comment in line with the ghosting discussion due to rep:

Having recovered a DC from a Ghost image, it's possible but there can be wrinkles if replication has continued with 'current' version of the DC that you wish to restore.

As replication continues, the USN continues to be incremented and restoring the ghost image results in the DC reporting lower USN and it will be out of sync with the up-to-date DCs.

There are ways around this but adding Exchange into the mix likely adds even more wrinkles.

For ref. there's a discussion of this issue and possible ways to correct it:http://utools.com/help/UsnRollback.asp

I have done this several times at customers, and although the walkthrough documentation is a bit on the heavy side, the procedure itself actually isn't that complicated. For a one-server job with two pc's I'd say this is done in 3-4 hours if you know what you're doing.

IF you are running Exchange 2007 the procedure is unsupported though, so don't go there.

We can rename both domain/domain controller by using netdom tool

look at this article http://www.morgantechspace.com/2013/08/how-to-rename-domain-controller-name.html

1. To use Netdom, you must run the netdom command from an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.

2. At the command prompt, type the following command to add the new domain controller name, and then press ENTER key:

Type the following command to designate the new name as the primary computer name, and then press ENTER key:

3.Restart the computer.

4.After the computer restarts, open a Command Prompt. At the command prompt, type the following command to remove the old domain controller name, and then press ENTER:

Renaming a Domain Controller's ComputerName

Petri has some advice for renaming your domain controller, and it's possible. There are lots of hooks throughout the DC into the domain's name. This article is simply for renaming your DC's computer name, as indicated in the title of this question: 'Renaming windows 2003 domain controller?'

Really the best advice is to ensure that you have a second DC, and rebuild this machine once that second DC is able to take control. Certainly just power off your machine, ensure everything works on your domain using the second DC. That'll give you confidence that it's OK to go ahead and rebuild your first DC.

Heck, take a Ghost image of the machine that you want to rename in case things go sideways. If the re-naming project over the weekend doesn't give you good results, then you could reimage the machine and the users wouldn't be any wiser when they walk into work on Monday morning.

Renaming a Domain

You will encounter too many hidden hooks in Windows, Active Directory, and Exchange. You'll be paying the price in time wasted downstream, that I'd not even consider this option.

p.campbellp.campbell

I would say its not worth it.

Here is the link to the technical guide for renaming a domain, its 19 pages log. Honestly if its that important, I'd EXMerge the mailboxs out then rebuilt the DC/Exchange server from new.

I'd personally not worry about it if its not really required. Unless like the boss to do it.

Not the answer you're looking for? Browse other questions tagged windows-server-2003domain-controllerrename or ask your own question.

we currently have an office server running on Windows 2003. The server hosts e-mail (exchange) and active directory. Also we have two client pc's which get their internet connection and their profiles through the server.

The server is currently running at a specific domain. xxx.companyname.nl. Our companyname has changed and we would like to change the domain to xxx.newcompanyname.nl. Is this a complex procedure (are we better off re-installing?), or can this be done easily?

Oskar Duveborn

8 Answers

Exchange being on a DC makes a normal 'Domain rename' a bit complicated. If you've only got a few mailboxes I'd consider doing a full PST export of the mailboxes with EXMERGE (and any Public Folders, using Outlook), uninstalling and retiring the Exchange organization, then performing a normal domain rename (see http://technet.microsoft.com/en-us/library/cc786120(WS.10).aspx), and re-installing Exchange and importing the email.

Be aware that after such a 'PST migration' you'll need to edit the X500 address proxies on recipients so that replies to old intra-organization emails work properly (see http://blogs.technet.com/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx for details about what I'm talking about).

This shouldn't be too hard of a road, really. Since you can gather all the pertinent details re: Exchange prior to the export / uninstall / reinstall / import, it should go fine.

Evan AndersonEvan Anderson

Seriously don't do it! Renaming your domain will take you far longer than migrating/creating to a new domain name.

Or easier still just ignore your domain name, end users never need interact with it. Aside form the 'member of domain' section in Windows it is irrelevant what your Domain is called - simply creating a new DNS zone and adding the new domain name to Exchange will do the trick.

Jon RhoadesJon Rhoades

Renaming domains has been possible since Windows Server 2003 was introduced (as opposed to Windows 2000, which explicitly stated domain names were not changeable). The procedure is a bit complex and involves using command-line tools (rendom.exe) and editing XML configuration files, but it can be done and works quite well.

Now, renaming a domain with Exchange is a bit more tricky. You can find a good guide to this here:

MassimoMassimo

just adding a related caution on ghost and DCs but can't comment in line with the ghosting discussion due to rep:

Having recovered a DC from a Ghost image, it's possible but there can be wrinkles if replication has continued with 'current' version of the DC that you wish to restore.

As replication continues, the USN continues to be incremented and restoring the ghost image results in the DC reporting lower USN and it will be out of sync with the up-to-date DCs.

There are ways around this but adding Exchange into the mix likely adds even more wrinkles.

For ref. there's a discussion of this issue and possible ways to correct it:http://utools.com/help/UsnRollback.asp

I have done this several times at customers, and although the walkthrough documentation is a bit on the heavy side, the procedure itself actually isn't that complicated. For a one-server job with two pc's I'd say this is done in 3-4 hours if you know what you're doing.

IF you are running Exchange 2007 the procedure is unsupported though, so don't go there.

We can rename both domain/domain controller by using netdom tool

look at this article http://www.morgantechspace.com/2013/08/how-to-rename-domain-controller-name.html

1. To use Netdom, you must run the netdom command from an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.

2. At the command prompt, type the following command to add the new domain controller name, and then press ENTER key:

Type the following command to designate the new name as the primary computer name, and then press ENTER key:

3.Restart the computer.

4.After the computer restarts, open a Command Prompt. At the command prompt, type the following command to remove the old domain controller name, and then press ENTER:

Renaming a Domain Controller's ComputerName

Petri has some advice for renaming your domain controller, and it's possible. There are lots of hooks throughout the DC into the domain's name. This article is simply for renaming your DC's computer name, as indicated in the title of this question: 'Renaming windows 2003 domain controller?'

Really the best advice is to ensure that you have a second DC, and rebuild this machine once that second DC is able to take control. Certainly just power off your machine, ensure everything works on your domain using the second DC. That'll give you confidence that it's OK to go ahead and rebuild your first DC.

Heck, take a Ghost image of the machine that you want to rename in case things go sideways. If the re-naming project over the weekend doesn't give you good results, then you could reimage the machine and the users wouldn't be any wiser when they walk into work on Monday morning.

Renaming a Domain

You will encounter too many hidden hooks in Windows, Active Directory, and Exchange. You'll be paying the price in time wasted downstream, that I'd not even consider this option.

p.campbellp.campbell

I would say its not worth it.

Here is the link to the technical guide for renaming a domain, its 19 pages log. Honestly if its that important, I'd EXMerge the mailboxs out then rebuilt the DC/Exchange server from new.

I'd personally not worry about it if its not really required. Unless like the boss to do it.

Not the answer you're looking for? Browse other questions tagged windows-server-2003domain-controllerrename or ask your own question.