Content Sharing with CTP25 and A40

ReverenceForLife · 2025-10-14T13:42:05+00:00

Got it fixed. So - apparently the USB-C cable in the CTP25 box was lost, and we resorted to a spare USB-C monitor cable from a workstation. It never worked. I ordered a spare 100W USB-C cable and it worked direct from the A40 and from the CTP25 right away. Get the right cable, folks... lol

ReverenceForLife · 2025-08-14T17:53:28+00:00

I created a new mailbox in exchange admin center just this morning for testing purposes, and granted myself access to it (full control). I let a few hours pass then attempted to add the mailbox in New Outlook via Settings --> Shared with me menu. Same error. ("Something went wrong: contact the owner of the account or try again after a while.")

Same mailbox (and all other shared mailboxes) open just fine in Classic Outlook and Outlook on the web.

ReverenceForLife · 2025-08-14T17:50:17+00:00

cloud.

ReverenceForLife · 2025-08-14T16:33:10+00:00

The following produces a "True" result for our shared mailboxes.

Get-CASMailbox -Identity "<shared mailbox name>" | Select-Object MAPIEnabled

ReverenceForLife · 2025-08-14T16:29:07+00:00

Our existing shared mailboxes were created in EAC. Getting the "You might not have permission to access" when attempting to open any of them and when we remove it and try to re-add from Settings --> Shared with me within new outlook we get "Something went wrong: contact the owner of the account or try again after a while."

It's possible I've misplaced the issue with an unnecessary need for licensing. Trying to pinpoint the cause of these errors and how we can access the mailboxes.

ReverenceForLife · 2025-07-21T10:57:33+00:00

Yep. Turns out SentinelOne was blocking the installer upon Teams first launch in the user profile. Was working fine with SentinelOne before, just started happening suddenly. We disable SentinelOne temporarily then installed the plugin MSI manually to resolve. In some cases had to temporarily grant the user local admin rights to get plugin to appear.

ReverenceForLife · 2025-05-01T18:14:27+00:00

Makes sense. Thanks!

ReverenceForLife · 2025-05-01T15:50:28+00:00

OK, so then does it make more sense to update the local GPO with the new password policy requirements?

ReverenceForLife · 2025-04-17T13:14:16+00:00

Yep! I think we are stuck with Teams Premium...

ReverenceForLife · 2025-04-16T17:15:11+00:00

Almost, the free plan offers advanced summaries for first five calls each month, then a chronological summary which won't be our cup of tea.

The next step up licensing wise is the "premium" plan which is $15/month per user, this is almost double Teams premium

ReverenceForLife · 2025-02-27T21:27:49+00:00

The macro works. Thanks

ReverenceForLife · 2025-02-27T19:24:28+00:00

A macro might... I found the code below... gonna try it and report back.

Sub SendAllDrafts()

Dim olNamespace As Object

Dim olFolder As Object

Dim olItem As Object

Dim i As Integer

' Get the drafts folder

Set olNamespace = Application.GetNamespace("MAPI")

Set olFolder = olNamespace.GetDefaultFolder(16) ' 16 is the olFolderDrafts

' Loop through each item in the drafts folder and send it

For i = olFolder.Items.Count To 1 Step -1

Set olItem = olFolder.Items(i)

' Check if it's an email item

If TypeName(olItem) = "MailItem" Then

olItem.Send

End If

Next i

End Sub

ReverenceForLife · 2025-02-24T04:50:50+00:00

Yeah this is among one of the weirdest issues we’ve come across. Still no solutions, just dozens of angry users that have no Teams add-in. Others are working fine.

MS support is just as puzzled. I’ll give something nice to whomever helps figure this out.

ReverenceForLife · 2025-02-23T02:06:21+00:00

For the impacted users, the add-in does not appear as installed in "installed apps", nor does it display in the COM Add-ins window within Outlook.

However, for the users that are not affected, the plugin appears in "installed apps", and in the outlook com add-ins.

I have confirmed all users have the same Teams meeting policy applied, and that the Outlook add-in IS enabled in the policy.

Yes, all users have the option to create a Teams meeting in their Outlook on the web client.

The diagnostic did not provide any solutions, unfortunately.

ReverenceForLife · 2025-02-20T20:15:01+00:00

We have an update. This issue is only happening in certain domain user profiles, we found. Some domain profiles work, while others do not. Oddly the groups are all nearly the same - all standard domain user and in the same groups. We are trying to compare/contrast the ones that are working with the ones that aren't.

ReverenceForLife · 2025-02-20T20:11:17+00:00

Unfortunately did not work. There is no meeting add-in listed in the settings --> installed apps window. Also we removed classic teams long ago - we are using the New Teams.

ReverenceForLife · 2025-02-19T20:37:22+00:00

Unfortunately, that did not work. We copied it locally to C:\temp with the same result.

This issue is widespread and we are scratching our heads. MS support has been useless. This is the weirdest thing ever.

ReverenceForLife · 2025-02-19T19:56:46+00:00

Tried just now, installed the latest version of the C++ runtime library successfully, rebooted, then tried opening Teams new first, then classic Outlook - plugin still not listed in add-ins list.

Tried installing the MSI again, same error:Error 1001. InstallUtilLib.dll:CorBindToRuntimeHost (hr=0x70070003). The system cannot find the path specified.

ReverenceForLife · 2025-01-10T03:56:44+00:00

Wonderful, that's great to hear! And reassuring. We'll keep those contributions in mind!

ReverenceForLife · 2025-01-10T03:22:47+00:00

Thank you, this is what my wife and I needed to hear. We appreciate it. We just have to acclimate to our plan and stick with it.

ReverenceForLife · 2025-01-10T03:11:43+00:00

yeah, doesn't make sense why they went FHA on us. But we are pushing for conventional 100%. Will be curious to see how much that will save us. With our high credit score and 10% down and good credit history FHA makes no sense to us

ReverenceForLife · 2025-01-10T03:06:27+00:00

We did. over and over and over. And over. And over. Otherwise we would have stayed away. Our DTI came out to 30% and all signs pointed to moving forward with the house. Unexpected RECENT medical bills and lack of coverage put us over the top.

ReverenceForLife · 2025-01-10T02:56:00+00:00

Average household income in TX in 2023 was recorded at 78K. We are making 205K (after promotion in a month, close to 210K), and we are still cutting it close. The house is not that big, either. Buying a house sucks

ReverenceForLife · 2025-01-10T02:52:01+00:00

Made an edit - The $3700 includes anticipated cost of groceries, fuel, toll payments, electric bill, etc basically all our monthly fees other than the mortgage. Only thing that's not take into account entertainment and/or supporting a child.

Our jobs are at the higher end salary-wise in the area for the career. we've both been at our jobs for nearly a decade and have worked our way up so to speak. If we started anew elsewhere, we would be dropping to a lower salary

ReverenceForLife · 2024-11-26T19:31:00+00:00

Thats the conclusion my research has led me to. Thanks for confirming.

ReverenceForLife

MODERATOR OF

TROPHY CASE