internal domain name and activesync
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 'username@someplace.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...
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 'username@someplace.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...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The Autodiscover information comes from the information you have configured in Exchange. If you have put the wrong URLs for the ActiveSync virtual directories then the wrong information will be returned to the client.
Create a test account and run it through the Microsoft test site at http://exrca.com/
That will show you what is being returned to the clients.
Clients can login with the UPN if the correct UPN is set on their account. It doesn't have to be done at the point of account creation.
Simon.
Create a test account and run it through the Microsoft test site at http://exrca.com/
That will show you what is being returned to the clients.
Clients can login with the UPN if the correct UPN is set on their account. It doesn't have to be done at the point of account creation.
Simon.
ASKER
Hi Simon, thank you for the information and advice. I did a little research on UPN. I was only aware of this through textbooks, but have never implemented it myself. From what I read, my users will be able to login using the UPN extension, so long as that is what is specified when the account is created, correct?
In regards to the Autodiscover feature... it actually works 90% for me... the only portion that is not getting filled in correctly is the public DNS name. Is there a way to manually alter the values returned through Autodiscover?
unfortunately, my domain wasn't named with a .local, I went full tilt and did 'someplace.state.us', this domain belongs to the government apparently. there is also some other non-functioning parts of the domain, and general infrastructure changes, so this seems like the best time to migrate.