You can add outlook 2016 with no account. Then open the tool in the systems tray and test autodiscover down there. Mine is still showing all failed in the split DNS I have going on.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Joseph L. Casale Sent: Thursday, June 1, 2017 10:29 AM To: 'ntsysadm@lists.myitforum.com' <ntsysadm@lists.myitforum.com> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue Notice: This email is from an outside source. Please do not open any attachments, click on any hyperlinks, or respond without first confirming the authenticity of the email. The test asks for an email and its associated password. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 8:21 AM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue Everything looks good; I can't test a nonworking account if I can't add said account, though, can I? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Joseph L. Casale Sent: Thursday, June 01, 2017 10:08 AM To: 'ntsysadm@lists.myitforum.com' <ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue I haven't seen a scenario, but I could imagine one for an internal network where the service connection point was wrong and dns varied between workstations which might result in the behavior you describe. Might be worth checking the config. What does the output between a working and a non-working desktop look like for the outlook test e-mail auto configuration for the same account? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 7:46 AM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue Now why did this not happen on my spare D630? And why did the D630 not hang on credential pass? I'm confused about this; why some of us are having performance issues during account add and others are not. And it seems specific to certain workstations.Like I said; only mine and this other guy is having the issue; our admin can't see the problem. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, June 01, 2017 9:38 AM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue They should be recreated for the proper contents of the new profile. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 9:25 AM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue If I move them, though, will they be re-created upon the creation of the new profile? And could those have anything to do with why Outlook is crashing for this account? In that case it's just one computer. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, June 01, 2017 9:20 AM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue In appdata for Outlook are a few XML files where OST and PST files are stored. Before you create a new profile, you should save-off those XML files (put them in a different folder). They are used by Outlook 2016 to build the profile instead of the PRF files that prior versions of Outlook used. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 8:56 AM To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com> Subject: [NTSysADM] Nasty Outlook 2016 and Windows 10 issue Hi all, This might end up on the Exchange list, but until then, it looks like a different issue. I have recently reinstalled Office 2016 in light of a crashing Outlook when I went to set up this email address inside. Upon reinstall, I created a new profile, (the "connect Outlook to Office 365" dialogue needs to go the hell away, if you ask me), selected connect to a different account, and then all of the fields are autopopulated with values from my other email account which is indeed Office 365. If this is a brand new office install and my computer is set up with a local account, from where is Outlook even pulling values from my Microsoft account anyway? Not sure whether the two issues are related, but after correcting the autopopulated fields to match the values for this account (on premise Exchange server 2016), I'm having an annoying thing happen where the credentials prompt just hangs for ever and ever. Hence I'm having to use the Windows 10 mail application until I can resolve the issue. It's only on one computer where it happens; this one is fine, and my other laptop is fine. It's only my newer primary laptop where this is happening. Someone else I know is having the same issue, and autodiscover is set up correctly. Any other advice? This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
