Always happy to help. This is my recommended brand: [Image result for clue by four image]
From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Thursday, June 1, 2017 10:19 AM To: [email protected] Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue Michael, can I hire you for a day or two to beat that idea into my desktop tech's heads? We will provide the clue by four. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, June 1, 2017 10:08 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue I have no idea. To evaluate, I would be looking at connection statistics, debug logs, and wireshark. However - if a workstation gives you problems, re-image it. It's not worth the time or hassle to debug anymore. A rebuild can be done in 30 minutes or less. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 9:46 AM To: [email protected]<mailto:[email protected]> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, June 01, 2017 9:38 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue They should be recreated for the proper contents of the new profile. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 9:25 AM To: [email protected]<mailto:[email protected]> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, June 01, 2017 9:20 AM To: [email protected]<mailto:[email protected]> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Katherine M. Moss Sent: Thursday, June 1, 2017 8:56 AM To: [email protected]<mailto:[email protected]> 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?
