| Author |
Message |
Adam
Guest
|
Posted:
Wed Sep 21, 2005 8:52 pm Post subject:
change netbios domain name after migration |
|
|
Is there a way to change the netbios domain name? For example, when we join
a new pc/laptop to our domain it joins using the old netbios name. So when
you log into the pc/laptop you see the old nebios domain name in the domain
field. We did an in place upgrade from NT4. It is not causing any conflicts
but just anoying!
Thanks,
Adam |
|
| Back to top |
|
 |
Ada Pan [MSFT]
Guest
|
Posted:
Thu Sep 22, 2005 8:51 am Post subject:
RE: change netbios domain name after migration |
|
|
Hi Adam,
As I know, it is expected behavior that the NetBIOS domain name is
displayed in the Windows Logon window. This is because that not all the
available domains have DNS domain names. For example, many corporations'
network still contains Windows NT domains. Therefore, for backward
compatibility considerations, the NetBIOS names are listed on the logon
window. However, as the list is just for the user to choose a suitable
logon domain, this design will not affect the domain usage.
Also, this behavior is not changed in Windows Server 2003 AD domains, even
after upgrading the domain functional level. When upgrading a Windows NT
domain to Windows Server 2003, we are prompted to provide a DNS domain
name. However, the old Windows NT NetBIOS domain name must be kept. In
other words, we cannot change the NetBIOS name during the upgrade.
I would like to suggest that you do not make any changes on the current
domains if it is acceptable to choose ABC NetBIOS domain name in the logon
list, as all the possible solutions so far are very complicated and have
potential risks.
Having said that, I would like to suggest you use one of the following
possible solutions to change the NetBios domain name.
IMPORTANT CAUTION: 1). The domain rename procedure has not been
extensively tested in large installations. Microsoft cannot guarantee that
everything will function well after changing the domain name. Please
perform complete backup for your domain first and use the method at your
own risk. 2). No matter which method you will finally use, please perform a
complete backup for your domain first.
1. Use RenDom.
Note: As I know, rendom.exe is a possible solution. However, it is a very
complex, multi-step process and could cause potential problems during the
rename process. In most cases, it requires modifications on all domain
controllers and on all domain members (servers and workstations), and
should NOT be considered a routine operation.
Windows Server 2003 domain first includes a new feature of domain rename by
using a new tool called RenDom.exe (Windows Server 2003 domain rename tool).
Reference on RenDom:
Step-by-Step Guide to Implementing Domain Rename
http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a
2a2e2/Domain-Rename-Procedure.doc
Understanding How Domain Rename Works
http://download.microsoft.com/download/9/6/5/965e6899-e086-4b3e-8ed6-516ea07
ea225/Domain-Rename-Intro.doc
Download:
Windows Server 2003 Domain Rename Tools
http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx
Please Note: The Windows Server 2003 domain rename tools have special
requirements, especially on the Exchange side. Actually, the Windows Server
2003 domain rename tools were originally designed to rename domains in
Active Directory services forests that do not contain Exchange computers.
This limitation occurred because renaming a domain affects a number of
Exchange attributes and there was no method to repair these Exchange
attributes. Because of this, the domain rename operation is not supported
in forests that contain Microsoft Exchange Server 5.5 computers or
Microsoft Exchange 2000 Server computers.
Exchange 2003 supports the domain rename operation because it is compatible
with the Exchange Domain Rename Fix-Up tool. The Exchange Domain Rename
Fix-Up tool repairs Exchange attributes after a domain rename operation is
complete.
For more information please refer to:
838623 TechNet Support WebCast: Renaming domains when Microsoft Exchange
Server
http://support.microsoft.com/?id=838623
Exchange 2003: Domain Rename Fixup (XDR-Fixup)
http://www.microsoft.com/downloads/details.aspx?FamilyId=24B47D4A-C4B9-4031-
B491-29839148A28C&displaylang=en
2. We have a safer option: Install a new domain with the correct domain DNS
and NetBIOS name (it can be either a Windows 2000 or a Windows Server 2003
domain), use Active Directory Migration Tool (ADMT) to migrate necessary
domain data (including user accounts, groups, client computers, security
settings) to the new domain, perform thorough tests in the new domain, and
then remove the old domain.
For more information regarding ADMT, please refer to:
Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp
Download details: Active Directory Migration Tool v.2.0
http://www.microsoft.com/downloads/details.aspx?familyid=788975b1-5849-4707-
9817-8c9773c25c6c&displaylang=en
DomainMig.chm in the ADMT installation folder (this file contains very good
information).
3. Just for your reference, we are able to code a customized Windows Logon
window. If necessary, you can have your developer team write a Graphical
Identification and Authentication (GINA) DLL to only display DNS mode
domain names in the logon window. I would like to provide the following
information, which may assist you or your developer team.
The Essentials of Replacing the Microsoft Graphical Identification and
Authentication Dynamic Link Library
www.microsoft.com/windows2000/docs/msgina.doc
Gina Sample: Graphical Identification and Authentication DLL
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcsample98/
html/vcsmpginasample.asp
Also, if you or your developer team needs more information regarding the
GINA programming, I would like to suggest that you use our developer
newsgroups. The developer newsgroups are located at:
http://msdn.microsoft.com/newsgroups/default.asp
This is just a method for your reference. It requires coding a new GINA
DLL, and replacing the GINA DLL on all of the domain members. Personally, I
do not think it is a good idea for this situation but just a possible
solution for your reference.
Hope it helps.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
 |
