@irj said in Outlook 2016/o365: Sent items issue:

@gjacobse said in Outlook 2016/o365: Sent items issue:

Thus far, nothing has resolved this issue.

As the install was Office 365;
Deleted OST file
Deleted User Mail profile
Online repair
Un-installed Office 365
Cleared application / user folders - rebooted
Installed Office 2016

The only other thing i can think of is;

Backup user data, wipe the drive (2 min max as it is a nvm drive) Image and restore user data.

This is an odd issue to say the least. I am hoping the o365 team can determine a solution rather than having to go that route.

I feel like you're shooting a shotgun in the woods during a new moon and praying to hit a target.

If you don't have permission to make any changes because of GPO and you have no visibility in office 365. Then just escalate the issue. Otherwise it's just a time waste for all involved.

Lol- I did. The O365 team kicked to the IR Team ( incident response), who closed it as I was working ...

Guess I’ll just have to reimage it ,.,.,

Had the user install the outlook app.

“Oh this is much better”

Problem solved.

@jaredbusch Well that is one way to secure things......

@kmac76 It works well, just haven't tried this.

See my post earlier had a user who could not send. Microsoft has an open service advisory not published about general slowness in their system.

@Dashrender said in Managing Distribution Groups in an Exchange Hybrid Environment:

@EddieJennings said in Managing Distribution Groups in an Exchange Hybrid Environment:

I ought to have clarified. DUO MFA comes into play with Outlook for our mailboxes that are in Exchange Online. On-prem mailboxes (the few we have left aren't subject to DUO).

Are those that are left on prem - are they actual users? If so, I'm curious why they can't be migrated?

Eventually all users will be migrated, so, yes, we still have real users on-prem.

This is outside the scope of the original question / scenario, but I've learned a good bit during this process with much of that learning validating a few things I already knew, such as the value of taking the necessary time to plan, and prep the environment for migration (removing unnecessary objects, etc.).

Looks like @Osvaldo was able to get it.

@Dashrender said in O365 Outbound email issue:

@JaredBusch said in O365 Outbound email issue:

For the record, even though I made the above connector and it failed to verify, I did save the connector. Apparently, that was enough as email is sending now.

So which connector is solving this - the TLS regardless of cert condition, or the No-TLS

I only left the TLS regardless of cert, so it has to be that one.

@Obsolesce said in Microsoft Search in Bing and Office 365 ProPlus:

@scottalanmiller said in Microsoft Search in Bing and Office 365 ProPlus:

Since I switched to DDG, I've noticed Google has gone down hill significantly.

That's why, it's because YOU switched.

No reason to keep it good, I guess, lol.

@anamanp said in Office 365 NDR for strange email address.:

@Romo Can you please tell me if this was resolved?

Yes, his reply with the solution was three above your post.

Rules set on OWA to keyword autoforward. The account was compromised.

@JaredBusch said in Need to setup O365 shared calendar:

@Dashrender said in Need to setup O365 shared calendar:

@JaredBusch said in Need to setup O365 shared calendar:

@Dashrender said in Need to setup O365 shared calendar:

If it's a fully shared (controlled by all) calendar, I would choose Can edit.

That does not answer the question

It is a normal user, the admin account. That went to their calendar and clicked new calendar. They then shared it as shown.

Then I don't understand the question - I said - choose "Can edit" that's one of the choices you showed as an option.

WTF does "Can Edit" mean? Is it actually the most open access? I have no idea.

It's all hidden from the GUI now as far as I know but higher access levels still exist. The only thing I've actually run into people trying to use that requires it is messing with categories.

You have to be a Publishing Editor or Owner to work with them.

I usually end up assigning those for users using PowerShell when the need arises.

get/set/add-mailboxfolderpermission

This is working on several machines now. But @romo reports that it is still hit or miss, it's not a reliable or permanent fix, but it more reliable than other attempts. It remains, as MS has stated, somewhat random.

I've seen issues with search for the last week or so. A few people here have been unable to search public folders or their inboxes on and off. Supposedly resolved. We'll see...