locked
Error than renaming a 2012 DC RRS feed

  • Question

  • The server is a Hyper-V on a 2012 server

    Domain functional level is 2008 R2

    C:\ >netdom computername pc2 /add:pc200.domain.com

    Unable to add pc200.domain.com

    as an alternate name for the computer.

    The error is:

    The requested resource is in use.

    The command failed to complete successfully.

    Have tried C:\ >netdom computername pc2.domain.com /add:pc200.domain.com with the same result.

    I don’t know that the requested resource is? But I have tried another new computer name that I’m sure I never used.


    • Edited by SakenArBiff Wednesday, September 18, 2013 7:36 AM
    Wednesday, September 18, 2013 7:33 AM

All replies

  • Hi,

    Renaming a DC is not recommended. It seems like that the below article is the one you referred to:

    http://terrytlslau.tls1.cc/2013/06/rename-domain-controller.html

    As this is not hosted by Microsoft, so Microsoft does not guarantee the accuracy of this
    information.


    Regards,

    Yan Li


    Cataleya Li
    TechNet Community Support



    • Edited by Yan Li_ Thursday, September 19, 2013 2:45 AM edit
    Thursday, September 19, 2013 2:42 AM
  • Hi

    No it is this http://technet.microsoft.com/en-us/library/cc835082.aspx I referred to.

    And it says "This command can safely rename Active Directory domain controllers as well as member servers."

    Would you say that if I denote the server than rename it and the premote it again should work? And be safer?

    Fredrik

    Thursday, September 19, 2013 6:52 AM
  • Hi,

    To rename the domain controller DC to altDC in the example.com domain:

    netdom computername dc /makeprimary:altdc.example.com

    Regards,

    Yan Li


    Cataleya Li
    TechNet Community Support

    Friday, September 20, 2013 3:00 AM
  • If I do netdom computername dc /makeprimary:altdc.example.com I get this:

    C:\ >netdom computername pc2 /makeprimary:pc200.domain.com

    Unable to make pc200.domain.com

    the primary name for the computer.

    The error is:

    The directory service is busy.

    The command failed to complete successfully.

    And if I understand it correctly you must first add the new name as an alternative name than make it primary.

    Before you can make a name the primary name of a computer, that name must exist as an alternate.”

    So first with the flag /add then the flag /makeprimary.


    • Edited by SakenArBiff Friday, September 20, 2013 7:27 AM
    Friday, September 20, 2013 7:27 AM
  • Hi,

    Did you ever get an answer to this as I have the same problem?

    Saturday, March 22, 2014 9:21 PM
  • Hi,

    Same here so will be grateful for answer...

    Regards

    Pawel

    Monday, March 24, 2014 9:30 AM
  • Hi,

    My solution was to remove MSSQLSvc entries in the computer objects attribute editor "servicePrincipalName". After that I could do the netdom successfully. When I was finished with the netdom I just added back the MSSQLSvc entries again.

    It seems like the servicePrincipalName is being locked by MSSQLSvc...

    1. Open Active Directory Users and Computers
    2. Click on View and change to Advanced Features
    3. Locate the DC and chose Properties
    4. Goto Attribute Editor
    5. Click Edit on servicePrincipalName
    6. Note down the MSSQLSvc entries and Remove them
    7. Click OK and close the windows
    8. Now try and do the netdom command again

    I would love to attach a screenshot as example, but it seems my account first needs to be verified :(

    • Proposed as answer by Javivi232 Wednesday, July 20, 2016 8:11 PM
    Tuesday, September 29, 2015 8:25 AM
  • Hi,

    My solution was to remove MSSQLSvc entries in the computer objects attribute editor "servicePrincipalName". After that I could do the netdom successfully. When I was finished with the netdom I just added back the MSSQLSvc entries again.

    It seems like the servicePrincipalName is being locked by MSSQLSvc...

    1. Open Active Directory Users and Computers
    2. Click on View and change to Advanced Features
    3. Locate the DC and chose Properties
    4. Goto Attribute Editor
    5. Click Edit on servicePrincipalName
    6. Note down the MSSQLSvc entries and Remove them
    7. Click OK and close the windows
    8. Now try and do the netdom command again

    I would love to attach a screenshot as example, but it seems my account first needs to be verified :(


    Many thanks for your post, it helped me for a few servers with same conflict issue.
    Saturday, May 21, 2016 12:40 PM
  • This is the solution for my problem, many thanks for share 
    Wednesday, July 20, 2016 8:12 PM
  • You can also temporarily stop the all SQL instances in services.msc - this will allow netdom to complete without error
    • Proposed as answer by Bob Hatcher Wednesday, July 5, 2017 2:36 PM
    • Unproposed as answer by Bob Hatcher Wednesday, July 5, 2017 2:36 PM
    Friday, March 3, 2017 3:58 AM
  • One other factor I just tried this was the alternate or new computer name has to end in a period "."or requires the FQDN. In my case this applies to a 2012R2 domain.

    Message I received: (I modified the hostnames)

    C:\Windows\system32>netdom computername abcd-57-domain1 /add:abcd-domain1
    The specified alternate computer name "mpiw-domain1" does not contain a dot.
    Although it is a valid DNS name, usually a DNS name consists of multiple
    labels, for example server1.microsoft.com. This field MUST contain the full
    DNS name of a computer.

    Do you want to proceed (Y or N)?
    N
    The alternate computer name was not added.

    The operation was canceled by the user.

    The command failed to complete successfully.


    C:\Windows\system32>netdom computername abcd-57-domain1 /add:abcd-domain1.
    Successfully added abcd-domain1.
    as an alternate name for the computer.

    The command completed successfully.

    • Proposed as answer by Bob Hatcher Wednesday, July 5, 2017 3:57 PM
    Wednesday, July 5, 2017 2:42 PM
  • i was having the same issue and your solution work for me

    i think the main problem is i use a third party backup software that use MSSQL 2008 and by removing the software you can perform the netdom command

    hope this note help any one

    Wednesday, January 10, 2018 6:33 AM