none
How to rename domain netbios name ? RRS feed

  • Question

  • Hi there
    wonder if someone can help me
    I have a domain (windows server 2008 R2) called <MNhosting.Local> and netbios name for this domain is MNHosting so every time users have to type MNHostin\username to login
    they asked me to change this name to MN only
    is there any way to do that ?
    Thursday, June 23, 2011 8:07 AM

Answers

  • Hello,

    Read this Microsoft article for renaming: http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx

    Note that the domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Thursday, June 23, 2011 8:09 AM
  • Hi,
    I had followed these steps in our windows 2003 Single forest - Single Domain environment and domain without exchage. It may help you undestand what all steps are involved in domain rename operation. Has to be done carefully.

    Requirements :-
    Cotrol Station :- The computer that will be used to execute rendom.exe should be a member Computer with windows 2003 Standard/Enterprise/Data Center installed.
    Credentials Required :- User should be a member of Enterprise admin group.
    Domain Naming Master must be running.
    Domain functional level – Windows 2003 OR above.
    STEPS :-

    1. Create DNS zone for new domain.
    [ DNS zone should be Active Directory Integrated so that changes made to this zone during rename operation will get replicated to all domain controllers automatically ]

    2. Configure domain to accept new DNS suffix.
    [ ADSI Edit is used to perform this operation. Install windows 2003 support tools from CD….
    How To Add New DNS suffix :--
    Install Windows 2003 support tools.
    Click start à Programs à Windows 2003 support toolsà ADSI Edit OR startà Runà AdsiEdit.exe
    Double click the corresponding domain directory partition of Domain to be renamed.
    Right Click domain container à Properties àAttribute Editor à Double Click MsDs-AllowedDNSSuffixes à In multivalued string editor àValue to Add == New DNS Suffix à OK ]

    3. Enable update DNS suffix option for computers.
    System Properties à Computer Name à Change à More à select Change Primary DNS suffix when Domain membership changes option
    OR
    Using group policy –
    Computer configuration à Administrative Templates à Network à DNS client à Primary DNS suffix à Type New suffix.
    Important :-
    Domain Controllers are not configured to accept new DNS suffix automatically. Change DNS suffix of all Domain controllers after rename operation is completed.

    4. Set Up control station :-
    Copy rendom.exe & gpfixup.exe to a folder on Hard Disk
    <cdrom>\valueadd\msft\mgmt\domren\ to c:\DomainRename
    Rendom.exe will be run under credentials of currently logged on user . To
    supply different username and password use /user & /pwd switch

    5. Generate forest description file :-
    C:\DomainRename\rendom /list
    This will create a file domainlist.xml in c:\DomainRename.
    Create copy of domainlist.xml
    Copy domainlist.xml copy-domainlist.xml

    6. Specify the New forest Description :-
    Edit Domainlist.xml using Notepad
    Replace Old Domain DNS & Netbios names with New Domain DNS name and NetBios name.
    ** Changing NetBios name is optional.

    7. Specify Source Domain Controller ( Optional )
    Domain rename tool contacts one arbitrarily chosen domain controller
    OR
    It can be specified in each domain entry by
    <DcName>Dc-Old-Dns-Name</DcName> in domainlist.xml

    8. Review New Forest Description :-
    rendom /showforest
    [ This command will display contents of domainlist.xml in easier to read format & in which one can see forest structure .
    Run this command every time you make changes to domainlist.xml ]

    9. Generate Domain Rename Instructions :-
    rendom /upload
    [ This command will upload domain rename instructions to the configuration partition on Domain Naming Master in special script format]
    Check dclist.xml file created in C:\DomainRename directory.
    ** Open dclist.xml with notepad and check if it contains entry for each
    Domain Controller.

    10. Push Domain Rename Instructions to all DCs and Verify DNS readiness:-
    repadmin.exe and dsquery.exe must be installed on control station
    ** Use repadmin.exe to force Active Directory replication of directory
    Changes on the domain naming master to all DCs in the forest .
    If not run we’ll have to wait till replication occurs.
    Check Domain Naming Master’s availability :-
    dsquery server –hasfsmo name
    To force replication :-
    repadmin /syncall /d /e /P /q DomainNameMaster
    If replication fails , reattempt above command.
    Check following DNS records :-
    CNAME à DsaGuid._msdcs.DnsForestName
    SRV à _ldap._tcp.pdc._msdcs.DnsDomainName
    SRV à _ldap._tcp.gc._msdcs.DnsDomainName
    SRV à _ldap._tcp.dc._msdcs.DnsDomainName
    KDC à

    11. Verify Readiness of Domain Controllers :-
    *** All previous steps must be completed successfully
    rendom /prepare
    Check the file dclist.xml to determine whether all DCs have achieved
    the prepare state.
    e.g. <State>Prepared</State>
    *** If in any case DC fails to get updates , then its entry should
    be removed from dclist.xml & should be demoted in new forest after
    renaming is done.
    *** Backup dclist.xml after each change.
    *** Check log in c:\DomainRename directory

    12. Execute Domain Rename Instructions:-
    rendom /execute
    After this successful DCs will reboot automatically. If any DC fails ,
    Dclist.xml file we’ll be updated accordingly.
    e.g. following entries in dclist.xml file
    <state>error</state> à indicates Error has occurred
    <LastError></LastEror> à contains Error Code
    <FatalErrorMsg></ FatalErrorMsg> à contains Error description.
    *** To force retry for failed DCs edit
    <Rerty></Retry> to <Rerty>yes</Retry> in dclist.xml
    *** If error still persists irrecoverable error has occurred.

    13. End Rendom command :-
    rendom /end

    14. Change DNS suffix of all DC

    15, Gpfixup.exe is needed to run after Renaming Domain to Fix UP Group Policy related
    errors.
    Gpfixup.exe is a free ultility available on Microsoft website
    ***This Document is useful for performing Rename operation in Single Domain environment.
    If multiple domains / Domain having MS Exchange installed exists additional steps are required to configure trusts / Ms Exchange
    For details visit http://www.microsoft.com

    Friday, June 24, 2011 3:20 PM
  • Technically, domain name is possible but if you got Certificate Authority, Exchange 2007 & above running in your environment, its not possible to rename the Domain or Netbios name. Domain rename is a risk operation & you can't be sure that problem will not exists even if you successful carry rename operation.

    Alternative to the domain rename is configuring & using different UPNsuffix for login to domain.

    http://support.microsoft.com/kb/243629

    http://support.microsoft.com/kb/243280/EN-US

    Domain Controller rename does not rename all AD DFSR SYSVOL objects

    http://support.microsoft.com/kb/2001271

    I don't advice because user complain of typing extra word for login, you would like to perform such a big operation & even suffer downtime during renaming of the domain. More on domain rename is below.

    http://technet.microsoft.com/en-us/library/cc794919%28WS.10%29.aspx

    http://technet.microsoft.com/en-us/library/cc794869%28WS.10%29.aspx

    The viable approach is migration of all the object to another domain using ADMT/Quest/NetIQ tool.  

    Personally, i would leave the domain name as it is.

     

    Regards


    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Thursday, June 23, 2011 8:23 AM
    Moderator

