Outlook 2016 extremely slow when joins a domain.

I installed Windows 10 Pro with Office 2016 Home & Business.
Everything works fine with Outlook 2016 connecting to our Exchange 2010 Enterprise. The connection is quick, the sync is fast and the data is always up-to-date.
Then after doing all my tests, I was ready to join my PC to our Windows 2008 R2 domain.

When I join the domain, it creates a new profile (this is normal), where I have to configure most of the programs again.

When I get to Outlook 2016, it does validate the email account fine.
Now everytime I start Outlook 2016 (after being already configured with my email account), the initial connection to the server takes between 2-3 minutes (as opposed to 5 seconds when it was a standalone) and syncing takes very long.

Is there a way to determine what is happening?
As I said, as soon as I join our domain, the behavior of Outlook 2016 goes to pieces.
I need a solution before I start upgrading our 30+ remaining users to Outlook 2016.

Thanks for your help,
Roberto.
ROBERTO PAREJAIT ManagerAsked:
Who is Participating?
 
NerdsOfTechTechnology ScientistCommented:
Using the same URL makes it easier for users to access your Exchange server because they only have to remember one address. Regardless of the choice you make, you need to make sure you configure a private DNS zone for the address space you configure.

To send users to your Exchange 2016 Mailbox server, you need to configure the existing DNS host (A) record on your internal DNS servers. The internal DNS records should point to the internal host name and IP address of your Exchange 2016 Mailbox server. The internal host names you use should match the external host names


for example,
CNAME, mail.tecnicard.com, tc3191.tecnicard.com
CNAME, owa.tecnicard.com, tc3191.tecnicard.com
A, autodiscover.tecnicard.com, (internal network ip)

Open in new window


Check with your domain/DNS admins about the above referenced Microsoft article.
0
 
NerdsOfTechTechnology ScientistCommented:
Check to make sure your domain's autodiscover DNS entries are correct.

When changing or setting the DNS records, it is advised to set the time to live (TTL) values to a small time interval (like 5 minutes) in case of error as this is how long the entry is kept in cache.

ref: https://technet.microsoft.com/en-us/library/mt473798(v=exchg.150).aspx

The initial sync should take a long time as it is building an index.
0
 
ROBERTO PAREJAIT ManagerAuthor Commented:
Our email domain is tecnicard.com
Our network domain is tc3191.com

According to our domain admin guys, none of the DNS records for tecnicard.com is configured inside our network domain (tc3191.com).
Anything referring to tecnicard.com will be retrieved from our public DNS (which don't have anything defined for our network domain).
So it should not be a conflict because they are different.

If after joining the domain and having this problem, I reboot and sign-in as a local user, the outlook behavior is normal and very fast.
The problem happens just when I am signed-in to our domain.

Could it be just a corrupted profle on my machine?
0
 
ROBERTO PAREJAIT ManagerAuthor Commented:
Update:
It does not seem like a corrupted profile.
I just created new ones and as soon as I join the domain, Outlook becomes extremely sluggish.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.