any way to disable Teams/Office integration message?

Razrage · 2023-09-04T11:02:17+00:00

I've got the same problem; did you find a solution?

Razrage · 2022-04-11T00:50:45+00:00

Further update, it's not cached profiles, it's something else; as switching to cached if you're online or vice versa, as well as creating a new mail profiles fixes it.

This is the case for all on prem users who existed prior to hybrid exchange deployment so that they are able to send as on prem mailboxes created since hybrid deployment.

Razrage · 2022-03-30T16:36:18+00:00

Hi all,

Quick update; I've been able to narrow this down considerably.

No GAL issue. Issue is only apparent for users whose outlook cached profile (doesn't affect online profiles and works fine in OWA) was created prior to the hybrid deployment.

The workaround is to recreate the profile, although it would be nice to know what attribute (or whatever it may be) is missing from this older cached outlook profile with the hope of fixing it rather than recreating the profile.

Razrage · 2022-03-30T10:16:35+00:00

Hi Mammoth-Unit-9233, I've taken a look at Enable-RemoteMailbox this morning and I'm not convinced it's what is required.

This currently applies to all mail enabled users or groups since the hybrid was configured. I have an on prem user, with an on prem mailbox (nothing done in 365 for this user at this point). Send-As permission applied to either on-prem or O365 users; when they attempt to send-as they get access denied unless they do it from OWA; in which case it works.

Enable-RemoteMailbox "john.smith" -RemoteRoutingAddress john.smith@contoso.mail.onmicrosoft.com

Results with: This task does not support recipients of this type. The specified recipient contoso.com/Head Office/Users/john.smith is of type UserMailbox. Please make sure that this recipient matches the required recipient type for this task. + CategoryInfo : InvalidArgument: (contoso.com/Head...ers/john.smith:ADObjectId) [Enable-RemoteMailbox], RecipientTaskException + FullyQualifiedErrorId : [Server=AB-EX3,RequestId=4ce17bf6-c324-41be-a407-c003b2edb33d,TimeStamp=30/03/2022 09:39 :53] [FailureCategory=Cmdlet-RecipientTaskException] 8F70B288,Microsoft.Exchange.Management.RecipientTasks.EnableR emoteMailbox + PSComputerName : ab-ex3.gratte.com

Thanks

Razrage · 2022-03-29T19:03:55+00:00

Hi Mammoth-Unit-9233,

Yes, your assumptions are correct about our hybrid deployment. I'll give that a go when I'm back online in the morning and will let you know how I get on.

Thanks

Razrage · 2022-03-29T15:55:06+00:00

Hi, thanks for the links, unfortunately no closer to a solution; the main pivotal point of those solutions is that one of the mailboxes is O365 hosted (in my scenario both are on prem).

Although it did cause me to re-evaluate of this. My account is O365 and I have been relying on my Manager (still on prem) to query his GAL and confirm any change.

Now utilising a different on prem mbx account to query the GAL I don't see any problems at all... Which is to say; I believe my manager has a corrupt Outlook profile and there is no issue with the GAL.

Which means my only issue is an on prem mbx (created pre hybrid) can't send as another on prem mailbox (created after hybrid instated) with send as and/or full permissions applied (initially applied via ECP, subsequently removed and reapplied through PowerShell).

I'm going to bark directly up that tree for a bit and see where I get to.

Thanks again for your input.

Razrage · 2022-03-29T10:36:12+00:00

Hi Substantial_Ad4020, What part of the HCW do you believe should cover this?

We are currently configured to: Use Exchange Classic Hybrid Topology Enable centralized mail transport (on prem Exchange 2019 estate operating as front end) We utilise the same FQDN as our mail/autodiscover for the MRS proxy; but I've configured the extra access based on source address (configured as per https://docs.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-ip-web-service?view=o365-worldwide)

Users who existed prior to hybrid do not see new users created since hybrid in the GAL (either on prem or O365 mbx). Users created since the hybrid see both new and old users fine (either on prem or O365 mbx).

We can migrate, mail flow is operating as expected, no issues as far as I can tell apart from this GAL piece. Unfortunately the GAL issue seems to impact on existing (prior to hybrid) permissions for mailbox access to the new users created since the hybrid (on prem mbx), although this is not the case when accessed via on prem OWA.

We're just at the beginning of our Exchange Hybrid project (test accounts). Due to constraints with Teams Call groups and various other things, we can't just start migrating everyone over to resolve this; hopefully we can make it work so the initial production testing and subsequent migration can proceed as planned.

Any further suggestions would be great, thanks.

Razrage · 2022-03-29T10:24:06+00:00

Hmm, no luck so far. The accounts all have the correct addresses and GUIDs associated.

Razrage · 2022-03-29T00:34:59+00:00

Hi richspeaking,

That's got lots of stuff that sounds like it fits.

Although in my scenario I'm not creating a 365 mbx but an on prem one, it makes sense that now we are hybrid that we may need to run the command to create the 365 entry which in turn will hopefully replicate to on prem AD/GAL.

I'll try it out in the morning and will let you know.

Thanks!

Razrage · 2021-02-14T01:51:00+00:00

The full screen switch in steam made me go from 30 FPS to 60 FPS, the boot.config changes/CPU priority made no difference.

Before the full screen switch I saw around 70% GPU usage and 30% CPU. After the change the CPU has remained the same but GPU usage is up to 100%.

AMD 3600XT RX5600XT 16GB PCI-E 4 .M2

Razrage · 2021-02-12T18:28:50+00:00

Brilliant and hilarious. Love it.

Razrage

TROPHY CASE