All replies

  • Hello,

    Read this Microsoft article for renaming: http://technet.microsoft.com/en-us/library/cc738208(WS.10).aspx

    Note that the domain rename operation is not supported in Microsoft Exchange Server 2007 or Exchange Server 2010.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Thursday, June 23, 2011 8:09 AM
  • Technically, domain name is possible but if you got Certificate Authority, Exchange 2007 & above running in your environment, its not possible to rename the Domain or Netbios name. Domain rename is a risk operation & you can't be sure that problem will not exists even if you successful carry rename operation.

    Alternative to the domain rename is configuring & using different UPNsuffix for login to domain.

    http://support.microsoft.com/kb/243629

    http://support.microsoft.com/kb/243280/EN-US

    Domain Controller rename does not rename all AD DFSR SYSVOL objects

    http://support.microsoft.com/kb/2001271

    I don't advice because user complain of typing extra word for login, you would like to perform such a big operation & even suffer downtime during renaming of the domain. More on domain rename is below.

    http://technet.microsoft.com/en-us/library/cc794919%28WS.10%29.aspx

    http://technet.microsoft.com/en-us/library/cc794869%28WS.10%29.aspx

    The viable approach is migration of all the object to another domain using ADMT/Quest/NetIQ tool.  

    Personally, i would leave the domain name as it is.

     

    Regards


    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Thursday, June 23, 2011 8:23 AM
    Moderator
  • Hello,

    domain rename is possible with restrictions, so please describe in detail installed server roles, applications and services running in the domain.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, June 23, 2011 11:03 AM
  • As others mentions here, If needed, you can rename the domain using domain rename tool.  But it is not an easy process.  Also, domain rename is not supported in Exchange 2007 & Exchange 2010 environment.

    So test everything in the lab first if you are planning to do this. 


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara
    This posting is provided AS IS with no warranties,and confers no rights.
    Thursday, June 23, 2011 2:13 PM
    Moderator
  • Hi,
    I had followed these steps in our windows 2003 Single forest - Single Domain environment and domain without exchage. It may help you undestand what all steps are involved in domain rename operation. Has to be done carefully.

    Requirements :-
    Cotrol Station :- The computer that will be used to execute rendom.exe should be a member Computer with windows 2003 Standard/Enterprise/Data Center installed.
    Credentials Required :- User should be a member of Enterprise admin group.
    Domain Naming Master must be running.
    Domain functional level – Windows 2003 OR above.
    STEPS :-

    1. Create DNS zone for new domain.
    [ DNS zone should be Active Directory Integrated so that changes made to this zone during rename operation will get replicated to all domain controllers automatically ]

    2. Configure domain to accept new DNS suffix.
    [ ADSI Edit is used to perform this operation. Install windows 2003 support tools from CD….
    How To Add New DNS suffix :--
    Install Windows 2003 support tools.
    Click start à Programs à Windows 2003 support toolsà ADSI Edit OR startà Runà AdsiEdit.exe
    Double click the corresponding domain directory partition of Domain to be renamed.
    Right Click domain container à Properties àAttribute Editor à Double Click MsDs-AllowedDNSSuffixes à In multivalued string editor àValue to Add == New DNS Suffix à OK ]

    3. Enable update DNS suffix option for computers.
    System Properties à Computer Name à Change à More à select Change Primary DNS suffix when Domain membership changes option
    OR
    Using group policy –
    Computer configuration à Administrative Templates à Network à DNS client à Primary DNS suffix à Type New suffix.
    Important :-
    Domain Controllers are not configured to accept new DNS suffix automatically. Change DNS suffix of all Domain controllers after rename operation is completed.

    4. Set Up control station :-
    Copy rendom.exe & gpfixup.exe to a folder on Hard Disk
    <cdrom>\valueadd\msft\mgmt\domren\ to c:\DomainRename
    Rendom.exe will be run under credentials of currently logged on user . To
    supply different username and password use /user & /pwd switch

    5. Generate forest description file :-
    C:\DomainRename\rendom /list
    This will create a file domainlist.xml in c:\DomainRename.
    Create copy of domainlist.xml
    Copy domainlist.xml copy-domainlist.xml

    6. Specify the New forest Description :-
    Edit Domainlist.xml using Notepad
    Replace Old Domain DNS & Netbios names with New Domain DNS name and NetBios name.
    ** Changing NetBios name is optional.

    7. Specify Source Domain Controller ( Optional )
    Domain rename tool contacts one arbitrarily chosen domain controller
    OR
    It can be specified in each domain entry by
    <DcName>Dc-Old-Dns-Name</DcName> in domainlist.xml

    8. Review New Forest Description :-
    rendom /showforest
    [ This command will display contents of domainlist.xml in easier to read format & in which one can see forest structure .
    Run this command every time you make changes to domainlist.xml ]

    9. Generate Domain Rename Instructions :-
    rendom /upload
    [ This command will upload domain rename instructions to the configuration partition on Domain Naming Master in special script format]
    Check dclist.xml file created in C:\DomainRename directory.
    ** Open dclist.xml with notepad and check if it contains entry for each
    Domain Controller.

    10. Push Domain Rename Instructions to all DCs and Verify DNS readiness:-
    repadmin.exe and dsquery.exe must be installed on control station
    ** Use repadmin.exe to force Active Directory replication of directory
    Changes on the domain naming master to all DCs in the forest .
    If not run we’ll have to wait till replication occurs.
    Check Domain Naming Master’s availability :-
    dsquery server –hasfsmo name
    To force replication :-
    repadmin /syncall /d /e /P /q DomainNameMaster
    If replication fails , reattempt above command.
    Check following DNS records :-
    CNAME à DsaGuid._msdcs.DnsForestName
    SRV à _ldap._tcp.pdc._msdcs.DnsDomainName
    SRV à _ldap._tcp.gc._msdcs.DnsDomainName
    SRV à _ldap._tcp.dc._msdcs.DnsDomainName
    KDC à

    11. Verify Readiness of Domain Controllers :-
    *** All previous steps must be completed successfully
    rendom /prepare
    Check the file dclist.xml to determine whether all DCs have achieved
    the prepare state.
    e.g. <State>Prepared</State>
    *** If in any case DC fails to get updates , then its entry should
    be removed from dclist.xml & should be demoted in new forest after
    renaming is done.
    *** Backup dclist.xml after each change.
    *** Check log in c:\DomainRename directory

    12. Execute Domain Rename Instructions:-
    rendom /execute
    After this successful DCs will reboot automatically. If any DC fails ,
    Dclist.xml file we’ll be updated accordingly.
    e.g. following entries in dclist.xml file
    <state>error</state> à indicates Error has occurred
    <LastError></LastEror> à contains Error Code
    <FatalErrorMsg></ FatalErrorMsg> à contains Error description.
    *** To force retry for failed DCs edit
    <Rerty></Retry> to <Rerty>yes</Retry> in dclist.xml
    *** If error still persists irrecoverable error has occurred.

    13. End Rendom command :-
    rendom /end

    14. Change DNS suffix of all DC

    15, Gpfixup.exe is needed to run after Renaming Domain to Fix UP Group Policy related
    errors.
    Gpfixup.exe is a free ultility available on Microsoft website
    ***This Document is useful for performing Rename operation in Single Domain environment.
    If multiple domains / Domain having MS Exchange installed exists additional steps are required to configure trusts / Ms Exchange
    For details visit http://www.microsoft.com

    Friday, June 24, 2011 3:20 PM
  • Hi,
    I had followed these steps in our windows 2003 Single forest - Single Domain environment and domain without exchage. It may help you undestand what all steps are involved in domain rename operation. Has to be done carefully.

    (snip)
    I just changed the netbios domain name in our test environment using these steps and it seems like it worked like a charm. Some of the steps could even be left out because the dns name stayed the same. Thanks for the compact version of the guide. You basically took it down from 94 pages to 2.
    Thursday, July 16, 2015 11:34 AM