packetloss

joined 2 years ago
[–] packetloss 2 points 1 year ago* (last edited 1 year ago) (2 children)

Edit: September 25, 2023 - Added more details to the solution for my issue.

Just wanted to update this so if anyone else is having the same issue hopefully it helps them.

During initial tenant setup I created a couple of retention policies. I thought these would only affect Teams data, but it turns out it also applied to Exchange Online mailboxes. When I tried to remove the Exchange Online license from the user it would give an Exchange error message in admin console and the mailbox would not get removed.

The issue turned out to be caused by holds that were applied to the user mailbox. Specifically these two:

DelayHoldApplied

ReleaseDelayHoldApplied

Both were set to $true.

  1. I removed the retention policies, they probably weren't configured correct in the first place.

  2. Used the following Powershell command to identify the holds applied to mailboxes:

Get-Mailbox | FL Identity,*HoldApplied*

  1. Used the "Set-Mailbox" command to remove those holds:

Set-Mailbox -Identity @mydomain.com -RemoveDelayHoldApplied

Set-Mailbox -Identity @mydomain.com -RemoveDelayReleaseHoldApplied

  1. Delete the user's mailbox by removing the Exchange Online license from the user and waited for the mailbox to disappear from the Exchange Online admin center.

  2. Run the following command to wipe out the pre-existing mailbox data. Without doing this, even after the on-prem user is synced Exchange Online will not care that the user has an on-prem mailbox, and will restore the previously deleted cloud mailbox from step 4.

Set-User @mydomain.com -PermanentlyClearPreviousMailboxInfo

  1. Force a sync of users using Azure AD Connect

  2. Re-enable the Exchange Online license for the user. After this is done in the users Mail settings you should see a message "This user's on-premises mailbox hasn't been migrated to ‎Exchange Online‎. The ‎Exchange Online‎ mailbox will be available after migration is completed"

Thanks to everyone who replied and offered help.

[–] packetloss 5 points 1 year ago (2 children)

I think this is what OP is talking about. Links show up, but when tapping on them they don't work.

[–] packetloss 8 points 1 year ago

It took all of a couple of minutes for the download option to show for me.

[–] packetloss 1 points 1 year ago

No, we don't have any licenses other than Business Basic or Business Standard.

[–] packetloss 32 points 1 year ago (7 children)

Update the OS and all installed applications using a single command.

[–] packetloss 12 points 1 year ago (1 children)

Pretty sure they're not transporting kids in that vehicle, but the OP spotted this vehicle while taking the kids to school.

[–] packetloss 22 points 1 year ago (1 children)

I've tried a handful of the Android apps and so far the most comfortable one for me is Liftoff. But I loved Boost for Reddit, so I'm very much looking forward to trying the Lemmy version.

[–] packetloss 58 points 1 year ago (1 children)

Is this how you partition a hard drive?

[–] packetloss 6 points 1 year ago

Perfect depiction of downtown Vancouver.

[–] packetloss 9 points 1 year ago

The closest thing to an official app is Jerboa.

[–] packetloss 5 points 1 year ago

The biggest and most surprising life lesson I've learned as a home owner: The sheer amount of jankiness that is in your walls that you don't know about will actually terrify you once you start any sort of major renovation.

I can't tell you how many times I said the words "Are you fucking kidding me?" or "What the actual fuck?" during my recent reno. After what I saw, a coffee can as a piece of ducting is mild.

[–] packetloss 4 points 1 year ago (4 children)

I tried Google Authenticator, Bitwarden, Duo Authenticator, and Microsoft Authenticator. I also tried on mobile (Android) and on desktop.

In all cases the authenticator was giving me a 6 digit code, but the code was not valid. If I used the same secret on multiple authenticators they all gave me the same TOTP codes, which is expected, but the codes wouldn't work. So even though multiple authenticators are displaying the same TOTP code, the code the site is expecting doesn't match. Meaning the site is not using the secret it generated properly.

view more: ‹ prev next ›