Merging 2 domains with same NetBIOS domain name

%3CLINGO-SUB%20id%3D%22lingo-sub-325950%22%20slang%3D%22en-US%22%3EMerging%202%20domains%20with%20same%20NetBIOS%20domain%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325950%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20the%20current%20situation%20at%20a%20new%20company%20I%20started%20with%3A%3C%2FP%3E%3CP%3EThere%20are%20two%20locations%20with%20separate%20AD's%3A%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3Elocation%20one%20-%20%3CSTRONG%3Elocation1.company.com%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3Elocation%20two%20-%26nbsp%3B%3CSTRONG%3Elocation2.local%3C%2FSTRONG%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EOne%20Office%20365%20Business%20Premium%20tenant%3C%2FP%3E%3CUL%3E%3CLI%3Econnected%20to%20AD%20location2.local%20via%20AAD%20Connect%20w%2F%20Password%20Hash%20Sync%3C%2FLI%3E%3CLI%3EuserPrincipalName%20-%20company.com%20(SMTP%20address)%3C%2FLI%3E%3CLI%3EAD%20location1.company.com%20is%20not%20connected%2C%20but%20users%20are%20manually%20created%20in%20Office%20365%20(local%20AD%20and%20Office%20are%20separate%20user%20accounts).%3C%2FLI%3E%3C%2FUL%3E%3CP%3EThe%20plan%20is%20to%20create%20a%20new%20Forest%20%3CSTRONG%3Ecorp.company.com%3C%2FSTRONG%3E%20and%20migrate%20EVERYTHING%20to%20that%3C%2FP%3E%3CP%3ESo%20basically%20the%20super%20simplify%20plan%20is%2C%3C%2FP%3E%3CUL%3E%3CLI%3Edisconnect%20the%20sync%2C%3C%2FLI%3E%3CLI%3Ecreate%20new%20forest%3C%2FLI%3E%3CLI%3Ejoin%20domains%20to%20new%20forest%3C%2FLI%3E%3CLI%3Emigrate%20everything%20using%20ADMT%20to%20new%20forest%3C%2FLI%3E%3CLI%3Ereconnect%20to%20original%20O365%20tenant%3C%2FLI%3E%3C%2FUL%3E%3CP%3EMy%20problem%20is%20%3CSTRONG%3Elocation2.local%3C%2FSTRONG%3E%20has%20the%20netbios%20domain%20name%20%3CSTRONG%3ECOMPANY%3C%2FSTRONG%3E%20and%20I'd%20like%20to%20use%20this%20netbios%20name%20for%20the%20new%20%3CSTRONG%3Ecorp.company.com%3C%2FSTRONG%3E%20domain.%20From%20what%20I've%20read%2C%20having%202%20domains%20with%20the%20same%20netbios%20domain%20name%20will%20cause%20problems.%20If%20this%20is%20true%20how%20do%20I%20get%20around%20this%2C%20or%20what%20is%20my%20best%20option%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325967%22%20slang%3D%22en-US%22%3ERe%3A%20Merging%202%20domains%20with%20same%20NetBIOS%20domain%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325967%22%20slang%3D%22en-US%22%3EThat%20will%20be%20a%20problem%20as%20its%20pretty%20common%20knowledge%20if%20you%20plan%20to%20use%20ADMT%20there%20will%20need%20to%20be%20a%20trust%20and%20AFAIK%20you%20can't%20do%20that%20if%20the%20NetBIOS%20name%20is%20the%20same.%3CBR%20%2F%3E%3CBR%20%2F%3EHmm.%3CBR%20%2F%3E%3CBR%20%2F%3ESome%20ways%20you%20could%20get%20around%20this.%3CBR%20%2F%3E%3CBR%20%2F%3E1.)%20Go%20with%20a%20new%20NetBIOS%20name%20(I.e.%20COMPANYNEW)%3CBR%20%2F%3E2.)%20Consolidate%20onto%20location1.company.com%20then%20move%20to%20corp.company.com%3CBR%20%2F%3E3.)%20Take%20everything%20out%20on%20location2.local%20and%20then%20build%20corp.company.com%20from%20scratch%20(not%20recommended%20but%20it's%20an%20option)%3CBR%20%2F%3E%3CBR%20%2F%3EI%20wouldn't%20say%20that%20there%20is%20any%20'best'%20option%20as%20such.%20It's%20the%20best%20of%20a%20worst%20bunch%20as%20you%20are%20cleaning%20up%20here.%20If%20I%20took%20a%20short%20term%20view%20having%20a%20new%20NetBIOS%20name%20is%20easiest.%20If%20I%20took%20a%20very%20long%20term%20view%20and%20want%20it%20to%20be%20exactly%20by%20the%20book%20I%20would%20probably%20at%20least%20consider%202%20or%203.%20However%2C%20that's%20a%20lot%20of%20work%20potentially.%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20is%20important%20because%20you%20shouldn't%20change%20it%20once%20set.%20There%20is%20workarounds%20to%20change%20it%20but%20changing%20the%20name%20after%20its%20implemented%20will%20mean%20you%20won't%20be%20supported%20after.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

This is the current situation at a new company I started with:

There are two locations with separate AD's: 

  • location one - location1.company.com
  • location two - location2.local

One Office 365 Business Premium tenant

  • connected to AD location2.local via AAD Connect w/ Password Hash Sync
  • userPrincipalName - company.com (SMTP address)
  • AD location1.company.com is not connected, but users are manually created in Office 365 (local AD and Office are separate user accounts).

The plan is to create a new Forest corp.company.com and migrate EVERYTHING to that

So basically the super simplify plan is,

  • disconnect the sync,
  • create new forest
  • join domains to new forest
  • migrate everything using ADMT to new forest
  • reconnect to original O365 tenant

My problem is location2.local has the netbios domain name COMPANY and I'd like to use this netbios name for the new corp.company.com domain. From what I've read, having 2 domains with the same netbios domain name will cause problems. If this is true how do I get around this, or what is my best option?

1 Reply
Highlighted
That will be a problem as its pretty common knowledge if you plan to use ADMT there will need to be a trust and AFAIK you can't do that if the NetBIOS name is the same.

Hmm.

Some ways you could get around this.

1.) Go with a new NetBIOS name (I.e. COMPANYNEW)
2.) Consolidate onto location1.company.com then move to corp.company.com
3.) Take everything out on location2.local and then build corp.company.com from scratch (not recommended but it's an option)

I wouldn't say that there is any 'best' option as such. It's the best of a worst bunch as you are cleaning up here. If I took a short term view having a new NetBIOS name is easiest. If I took a very long term view and want it to be exactly by the book I would probably at least consider 2 or 3. However, that's a lot of work potentially.

It is important because you shouldn't change it once set. There is workarounds to change it but changing the name after its implemented will mean you won't be supported after.

Best, Chris