Per W.
Guest
|
Posted:
Thu Sep 22, 2005 8:51 am Post subject:
Re: change netbios domain name after migration |
|
|
"Adam" <Adam@discussions.microsoft.com> skrev i melding
news:89BF4455-04FA-4B02-A8EE-431F149D0528@microsoft.com...
| Quote: | Is there a way to change the netbios domain name? For example, when we
join
a new pc/laptop to our domain it joins using the old netbios name. So
when
you log into the pc/laptop you see the old nebios domain name in the
domain
field. We did an in place upgrade from NT4. It is not causing any
conflicts
but just anoying!
|
No.
/Per W. |
|
| Back to top |
|
 |
Adam
Guest
|
Posted:
Thu Sep 22, 2005 12:50 pm Post subject:
RE: change netbios domain name after migration |
|
|
Thanks for all the info. It sounds like I'm keeping my netbios domain name!
No big deal
"Ada Pan [MSFT]" wrote:
| Quote: | Hi Adam,
As I know, it is expected behavior that the NetBIOS domain name is
displayed in the Windows Logon window. This is because that not all the
available domains have DNS domain names. For example, many corporations'
network still contains Windows NT domains. Therefore, for backward
compatibility considerations, the NetBIOS names are listed on the logon
window. However, as the list is just for the user to choose a suitable
logon domain, this design will not affect the domain usage.
Also, this behavior is not changed in Windows Server 2003 AD domains, even
after upgrading the domain functional level. When upgrading a Windows NT
domain to Windows Server 2003, we are prompted to provide a DNS domain
name. However, the old Windows NT NetBIOS domain name must be kept. In
other words, we cannot change the NetBIOS name during the upgrade.
I would like to suggest that you do not make any changes on the current
domains if it is acceptable to choose ABC NetBIOS domain name in the logon
list, as all the possible solutions so far are very complicated and have
potential risks.
Having said that, I would like to suggest you use one of the following
possible solutions to change the NetBios domain name.
IMPORTANT CAUTION: 1). The domain rename procedure has not been
extensively tested in large installations. Microsoft cannot guarantee that
everything will function well after changing the domain name. Please
perform complete backup for your domain first and use the method at your
own risk. 2). No matter which method you will finally use, please perform a
complete backup for your domain first.
1. Use RenDom.
Note: As I know, rendom.exe is a possible solution. However, it is a very
complex, multi-step process and could cause potential problems during the
rename process. In most cases, it requires modifications on all domain
controllers and on all domain members (servers and workstations), and
should NOT be considered a routine operation.
Windows Server 2003 domain first includes a new feature of domain rename by
using a new tool called RenDom.exe (Windows Server 2003 domain rename tool).
Reference on RenDom:
Step-by-Step Guide to Implementing Domain Rename
http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a
2a2e2/Domain-Rename-Procedure.doc
Understanding How Domain Rename Works
http://download.microsoft.com/download/9/6/5/965e6899-e086-4b3e-8ed6-516ea07
ea225/Domain-Rename-Intro.doc
Download:
Windows Server 2003 Domain Rename Tools
http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx
Please Note: The Windows Server 2003 domain rename tools have special
requirements, especially on the Exchange side. Actually, the Windows Server
2003 domain rename tools were originally designed to rename domains in
Active Directory services forests that do not contain Exchange computers.
This limitation occurred because renaming a domain affects a number of
Exchange attributes and there was no method to repair these Exchange
attributes. Because of this, the domain rename operation is not supported
in forests that contain Microsoft Exchange Server 5.5 computers or
Microsoft Exchange 2000 Server computers.
Exchange 2003 supports the domain rename operation because it is compatible
with the Exchange Domain Rename Fix-Up tool. The Exchange Domain Rename
Fix-Up tool repairs Exchange attributes after a domain rename operation is
complete.
For more information please refer to:
838623 TechNet Support WebCast: Renaming domains when Microsoft Exchange
Server
http://support.microsoft.com/?id=838623
Exchange 2003: Domain Rename Fixup (XDR-Fixup)
http://www.microsoft.com/downloads/details.aspx?FamilyId=24B47D4A-C4B9-4031-
B491-29839148A28C&displaylang=en
2. We have a safer option: Install a new domain with the correct domain DNS
and NetBIOS name (it can be either a Windows 2000 or a Windows Server 2003
domain), use Active Directory Migration Tool (ADMT) to migrate necessary
domain data (including user accounts, groups, client computers, security
settings) to the new domain, perform thorough tests in the new domain, and
then remove the old domain.
For more information regarding ADMT, please refer to:
Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp
Download details: Active Directory Migration Tool v.2.0
http://www.microsoft.com/downloads/details.aspx?familyid=788975b1-5849-4707-
9817-8c9773c25c6c&displaylang=en
DomainMig.chm in the ADMT installation folder (this file contains very good
information).
3. Just for your reference, we are able to code a customized Windows Logon
window. If necessary, you can have your developer team write a Graphical
Identification and Authentication (GINA) DLL to only display DNS mode
domain names in the logon window. I would like to provide the following
information, which may assist you or your developer team.
The Essentials of Replacing the Microsoft Graphical Identification and
Authentication Dynamic Link Library
www.microsoft.com/windows2000/docs/msgina.doc
Gina Sample: Graphical Identification and Authentication DLL
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcsample98/
html/vcsmpginasample.asp
Also, if you or your developer team needs more information regarding the
GINA programming, I would like to suggest that you use our developer
newsgroups. The developer newsgroups are located at:
http://msdn.microsoft.com/newsgroups/default.asp
This is just a method for your reference. It requires coding a new GINA
DLL, and replacing the GINA DLL on all of the domain members. Personally, I
do not think it is a good idea for this situation but just a possible
solution for your reference.
Hope it helps.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
| Back to top |
|
 |
Ada Pan [MSFT]
Guest
|
Posted:
Fri Sep 23, 2005 12:50 pm Post subject:
RE: change netbios domain name after migration |
|
|
Hi Adam,
I am glad to hear the information helps. If you have any questions, please
feel free to submit your questions in the newsgroup. We are glad to be of
assistance.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
 |
|
|
|
|