MS Outlook and O365 issue
-
@gjacobse said:
@coliver said:
set the Pertino to the last address
Pertino is set as the last adapter.
I have about exhausted all ideas on this.
Oh that is unfortunate. Did you install the login helper from O365? I can't remember the name but it is one of the software downloads from the user profile. One of the things it does is analyze the computer for missing patches and the like. That had fixed one of them in the past but it was only for one user. Long shot but worth a try.
-
Just tried to set the account up on my computer and was unsuccessful.
Login helper, I remember that, and went to use it,.. but either they have changed it to not do it,.. or I got the wrong application.
-
Since I was working on a PC at the main office (this user is remote in South Carolina) I borrowed a Domain local computer to log in as this person and attempt to set up the Outlook.
Logging into the computer with the users AD account was fine. But Outlook could not connect to finish the setup.
No closer to resolving this.....
-
Open a support ticket. It sounds like a backend problem now.
-
I agree. Get MS support involved.
-
@gjacobse said:
@coliver said:
set the Pertino to the last address
Pertino is set as the last adapter.
I have about exhausted all ideas on this.
What about disabling Pertino while testing?
-
I've seen similar issues but the user was connecting to on-premise Exchange.
Did you delete the .OST file before you recreated her account?
-
@Reid-Cooper said:
What about disabling Pertino while testing?
I want to say yes I did. I did uninstall and reinstall Pertino. One issue with Pertino being disconnected / uninstalled is that she is unable to connect to AD and authenticate...
But I can disconnect / End Task and see what that does.
-
@gjacobse said:
@Reid-Cooper said:
What about disabling Pertino while testing?
I want to say yes I did. I did uninstall and reinstall Pertino. One issue with Pertino being disconnected / uninstalled is that she is unable to connect to AD and authenticate...
But I can disconnect / End Task and see what that does.
It wasn't using cached credentials? That seems odd.
-
@coliver said:
It wasn't using cached credentials? That seems odd.
No,... all Windows Cached Credentials were deleted...
-
@scottalanmiller said:
I've had this in the past and the answer was always "it just doesn't work."
We had one here and the answer was, use OWA.
-
I've done the same thing for years.... just use OWA.
-
When we've seen this issue it's usually been saved credentials in Windows credential manager. For some reason they can authenticate but then Outlook randomly tries the credentials in credential manager. If the credentials are old you will get a login prompt. That's always the first thing I check.
