Forum Discussion
Merging 2 domains with same NetBIOS domain name
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 Bu...
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
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