It's old school.  No need for you kids and your newfangled Attitude Alignment 
Tools. They work just fine the way they are.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Melvin Backus
Sent: Thursday, June 1, 2017 10:56 AM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] RE: Nasty Outlook 2016 and Windows 10 issue

Clue by Four?  Is that the same as an Attitude Alignment Tool?  More 
importantly is it a direct replacement or just a compatible part?

:)

--
There are 10 kinds of people in the world...
         those who understand binary and those who don't.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kennedy, Jim
Sent: Thursday, June 1, 2017 10:19 AM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
Sent: Thursday, June 1, 2017 10:08 AM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
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: 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: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?

Reply via email to