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

[Michael B. Smith]

Title: Message

EXCEPT I can't have my AD name the same as the netbios name!   But cool. Thanks for your input (and that of others on the list). VERY helpful. -----Original Message----- From: Rick Kingslan [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 4:50 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD Upgrade with "bad" NetBIOS name Michael,   Why worry about it?  A '.' is legal in a NetBIOS name, and it's not going to conflict with DNS or LDAP, which Windows 2000 is hugely more interested in.  NetBIOS is there for backwards compatability and legacy support.   Lab it, test it, and then upgrade.  It will be fine.   Rick Kingslan  MCSE, MCSA, MCT Microsoft MVP - Active Directory Associate Expert Expert Zone - www.microsoft.com/windowsxp/expertzone   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.