RE: [ActiveDir] AD Upgrade with "bad" NetBIOS name

[Jef Kazimer]

Title: Message

Sorry I didn’t realize you were doing an “inplace” upgrade of the domain.   I was suggesting using a separate name space (thus a separate netbios name) for migration.   Here is a Q article that suggest you might have to any way:   Cannot Use Same NetBIOS Name When You Upgrade a Windows NT 4.0 Domain to a Windows 2000 Domain (288443) The information in this article applies to:        Microsoft Windows 2000 Server SP1        Microsoft Windows 2000 Server SP2        Microsoft Windows 2000 Advanced Server SP1        Microsoft Windows 2000 Advanced Server SP2        Microsoft Windows NT Server 4.0 SP4        Microsoft Windows NT Server 4.0 SP5        Microsoft Windows NT Server 4.0 SP6        Microsoft Windows NT Server 4.0 SP6a This article was previously published under Q288443 SYMPTOMS When you upgrade a Windows NT 4.0 primary domain controller (PDC) to a Windows 2000 domain controller (DC) by using the same NetBIOS and DNS name, the Active Directory Wizard generates the following error message: The name "domain name.com" is already in use on this network. Type a name that is not in use. For example, this could occur if your Windows NT 4.0 domain name was testdomain.com and your Windows 2000 domain name was also testdomain.com. RESOLUTION Before you upgrade, change the NetBIOS name so that it is not the same as the Windows 2000 domain name.       Also look at this article too:   Cannot Alter Down-Level Domain Name During Upgrade from Windows NT 4.0 to Windows 2000 (240156)   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael B. Smith Sent: Thursday, June 26, 2003 3:26 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD Upgrade with "bad" NetBIOS name   I think you misunderstand.   The company's netbios name is company.com -- that's the NT4 domain is company.com. I'm concerned about doing an AD upgrade with a period in the netbios name. -----Original Message----- From: Jef Kazimer [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 3:35 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD Upgrade with "bad" NetBIOS name Why not just use an internal namespace?   I’ve done it at a few companies  use  “corp.com” publicly,  and  “corp.net” internally.   The only issue is if you don’t own corp.net and may in the future have to get to the external net.   Company.int is available. J     You can use “company.com” externally and “company.int” for your internal network.   This would provide you a migration path and a separation of internal and external namespaces.   Jef   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael B. Smith Sent: Thursday, June 26, 2003 1:53 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD Upgrade with "bad" NetBIOS name   Actually, that IS their real name. They are a "dot com" that has succeeded and is still around. -----Original Message----- From: Raymond McClinnis [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 2:34 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD Upgrade with "bad" NetBIOS name I don’t know that it’s such a bad thing…  Most or all of the TechNet examples will be personalized for their environment…J   But Seriously, I’d consider migrating to a domain that has their real name in it, if not entirely for esthetic reasons.   But that’s just me…       Thanks,   Raymond McClinnis Network Administrator Provident Credit Union   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael B. Smith Sent: Thursday, June 26, 2003 11:05 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] AD Upgrade with "bad" NetBIOS name   I've just retained a client whose NT4 domain name is company.com -- yes, their netbios domain name.   I'm seriously concerned about upgrading them to AD. Do I have any worries? I've never seen this one before, and it isn't covered in any of the whitepapers I've quickly perused.   Thanks.