J
_jp_99
Guest
I feel like there's probably an obvious answer I'm overlooking for this, but everyone else in my department is also stumped so I'll take any ideas at this point.
We've deployed Office 2013 to all our end users (Win 10 Pro user environment), mostly without issue. Recently, two things have started happening for new setups of Outlook specifically:
Outlook will then close, as the .ost is considered inaccessible. In troubleshooting the issue, we've found that the second authentication failure problem happens in non-elevated copies of Outlook in standard Windows user accounts, but does NOT happen in elevated instances of Outlook. We have also tried:
Currently the ideas are being floated that autodiscover's implementation isn't quite right or we're having a DNS issue since both the ost authentication and autodiscover are being affected, but I'm questioning whether permissions are a factor considering the way Admin accounts go through the setup successfully.
Any suggestions?
Continue reading...
We've deployed Office 2013 to all our end users (Win 10 Pro user environment), mostly without issue. Recently, two things have started happening for new setups of Outlook specifically:
- Autodiscover is no longer properly retrieving exchange accounts, so we have to manually enter the user's credentials (which do successfully authenticate)
- After the mail profile has been created and Outlook is being opened for the first time, it acts like it can't authenticate the account and then gives the error:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file [.ost filepath] cannot be accessed. You must connected to Microsoft Exchange at least once before you can use your Outlook data file (.ost)."
Outlook will then close, as the .ost is considered inaccessible. In troubleshooting the issue, we've found that the second authentication failure problem happens in non-elevated copies of Outlook in standard Windows user accounts, but does NOT happen in elevated instances of Outlook. We have also tried:
- Verifying the local machines can talk to the right servers with pings, tracerts etc.
- Verifying permissions are set to full r/w access for the user's Outlook directory
- Updating our host files
- Manual DNS entries
- Resetting .network adapters
- Wi-Fi vs LAN connections
- Verifying SMB settings between client and server
Currently the ideas are being floated that autodiscover's implementation isn't quite right or we're having a DNS issue since both the ost authentication and autodiscover are being affected, but I'm questioning whether permissions are a factor considering the way Admin accounts go through the setup successfully.
Any suggestions?
Continue reading...