Disjoint name space question

Question

I'm working with an organization where the Active Directory domain name and primary DNS suffix are both:
wxyz.com
For some reason, the NetBIOs name of the domain is:
XYZ
So users can logon with this NetBIOS name\username combination:
XYZ\jsmith
Technically, I believe this is a disjointed namespace.
Question: is any remedial action necessary before migrating from Exchange 2007?
I see that for other disjoint namespace scenarios, one would have to modify the msDS-AllowedDNSSuffixes attribute on the domain controller container or adjust the DNS suffix search list.
Since this is a NetBIOs name (not DNS), is there anything to do?
I've looked at a number of sources (for Exchange 2010 and 2013)...
http://technet.microsoft.com/en-us/library/bb676377(EXCHG.140).aspx
http://technet.microsoft.com/en-us/library/bb676377(v=exchg.150).aspx
But don't see any action to be taken for a NetBIOS name.
This discussion seems to imply that there is no problem:
http://social.technet.microsoft.com/Forums/exchange/en-US/13f9b284-87a2-4d0b-8a56-1e336414ed53/disjoint-namespace-netbios-name-question?forum=exchange2010
Thanks in advance!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Answer 1

I'd still follow the points that are listed in your article David.  This is in the Exchange 2013 post. 
Scenario: NetBIOS name of domain controller differs from subdomain of its DNS domain name
It does ask for the additional steps to be taken, and while it may work without I would not go against the documentation. 
The other thing you can do, is to do a cross forest migration to a new forest that is not disjoint.  I know that is a lot of work but then you will not run into these issues.  The same thing applies for customers who have a single label domain. 
It's DNS name is not "contoso.com", the DNS name is "contoso".  Yes you can do that, but it is not a good place to be in.....
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne 
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.