internal domain name and activesync
Posted on 2014-12-12
I am setting up a new domain to migrate users off a domain I created about seven years ago. Part of my internal domain name was owned by someone and caused problems when trying to get SSL certs. So going to start from scratch then use ADMT to move user accounts, etc
1) for the internal domain name I would like some advice. my public facing domain is '@someplace.com', so I was going to make my internal domain 'internal.someplace.com', with a NetBIOS name of 'SP'. So my users, when needed to specify the domain they are logging into would put 'SP\username'. Any advice on this?
2) I want my users to be able to setup their EAS phones with as little input as possible. I am aware of autodiscover, but not sure it can provide my users with the domain name if needed. So then I started thinking well maybe I should set my internal NetBIOS name to 'someplace' as well.
What is the best practice for the internal domain name and NetBIOS name?
What configuration would make it possible for my EAS phone users to simply enter 'email@example.com' and have the remaining fields populate with the correct information (essentially the user's domain and mail server 'mail.someplace.com')
hopefully that is all clear and makes sense.... I saw a Microsoft article that said it is recommended to make the domain prefix and domain NetBIOS name the same...